AI Search

Campaign Types

InMobi Exchange uses the ext.campaigntype signal in the bid response to classify campaign intent and tailor the ad experience accordingly. This drives campaign-aligned creative rendering — adjusting CTAs, end cards, deep linking behavior, and store overlay logic based on the campaign type provided by the DSP.

Supported Campaign Types

DSPs must pass ext.campaigntype in BidResponse.seatbid.bid.ext to correctly route the user experience.

Campaign Type Value Description
User Acquisition 0 Ensures an install-focused user experience with accurate conversion tracking. CTA: "Get App".
App-to-App Retargeting 1 Activates deep-linking workflows so that returning users land on contextually relevant in-app experiences. Improves ROAS by optimizing re-engagement loops and enabling precise post-install navigation logic. CTA: "Open App", "Tap to Resume".
Brand Awareness 2 Delivers awareness-first creatives and suppresses performance optimizations that misalign with brand KPIs. Prioritizes message delivery, completion, and viewability over click-through, so click-maximizing behaviors are not applied. CTA: "Brand Message", or no CTA.
App-to-Web Commerce 3 Flags awareness-focused flows and directs users to web product landing pages, preventing install-centric optimization misalignments. CTA: "Visit Site".

UX Changes for Retargeting Campaigns

When ext.campaigntype: 1 is passed, InMobi Exchange automatically adjusts the ad experience to support in-app re-engagement.

  • Android & iOS:
    • CTA updates from "Get App" To "Open App".
    • Endcard CTA text updates from "Get App" to "Open App".
    • Any user clicks leads directly into the app via deep link - not Playstore or Appstore.
  • iOS:
    • SK Store is disabled to maintain smoot in-app return flow.

On This Page

Last Updated on: 26 Aug, 2026