Set up Mobrain by Headway

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

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

Basic setup

To turn on Adjust’s integration with Mobrain by Headway, 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 Mobrain by Headway
  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 Mobrain by Headway to launch your campaign.

Mobrain by Headway will receive callbacks for these activities:

  • install
  • rejected install
  • session
  • event
  • reattribution
  • rejected reattribution

Advanced setup

Choose which data Mobrain by Headway receives from Adjust by customizing your setup.

Forward in-app revenue

Revenue forwarding lets Mobrain by Headway receive revenue amounts along with your revenue event data.

To forward in-app revenue to Mobrain by Headway, follow these steps.

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

Now Mobrain by Headway will receive the revenue amount for every tracked transaction.

 

Note: Link at least one revenue event to Mobrain by Headway 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 Mobrain by Headway, follow these steps.

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

Now Mobrain by Headway 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 Mobrain by Headway.

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 Mobrain by Headway, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > Mobrain by Headway
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. 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 Mobrain by Headway name.
  7. Select Save

Now Mobrain by Headway 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 app events

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

To forward app events to Mobrain by Headway, follow these steps.

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

Now Mobrain by Headway will receive app event data for each of your linked events.

List of all parameters forwarded to Mobrain by Headway

Mobrain by Headway requires Adjust to send the following parameters (data points) with your callbacks:

Placeholder Information
{activity_kind} Type of user activity
{app_id} Store App ID or Google Play Store
{app_name} Name of the app
{app_version_short} App version number (Android), release
{city} Device city
{click_time} Attributed click timestamp
{country_subdivision} Device subdivision of country, e.g., state
{country} Device two
{created_at} Activity timestamp
{idfa||gps_adid} IDFA, or GPS ADID if IDFA is empty
{installed_at} Install (i.e., first app open) timestamp
{is_reattributed} 1 if user was reattributed at least once from an earlier source. 0 if user has never been reattributed
{match_type} Attribution method
{os_name} Device operating system
{partner_parameters} Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{rejection_reason} Reason for a rejected attribution
{revenue_usd} Revenue, in US dollars