Set up MOLOCO
MOLOCO is an ad network integrated with Adjust. Our integration lets MOLOCO receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with MOLOCO for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with MOLOCO.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to MOLOCO parameters. Follow the guides linked below to use this feature.
iOS / Android / Windows / Unity / React Native / Flutter / Adobe Air / Cordova / Marmalade / Xamarin / Cocos2d-x / Titanium / Corona
Select MOLOCO and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > MOLOCO. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with MOLOCO.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with MOLOCO. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with MOLOCO, Adjust automatically sends MOLOCO the following data, by default:
- click
- install
- session
- uninstall
- reattribution
- event
- rejectedInstall
- ad revenue
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- Set the same data sharing settings for multiple platforms by selecting Use global settings.
Now, under What will be shared by default?, review the activities that Adjust shares with MOLOCO by default.
- click
- install
- session
- uninstall
- reattribution
- event
- rejectedInstall
- ad revenue
Send additional data
Choose the amount and type of data that you want to share with MOLOCO through callbacks. MOLOCO may use this information to optimize performance.
- Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with MOLOCO:
- Data from all attribution sources
- Only data attributed to MOLOCO
In-app revenue (from in-app purchases)
Sharing in-app revenue lets MOLOCO receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Ad revenue (from ad views)
Ad revenue sharing lets MOLOCO receive user ad revenue data. This lets MOLOCO use ad revenue data to optimize your user targeting and campaigns.
This feature is available with Adjust’s RevWorks package. To purchase our RevWorks package, contact your sales representative.
To share ad revenue to MOLOCO, select one or more Ad Revenue Sources.
- If you leave this field empty, we send ad revenue data from all integrated mediation sources.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means MOLOCO will receive your app’s session activity.
Map parameters
You usually need to map parameters to share custom data with MOLOCO.
Map events
Map events that you want to share to the values that MOLOCO can receive. Data for unmapped events is not shared with MOLOCO.
Under Map events, follow these steps to choose the in-app events you want to directly send to MOLOCO.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with MOLOCO.
- In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
- Select Apply.
Now MOLOCO will receive in-app event data for each of your linked events.
Map parameters
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to MOLOCO. This lets MOLOCO receive custom event details for each of your linked events.
Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To share partner parameters to MOLOCO, follow these steps.
- Set up partner parameters within the Adjust SDK: iOS, Android
- Check the Parameters data sharing checkbox.
- Map your events.
If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.
Configure your link and settings
You have the option to set your:
Create your link and share it with MOLOCO
In the Setup review screen, you can review your choices. You can also go back and make changes to:
- Your selected app
- Data sharing options
- Link structure parameters
- User destinations
- Attribution settings
Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with MOLOCO.
Once you’ve created your link, share it with MOLOCO for placement in campaigns.
List of all parameters forwarded to MOLOCO
MOLOCO requires Adjust to send the following parameters (data points) with your callbacks:
| Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id} | Android ID (Android only) |
{city} | Device city |
{country} | Device two-character country code |
{device_name} | Device model number |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{ip_address} | Device IP address |
{language} | Device two-character language code |
{mac_md5} | Uppercase MAC MD5 hash |
{mac_sha1} | Uppercase MAC SHA-1 hash |
{match_type} | Attribution method |
{os_name} | Device operating system |
{os_version} | Operating system version number |
{partner_parameters} | Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks |
{postal_code} | Device postal code of IP address |
{random} | Random number (unique per callback) |
{referrer} | Google Play Store referrer (Android only) |
{region} | Device region code |
{revenue_usd} | Revenue, in US dollars |
{sdk_version} | Adjust SDK version (per app) |
{session_count} | Number of sessions recorded by current Adjust SDK |
{time_spent} | Length of user's current session, in seconds |
{timezone} | Device time zone |
{tracking_enabled} | 1 if tracking is enabled, 0 if not |
{tracking_limited} | 1 if tracking is limited, 0 if not |
{user_agent} | Incoming raw user agent |
{win_hwid} | Windows Store hardware ID |
{win_naid} | Windows Store network adapter ID |
{win_udid} | Windows Phone unique device ID |
{adgroup_name} | Adgroup name, as taken from the tracker |
{app_id} | Store App ID or Google Play Store |
{app_name} | Name of the app |
{app_version} | App version number (Android), build-version-number for the bundle (iOS) |
{campaign_name} | Campaign name, as taken from the tracker |
{click_time} | Attributed click timestamp |
{created_at} | Activity timestamp |
{creative_name} | Creative name, as taken from the tracker |
{impression_based} | 1 if impression-based engagement, 0 if not |
{impression_time} | Attributed impression timestamp |
{install_begin_time} | App download began timestamp (Android and Google Play Store only) |
{install_finish_time} | App download completion timestamp |
{is_organic} | 1 if organic traffic, 0 if non-organic |
{network_name} | Network name, as taken from the tracker |
{referral_time} | User landed on app Play Store page timestamp (Android and Google Play Store only) |
{rejection_reason} | Reason for a rejected attribution |
{store} | Target store of click |
{ad_impressions_count} | Number of mobile ads served to end users |
{ad_revenue_network} | Ad network that displayed the ad |
{ad_revenue_unit} | Ad unit that generated the revenue |
{ad_revenue_placement} | User placement, as defined on the platform |
{ad_mediation_platform} | Mediation platform name |
{ad_revenue_payload} | Impression-level revenue data (ILRD) as a JSON |