AI Search

Android Inline Installs

Overview

Android Inline Installs is a Google Play-powered capability enabled by the InMobi SDK that allows users to install an advertised app directly within the ad experience, without redirecting to the Google Play Store.

This experience leverages the Google Play Install API to present app product details in a native, in-context interface, allowing users to complete the install flow without leaving the host app.

For DSPs and advertisers, this results in a more seamless user journey, reducing friction in the clickthrough flow and improving key metrics such as conversion rate, and overall campaign efficiency (IPM, CPA, CPI).

The integration follows a two-sided OpenRTB handshake:

  • Bid Request: InMobi signals availability using imp.ext.inlineinstallallowed
  • Bid Response: DSP enables the feature and passes an install referrer using seatbid.bid.ext.inlineinstall

Note

InMobi can also enable this feature on behalf of DSPs that do not support RTB based activation or install referrer based attribution. Please contact your Demand Partner Manager to discuss enablement.

Requirements

InMobi sets inlineinstallallowed = 1 only when all of the following conditions are met:

  • Device OS is Android
  • Google Play Store is installed and reachable
  • InMobi SDK version is 11.1.0 or higher

Bid Request

Object: BidRequest.imp.ext

Field Type Required Description
inlineinstallallowed integer Yes 1 = available, 0/ absent = not available

Example

"ext": {
  "inlineinstallallowed": 1
}

Bid Response

Object: BidResponse.seatbid[].bid[].ext.inlineinstall

Field Type Required Description
enabled boolean Yes 'true' to activate, false to opt out (default value is 'true').
referrer string No* Referrer string passed by the SDK to the Play Install API for attribution. * Strongly recommended.

Example

"ext": {
  "inlineinstall": {
    "enabled": true,
    "referrer": "dsp1_760a59d6-1507-11f1-96c3-9565488fcc70"
  }
}

Note

bid.bundle (the advertised app's package name) is required when enabled=true.

Referrer and Attribution

The InMobi SDK calls the Google Play Install API directly on the device. The flow bypasses the Play Store redirect entirely, which means:

  • There is no redirect URL for referrer parameters to be appended to.
  • There is no redirect chain for MMPs to read.

You must pass the referrer explicitly in the bid response for attribution.

Without a referrer:

  • The install reaches the app with no referrer string.
  • Attribution will be missed for the ad.
  • MMPs may record the install as organic or unattributed.
  • Campaign reporting (ROAS and conversions) becomes incomplete.

We recommend passing the install referrer explicitly in the bid response for attribution. If the DSP does not use Install Referrer for third-party attributions, then this recommendation may not be relevant for you. 

Note

InMobi passes the referrer to the Google Play Install API exactly as received. It does not validate or modify the value.

FAQs 

1. Is the referrer field required?

The referrer field is optional at the protocol level. However, it is strongly recommended for any campaign where you need install attribution. Since the InMobi SDK calls the Play Install API directly (rather than redirecting through a Play Store URL), there is no redirect chain for the MMP to read a referrer from. The only way to pass a referrer in this flow is explicitly through this field.Without it:

  • The app will be installed with no referrer string.
  • Your MMP might rely on a different attribution method, which is likely not deterministic.

2. What happens if I send enabled=true on an impression where inlineinstallallowed was not set?

If inlineinstallallowed is absent or set to 0 in the bid request, the device is not eligible for Inline Install. Setting enabled=true in the bid response will have no effect — the InMobi SDK will fall back to standard store redirect behaviour. DSPs should treat inlineinstallallowed = 1 as a prerequisite before activating Inline Install.

3. What is the auto opt-in setting, and how does enabled=false interact with it?

InMobi may enable automatic Inline Install opt-in for DSPs who have agreed to it. When auto opt-in is active, eligible impressions will be treated as opted-in by default, even without an explicit enabled=true in the bid response.

To override this and explicitly opt out of Inline Install for a specific bid, set enabled=false in the bid response extension.

4. Is bid.bundle required when activating Inline Install?

Yes. When enabled=true, DSP must include a valid bid.bundle in the bid object. This is the Android package name of the app to be installed (e.g. com.advertiser.game). The SDK uses this to identify the app on the Play Store. Bids with enabled=true and a missing or invalid bundle will not be processed for Inline Install.

5. Will a click be reported back to the DSP and advertiser if the user sees Inline Install?

Yes, click trackers will be invoked as usual when the user clicks on the ad.

On This Page

Last Updated on: 15 Apr, 2026