Set up MOLOCO
MOLOCO is a network and Adjust module partner. Our integration lets MOLOCO receive attribution and in-app event data through automated callbacks.
Use our basic setup instructions to turn on Adjust’s integration and send callbacks to MOLOCO. Then, use our advanced setup instructions to customize what information MOLOCO receives.
Basic setup
To turn on Adjust’s integration with MOLOCO, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > ADD PARTNERS
- Select the add (+) icon next to MOLOCO
- Turn on Enabled
- Optional: see advanced setup to customize your callbacks
- Select Save
Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to MOLOCO to launch your campaign.
MOLOCO will receive callbacks for these activities:
click
install
session
uninstall
reattribution
event
rejectedInstall
ad revenue
Advanced setup
Choose which data MOLOCO receives from Adjust by customizing your setup.
Only forward data attributed to MOLOCO
Adjust sends MOLOCO your installs and reattributions across all ad platforms.
To stop MOLOCO from receiving data attributed to other ad platforms, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO
- Turn on Attributed Only
Now MOLOCO will only receive data attributed to their own platform.
Forward in-app revenue
In-app revenue forwarding lets MOLOCO receive revenue amounts along with your revenue event data.
To forward in-app revenue to MOLOCO, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO
- Turn on In-App Revenue Forwarding
Now MOLOCO will receive the revenue amount for every tracked transaction.
Note: Link at least one revenue event to MOLOCO before turning on In-App Revenue Forwarding.
Forward ad revenue
Ad revenue forwarding lets MOLOCO receive user ad revenue data. This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.
To forward ad revenue to MOLOCO, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO
- Turn on Ad Revenue Forwarding
- Optional: Select one or more Ad Revenue Sources.
- If you leave this field empty, we send Ad Revenue Data from all integrated mediation sources.
- Select Save
Now MOLOCO can use ad revenue data to optimize your user targeting and campaigns.
Forward sessions
Adjust does not automatically send session callbacks due to the high volume of sessions.
To forward in-app sessions to MOLOCO, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO
- Turn on Session Forwarding
Now MOLOCO will receive your app’s session activity.
Forward custom data
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to MOLOCO.
Note: Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.
To forward partner parameters to MOLOCO, follow these steps.
- Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
- In the Adjust dashboard, find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO
- Turn on Parameter Forwarding
- Select Partner Parameter Mapping
- In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding MOLOCO name.
- Select Save
Now MOLOCO will receive custom event details for each of your linked events.
Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.
Forward in-app events
Event linking lets MOLOCO receive in-app event data. You can link every in-app event in Adjust to a preset MOLOCO name or a custom event name.
To forward in-app events to MOLOCO, follow these steps.
- Find your app and select your app options caret (^)
- Select Partner Setup > MOLOCO > Event Linking
- Find the event you want to link and update the field with a MOLOCO event or your own custom name
- When you finish linking events, select OK
- Select Save
Now MOLOCO will receive in-app event data for each of your linked events.
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 |
{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 |