> For the complete documentation index, see [llms.txt](https://help.branch.io/llms.txt).

# Enable InMobi (New)

> Integrate InMobi with Branch for effective in-app advertising, enabling click attribution, postbacks, and campaign management to engage mobile consumers.

## Overview

[InMobi](https://www.inmobi.com) is a global marketing cloud that helps brands reach and engage mobile consumers through in-app advertising. Connect InMobi to Branch to attribute clicks and installs, forward conversion events, and configure Postbacks.

For more information about integrating ad partners in general, visit our [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

> **Note: this guide is for new Branch**
>
> Please note that this guide is about integrating InMobi in the [new Branch experience](https://help.branch.io/marketer-hub/new-branch-overview.md). For information on InMobi in legacy Branch, visit our [legacy guide](https://help.branch.io/marketer-hub/inmobi.md).

### Partner capabilities

| Capability | Details |
| --- | --- |
| Company type | Non-SAN ad network |
| Deep linking | Supported |
| Attribution | Click-through attribution, View-through attribution |
| Ad campaign types | Acquisition campaigns, Retargeting campaigns |
| Ad formats | Banner, Interstitial |
| Click types | Client-side click, Server-side click |
| Supported platforms | iOS, Android |
| Link wrapping | Not supported |
| Cost ingestion support | Not supported |
| Pricing models | CPC, CPM |

## Before you begin

To set up the InMobi integration, you need:

- Ad partner integrations enabled for your Branch account. Availability varies by Branch plan. See [Branch pricing](https://www.branch.io/pricing/) or contact your Branch representative.
- A Branch account with access to **Configuration > Ad Partners** and admin permissions to enable and configure integrations.
- The Branch SDK implemented in your app ([iOS](https://help.branch.io/developer-hub/ios-sdk-overview.md) | [Android](https://help.branch.io/developer-hub/android-sdk-overview.md)) with [event tracking](https://help.branch.io/developer-hub/track-branch-events.md) configured.
- Your InMobi **iOS Property ID** and **Android Property ID**. Contact your InMobi account manager to obtain these values.
- Active campaigns running in InMobi.
- [PAM](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md) enabled (recommended).

> **Note: PAM uses two separate toggles**
>
> The **PAM for Publishers** toggle for this partner, found under **Partner settings** > **Manage account**, is separate from the account-level **PAM switch**. **PAM for Publishers** must be enabled to reconcile conversion events with your partner. To attribute events with PAM, you also need PAM enabled on the [Attribution page](https://help.branch.io/account-hub/attribution-page-new.md) under **Configuration** > **Attribution**. Learn more in our [PAM Overview](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers).

## Enable InMobi

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

Before postbacks can fire, you must enter your InMobi property IDs:

1. Select **Partner settings** to open the **Manage account** dialog.
2. Under **Postback Credentials**, enter your **iOS Property ID** and **Android Property ID**. These values are automatically included in your postbacks.
3. Select **Save**.

Once your credentials are saved, the Postbacks status on the Status tab will update from **Needs Setup** to **Enabled**.

(Recommended) You can also optionally enable the **PAM for Publishers** privacy setting in the Manage account dialog. When enabled, [PAM for Publishers](https://help.branch.io/marketer-hub/predictive-aggregate-measurement.md#pam-for-publishers) removes advertiser-specific user identifiers from postbacks for users who haven't opted in via Apple's App Tracking Transparency (ATT) framework, prioritizing identifiers provided directly by InMobi.

## Configure attribution

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

For more information, follow [Configure attribution](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-attribution) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Configure postbacks

Enabling InMobi automatically activates postbacks for `INSTALL`, `OPEN`, and `PURCHASE`. The default postback URL is:

```
https://advertiser.inmobiapis.com/tpce/v1/events/custom?ida=${ (user_data.idfa)! }&gpId=${ (user_data.aaid)! }&impId=${ (last_attributed_touch_data.~click_id)! }&eventTime=${ (timestamp/1000)?long }&trackingPartner=branch&attributed=<#if (last_attributed_touch_data.$3p)! == (ad_network.machine_name)!>1<#else>0</#if>&eventName=${ (name)! }&propertyId=<#if (user_data.os)! == "IOS">${ad_network.credentials.ios_pid}<#elseif (user_data.os)! == "ANDROID">${ad_network.credentials.and_pid}</#if>&purchaseValue=${ (event_data.revenue)! }&purchaseCurrency=${ (event_data.currency)! }&itemId=${(attributes.$itemid)!}&itemPrice=${(attributes.$price)!}&itemCurrency=${(attributes.$currency)!}&itemCount=${(attributes.$quantity)!}&itemCategory=${(attributes.$category)!}&itemName=${(attributes.$name)!}&productsList=<@urlencode><@jsonmap data=event_data></@jsonmap></@urlencode>&isViewThrough=<#if last_attributed_touch_type == "CLICK">0<#elseif last_attributed_touch_type == "IMPRESSION">1</#if>&deviceIp=${ (user_data.ip)! }&userAgent=${ (user_data.user_agent)! }&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>&appVersion=${ (user_data.app_version)! }&requestId=${ (id)! }&siteId=${ (last_attributed_touch_data.~secondary_publisher)! }&subSiteId=${ (last_attributed_touch_data.subSiteId)! }&deviceLanguage=${ (user_data.language)! }&deviceModel=${ (user_data.model)! }&osVersion=${ (user_data.os_version)! }&deviceBrand=${ (user_data.os)! }&ios_pid=${ (ad_network.credentials.ios_pid)! }&and_pid=${ (ad_network.credentials.and_pid)! }
```

To add postbacks for additional events or to customize behavior, follow [Configure postbacks](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md#configure-postbacks) in the general [Ad Partner Integration Guide](https://help.branch.io/marketer-hub/ad-partner-integration-guide-new.md).

## Create a Branch Ad Link

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

Follow [Create Ad Links](https://help.branch.io/marketer-hub/ad-links-new.md).

## Verify your data

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

- **In Branch** [**Liveview**](https://app.branch.io/testing-and-monitoring/events): 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**](https://help.branch.io/marketer-hub/analysis-dashboards-overview-new.md): review attributed installs and events where `Ad Partner Name = InMobi`.
- **In InMobi**: confirm that forwarded events are appearing in your InMobi attribution reporting.

## Data mappings

### Campaign data

Branch populates the following fields from InMobi campaign data.

| Branch field | Partner data |
| --- | --- |
| `~advertising_partner_name` | `"InMobi"` (static) |
| `~click_id` | impId |
| `~secondary_publisher` | siteId |