Set up InMobi DSP

InMobi DSP is an ad network integrated with Adjust. Our integration lets InMobi DSP receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with InMobi DSP for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with InMobi DSP.

Before you begin

Requirements

• Admin, Editor, or Custom Editor permissions in Adjust.
• Adjust SDK v4.0.0 and later to map SDK parameters to InMobi DSP 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

Credentials

GPMID and Advertiser ID

• For help finding your credentials, contact your InMobi DSP representative.

Select InMobi DSP and your app in Campaign Lab

1. Under Campaign Lab, select Partners.
2. Select New partner > InMobi DSP. Select Next to move to the next screen.
3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with InMobi DSP.
4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with InMobi DSP. To enable data sharing:

1. Enter your GPMID and Advertiser ID.

Once you enable data sharing with InMobi DSP, Adjust automatically sends InMobi DSP the following data, by default:

• install
• session
• reinstall
• reattribution
• event
• rejectedInstall
• rejectedReattribution
• 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:

1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
2. 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 InMobi DSP by default.

• install
• session
• reinstall
• reattribution
• event
• rejectedInstall
• rejectedReattribution
• ad revenue

Send additional data

Choose the amount and type of data that you want to share with InMobi DSP through callbacks. InMobi DSP may use this information to optimize performance.

1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with InMobi DSP:

• Data from all attribution sources
• Only data attributed to InMobi DSP

Ad revenue (from ad views)

Ad revenue sharing lets InMobi DSP receive user ad revenue data. This lets InMobi DSP use ad revenue data to optimize your user targeting and campaigns.

To share ad revenue to InMobi DSP, 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 InMobi DSP will receive your app’s session activity.

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets InMobi DSP receive your app’s uninstall and/or reinstall data measured by Adjust.

In-app revenue (from in-app purchases)

Sharing in-app revenue lets InMobi DSP receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Map events

Map events that you want to share to the values that InMobi DSP can receive. Data for unmapped events is not shared with InMobi DSP.

Map individual events

If you have a multi-platform app, you can choose to share different events per platform with InMobi DSP. This lets you:

• Set individual events to manage campaign strategies for each platform.
• Customize data sharing per platform.

Under Map events, follow these steps to choose the in-app events you want to directly send to InMobi DSP.

1. Select Map event.
2. In the Adjust event list, choose the Adjust event that you want to share with InMobi DSP.
3. Under Partner event, you need to select the InMobi DSP event that corresponds to the Adjust event.
   1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
      • Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
      • Select Use global mapping to map the same events for all platforms.
   2. In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
4. Select Apply.

Now InMobi DSP will receive in-app event data for each of your linked events.

Map all events

If InMobi DSP supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.

Now InMobi DSP will receive in-app event data for all your linked events.

Map subscription events

Map subscription events that you want to share to the values that your network can receive. Data for unmapped events is not shared with your network.

If you have a multi-platform app, you can choose to share different events per platform with your network. This lets you:

• Set individual events to manage campaign strategies for each platform.
• Customize data sharing per platform.

Under Map subscription events, follow these steps to choose the subscription events you want to directly send to your network.

1. Select Map event.
2. In the Adjust event list, choose the Adjust event that you want to share with your network.
3. Under Partner event, you need to select the partner event that corresponds to the Adjust event.
   1. For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
      • Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
      • Select Use global mapping to map the same events for all platforms.
   2. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to.
4. Select Apply.

Now your network will receive subscription event data for each of your linked events.

Map parameters

You usually need to map parameters to share custom data with InMobi DSP.

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to InMobi DSP. This lets InMobi DSP 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 InMobi DSP, follow these steps.

1. Set up partner parameters within the Adjust SDK.
   • Check Before you begin for all SDK development platform links.
2. Under Set your data sharing options, select Parameters.
3. Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
   1. Select Map parameter.
   2. In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
   3. In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.

Configure your link and settings

You have the option to set your:

• Link structure
• User destinations
• Attribution settings

Create your link and share it with InMobi DSP

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 InMobi DSP.

Once you’ve created your link, share it with InMobi DSP for placement in campaigns.

List of all parameters forwarded to InMobi DSP

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