Set up Inmobi

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

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

Basic setup

To turn on Adjust’s integration with Inmobi, 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 Inmobi
  4. Enter your GPM ID and ADVERTISER ID (contact your Inmobi representative for help finding these)
  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 Inmobi to launch your campaign.

Inmobi will receive callbacks for these activities:

  • install
  • rejected install
  • session
  • event
  • reattribution

Advanced setup

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

Only forward data attributed to Inmobi

Adjust sends Inmobi your installs and reattributions across all ad platforms.

To stop Inmobi from receiving data attributed to other ad platforms, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Inmobi
  3. Turn on Attributed Only

Now Inmobi will only receive data attributed to their own platform.

 

Forward in-app revenue

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

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

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

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

 

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

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

Now Inmobi 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 Inmobi.

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 Inmobi, 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 > Inmobi
  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 Inmobi name.
  7. Select Save

Now Inmobi 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 Inmobi receive app event data. You can link every app event in Adjust to a preset Inmobi name or a custom event name.

To forward app events to Inmobi, follow these steps.

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

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

List of all parameters forwarded to Inmobi

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

Placeholder Information
{adgroup_name} Adgroup name, as taken from the tracker
{android_id_md5} Lowercase Android ID hex MD5 hash
{app_id} Store App ID or Google Play Store
{app_version_raw} App version number (Android), build
{city} Device city
{click_attribution_window} Attribution window settings for device matching (hours)
{click_time} Attributed click timestamp
{connection_type} Internet connection type
{country} Device two
{created_at_milli} Activity timestamp with millisecond placeholders
{creative_name} Creative name, as taken from the tracker
{device_name} Device model number
{device_type} Device type
{gps_adid} Google Play Store advertising ID
{idfa} ID for advertisers (iOS only)
{idfv} Uppercase iOS ID for vendors
{impression_attribution_window} Attribution window settings for impression matching (hours)
{impression_based} 1 if impression
{inactive_user_definition} Inactivity period required for reattribution (hours)
{install_begin_time} App download began timestamp (Android and Google Play Store only)
{ip_address} Device IP address
{is_organic} 1 if organic traffic, 0 if non
{language} Device two
{last_time_spent} Length of user's last session, in seconds
{lifetime_session_count} Number of sessions recorded across entire user lifetime
{match_type} Attribution method
{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
{random} Random number (unique per callback)
{reattribution_attribution_window} Attribution window settings for reattribution (hours)
{referral_time} User landed on app Play Store page timestamp (Android and Google Play Store only)
{revenue_usd} Revenue, in US dollars
{session_count} Number of sessions recorded by current Adjust SDK
{time_spent} Length of user's current session, in seconds
{user_agent} Incoming raw user agent