Overview

InMobi DSP is a mobile-first, in-app programmatic demand-side platform (DSP) offered by InMobi. Connect InMobi DSP to Branch to attribute clicks and installs and configure Postbacks.

For more information about integrating ad partners in general, visit our Ad Partner Integration Guide.

Note: this guide is for new Branch

Please note that this guide is about integrating InMobi DSP in the new Branch experience. For information on InMobi DSP in legacy Branch, visit our legacy guide.

Partner capabilities

Capability	Details
Company type	DSP
Deep linking	Supported
Attribution	Click-through attribution, View-through attribution
Ad campaign types	Acquisition campaigns, Retargeting campaigns
Ad formats	Banner, Interstitial, Video, Recommendation, App of Day
Click types	Client-side click, Server-side click
Supported platforms	iOS, Android
Link wrapping	Not supported
Cost ingestion support	Not supported
Pricing models	CPI, CPC, CPM, CPA

Before you begin

To set up the InMobi DSP integration, you need:

• Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See Branch pricing or contact your Branch representative.
• A Branch account with access to Configuration > Ad Partners and admin permissions to enable and configure integrations.
• An InMobi DSP account with admin access. You'll need the following credentials, available from your InMobi DSP account manager: iOS Property ID, Android Property ID.

Enable InMobi DSP

To begin, navigate to Configuration > Ad Partners > InMobi DSP.

Enter your iOS Property ID, Android Property ID, then select Enable InMobi DSP on the InMobi DSP page. Contact your InMobi DSP account manager if you need these values.

Configure attribution

By default, InMobi DSP uses your global app attribution settings. To set attribution windows specific to InMobi DSP, enable the Override global app settings toggle on the Attribution windows tab.

For more information, follow Configure attribution in the general Ad Partner Integration Guide.

Configure postbacks

Enabling InMobi DSP automatically activates postbacks, including INSTALL and OPEN. The default postback URL template is:

http://advertiser.inmobiapis.com/tpce/v1/events/download?requestId=${ (id)! }&propertyId=<#if (user_data.os)! == "IOS">${ad_network.credentials.ios_pid}<#elseif (user_data.os)! == "ANDROID">${ad_network.credentials.and_pid}</#if>&appId=<@loop data=app.app_bundles val="bundle"><#if user_data.os == bundle.os><#if bundle.os=="ANDROID">${(bundle.android.package_name)!}<#elseif bundle.os == "IOS">${(bundle.ios.bundle_id)!}</#if><@break/></#if></@loop>&country=${ (user_data.geo_country_code)! }&dnt=<#if (user_data.limit_ad_tracking)! >1<#else>0</#if>&ida=${ (user_data.idfa)! }&gpId=${ (user_data.aaid)! }&deviceIp=${ (user_data.ip)! }&useragent=${ (user_data.user_agent)! }&deviceBrand=${(user_data.brand)!}&networkType=${(user_data.internet_connection_type)!}&carrier=${(user_data.carrier_name)!}&impId=${ (last_attributed_touch_data.~click_id)! }&trackingPartner=branch&eventTime=${ timestamp }&deviceName=${(user_data.model)!}&appVersion=${ (user_data.app_version)! }&firstevent=<#if (first_event_for_user)?? && first_event_for_user>1<#else>0</#if>&eventName=${ (name)! }&purchaseValue=${ (event_data.revenue)! }&purchaseCurrency=${ (event_data.currency)! }&isViewThrough=<#if (last_attributed_touch_type)! == 'IMPRESSION'>1<#else>0</#if>&ios_pid=${ (ad_network.credentials.ios_pid)! }&and_pid=${ (ad_network.credentials.and_pid)! }&deviceType=${ (user_data.model)! }&idv=${ (user_data.idfv)! }&os=${ (user_data.os)! }&osVersion=${ (user_data.os_version)! }

To add postbacks for additional events or to customize behavior, follow Configure postbacks in the general Ad Partner Integration Guide.

Create a Branch Ad Link

Create a Branch Ad Link to use in your InMobi DSP campaigns. Branch uses the link to attribute clicks and deep link users into your app.

Follow Create Ad Links.

Verify your data

After your integration is connected and events are flowing, you can verify data is reaching Branch:

• In Branch Liveview: confirm that events from your app appear in real time. This is the fastest way to confirm SDK events are firing.
• In Branch Analysis dashboards: review attributed installs and events where Ad Partner Name = InMobi DSP.
• In InMobi DSP: confirm that forwarded events are appearing in your InMobi DSP attribution reporting.

Data mappings

Campaign data

Branch populates the following fields from InMobi DSP campaign data.

Branch field	Partner data
~advertising_partner_name	"InMobi DSP" (static)

Link parameters

By default, Branch automatically appends these link parameters to InMobi DSP ad links. When a user clicks the link, InMobi DSP provides the corresponding values, which Branch ingests and uses for attribution and reporting.

Branch parameter	Link placeholder
Click ID	$IMP_ID
Campaign	$CAMPAIGN_NAME
Campaign ID	$CAMPAIGN_ID
Ad Set Name	$STRATEGY_NAME
Ad Set ID	$STRATEGY_ID
Creative Name	$CREATIVE_NAME
Creative ID	$CREATIVE_ID
Click ID	$IMP_ID
Click AAID	$GPID
Click IDFA	$IDA
Secondary Publisher	$SITE_NAME
Secondary Publisher ID	$SITE_APP_ID
Click IP Address	$USER_IP
Click User Agent	$UA