Set up MolocoAds

MolocoAds is a network and Adjust module partner. Our integration lets MolocoAds receive attribution and app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to MolocoAds. Then, use our advanced setup instructions to customize what information MolocoAds receives.

Basic setup

To turn on Adjust’s integration with MolocoAds, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select Add (+icon) next to MolocoAds
  4. Turn on Enabled
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to MolocoAds to launch your campaign.

MolocoAds will receive callbacks for these activities:

  • click
  • install
  • rejected install
  • session
  • event
  • reattribution
  • uninstall

Advanced setup

Choose which data MolocoAds receives from Adjust by customizing your setup.

Forward in-app revenue

Revenue forwarding lets MolocoAds receive revenue amounts along with your revenue event data.

To forward in-app revenue to MolocoAds, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > MolocoAds
  3. Turn on In-App Revenue Forwarding

Now MolocoAds will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to MolocoAds before turning on Revenue Forwarding

 

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to MolocoAds, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > MolocoAds
  3. Turn on Session Forwarding

Now MolocoAds will receive your app’s session activity.

 

Forward app events

Event linking lets MolocoAds receive app event data. You can link every app event in Adjust to a preset MolocoAds name or a custom event name.

To forward app events to MolocoAds, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup >MolocoAds > Event Linking
  3. Find the event you want to link and update the field with a MolocoAds event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

Now MolocoAds will receive app event data for each of your linked events.

List of all parameters forwarded to MolocoAds

MolocoAds requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder Information
{adgroup_name} Adgroup name, as taken from the tracker
{adid} Adjust device ID (all platforms)
{android_id} Android ID (Android only)
{app_id} Store App ID or Google Play Store
{app_name} Name of the app
{app_version} App version number (Android), build
{campaign_name} Campaign name, as taken from the tracker
{city} Device city
{click_time} Attributed click timestamp
{country} Device two
{created_at} Activity timestamp
{creative_name} Creative name, as taken from the tracker
{device_name} Device model number
{gps_adid} Google Play Store advertising ID
{idfa} ID for advertisers (iOS only)
{idfv} Uppercase iOS ID for vendors
{impression_based} 1 if impression
{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
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{language} Device two
{mac_md5} Uppercase MAC MD5 hash
{mac_sha1} Uppercase MAC SHA
{match_type} Attribution method
{network_name} Network name, as taken from the tracker
{os_name} Device operating system
{os_version} Operating system version number
{postal_code} Device postal code of IP address
{random} Random number (unique per callback)
{referral_time} User landed on app Play Store page timestamp (Android and Google Play Store only)
{referrer} Google Play Store referrer (Android only)
{region} Device region code
{rejection_reason} Reason for a rejected attribution
{revenue_usd} Revenue, in US dollars
{sdk_version} Adjust SDK version (per app)
{session_count} Number of sessions recorded by current Adjust SDK
{store} Target store of click
{time_spent} Length of user's current session, in seconds
{timezone} Device time zone
{tracking_enabled} 1 if tracking is enabled, 0 if not
{win_hwid} Windows Store hardware ID
{win_naid} Windows Store network adapter ID
{win_udid} Windows Phone unique device ID