These are some common questions that publishers may have while implementing MSPA.

If you have additional queries or need further assistance, Contact Us. 

If you have additional queries or need further assistance, Contact Us.

If you have additional queries or need further assistance, Contact Us. 

If you have additional queries or need further assistance,  Contact Us.  

If you have additional queries or need further assistance, Contact Us.   

If you have additional queries or need further assistance, Contact Us.    

Introduction

InMobi provides a transparent bidding adapter for Prebid.js (client-side integration) and Prebid Server (server-to-server integration). As a Prebid-approved bidder, InMobi continuously updates its adapter with new features and enhancements.

Prerequisites

• InMobi's Prebid.js adapter is available on Prebid.js v9.20 and above.
• Your website must be integrated with Prebid.js. For setup details, see the Prebid.js documentation.
• Download the InMobi Prebid.js Adapter:
  1. Go to Customize and Download Prebid.js page.
  2. Select InMobi as the Bidder Adapter.
  3. Click Get Prebid.js to download the file.

Configure InMobi for Prebid.js

1. Create an InMobi Account: Sign up for an InMobi Supply Side Platform (SSP) account. For more information, see Create InMobi Account. If you already have an InMobi account, use the same credentials to monetize your web properties.
2. Add Your Website: Add your website(s) to the InMobi platform. For more information, see Add Inventory.
3. Create Placements:
   1. Search for the website where you want to create a placement.
   2. Click +Add a Placement.
   3. Select the ad unit (e.g., Banner, Video, or Native).
   4. Name your placement.
   5. Enable Audience Bidding by turning the toggle ON.
   6. From the Partner dropdown, select Prebid.
   7. Click Create Placements.

Add InMobi to Your Prebid Setup

To configure InMobi in your Prebid.js setup:

1. Configure the placement ID on InMobi’s adapter. For more information, see InMobi Prebid Bidder Page.
2. Map the InMobi Placement ID to the corresponding ad format and website in your Prebid.js configuration. Start sending requests from your Prebid.js setup to InMobi.

This topic explains dimensions, metrics and filters such as visits, sessions/consent screen displays, and consent status on the InMobi CMP Analytics dashboard. 

Session/Consent Screen Display

A Session/Consent Screen Display is an instance where a user is prompted through a popup screen to manage their data privacy preferences when they access a website or application. This screen typically appears during the initial visit or when a new consent action is required due to policy changes, regulatory updates, or session expiry.

For example, when a user visits a website for the first time. The CMP displays a consent screen to manage privacy settings. It would be counted as one session/consent screen display. 

Visit

A Visit occurs whenever a user interacts with a website or application. 

For example, a visit begins when a user accesses a website or app for the first time. 

Additionally, if a user visits a website or an app, and comes back after 30 mins of inactivity, this would count as another visit.

In a third scenario, if a user visits a website or app, leaves, and returns the next day (UTC) of their previous visit, this would also be counted as a separate visit.

Consent States

Consent States are reflected differently for each regulation such as GDPR, CCPA, and GBC in InMobi CMP. The following table shows how you can select consent states for each regulation for analytics purposes.

 Consent or Pay Enabled

Consent or Pay Enabled is a dimension and filter provided by InMobi CMP allowing you to view analytics only for the sites for which Consent or Pay has been enabled by you. This is a convenient option as it saves you the time of selecting each site while generating reports. 

Paid User

Paid user is a metric enabling you to view analytics for only paid users and understand their user behavior and patterns for your site. 

This document outlines common errors encountered during Android SDK implementation, along with their causes and solutions. It aims to help developers troubleshoot issues quickly and ensure seamless integration.

1. Errors in oncmpError callback

One of the callbacks within ChoiceCMPCallback is onCmpError, which gets fired whenever there’s an issue in CMP. This function has a parameter: error which contains information about the error that has occurred.

Here’s a list of error messages that error can have:

 2. Errors that appear in console

Debug and Error Logs are logged in the console to track any misbehavior or errors in SDK. Here's a list of Error Logs and their description:

3. Info messages that appear in console

Info messages are logged in console to convey meaningful messages in SDK. Here is a list of those messages and description:

This document outlines common errors encountered during iOS SDK implementation, along with their causes and solutions. It aims to help developers troubleshoot issues quickly and ensure seamless integration.

1. Errors in cmpDidError delegate

One of the delegate functions within ChoiceCMPDelegate delegate is cmpDidError which gets fired whenever there’s an issue with the initialisation due to any reason. This function has a parameter: error which contains information about the error occurred.

Here’s a list of error messages that error.localizedDescription with have:

 2. Errors that appear in console

Debug and Error Logs are logged in console in order to track any misbehaviour or errors in SDK. Here's a list of Error Logs and their description:

This topic explains the concept of Concept or Pay and how publishers can honor end-user consent preferences by giving them a free opt-out option to limit data tracking.

What is Consent or Pay?

“Consent or Pay" is a concept where users are given a choice to either provide consent for data collection or pay to access content without consenting to data tracking or advertising. The three main options are:

• Consent: This is the option for users to allow the collection, processing, and sharing of their personal data in exchange for free access to a website or service. CMPs typically collect and store users' consent choices for compliance with privacy regulations, such as GDPR or CCPA. By providing consent, users allow consent for different data processing purposes as selected by the publisher on their and their vendor’s behalf. 
• Pay: This option is an alternative for users who prefer to completely opt out of any data processing. Instead of consenting to data collection, users can choose to pay a fee for an ad-free experience or access to premium content without any data tracking. This allows users more control over their privacy.
• Free Partial Accept: The European Data Protection Board (EDPB) has released an opinion citing that publishers must provide a “Free alternative to opt-out of personalized advertising”. Under this, InMobi CMP enables a Free partial accept option which allows end-users to opt out of personalized ads if they so choose. This way, InMobi’s solution remains compliant with EDPB's opinion on this topic.

Developments so far 

In November 2023, Meta introduced a paid subscription for Instagram and Facebook users who don't want to be tracked. This was referred to as the 'Pay or okay' model. ​

In response to this, the European Data Protection Board (EDPB) has published an opinion stating the following:​

“In most cases, it will not be possible for large online platforms to confront users only with a binary choice”.​

A free alternative should be given without behavioral advertising, e.g. involving the processing of less or no personal data.​

The scope of this opinion is for “large online platforms“ (evaluated on a case-by-case basis)​.

Consent or Pay 2.0

Consent or Pay 2.0 emerged after the EDPB's guidance to offer users a free opt-out of personalized ads.

Consent or Pay 2.0 Checklist 

• Partial Accept is mandatory (Reject all will be behind pay-wall). Users will be able to opt out of personalised ads.​ This is the main differentiator from the 1.0 version of Consent or Pay which only had a binary choice.
• At least one non-personalized purpose should be available to empower users to opt out of personalized ads​. This is also a check maintained by InMobi CMP on behalf of publishers. 
• Multiple implementation options for publishers:​
  • Option 1: Publishers can use CMP’s consent call-backs to re-direct the user themselves based on the consent state (Accept All, Reject All, etc).​
  • Option 2: Publishers can simply provide the re-direction URLs (web) in the CMP which does the re-direction​
• Balance publisher control vs. standardization for button copy (button labels), consent screen text, and language translations.​
• Provide publishers control to implement consent or pay in only certain countries but not in other countries.

This documentation outlines implementing the Consent or Pay model with InMobi CMP. InMobi CMP enables publishers to provide a free option to opt out of data tracking and receiving personalized ads with the Partial Accept option. For more information on Consent or Pay, see Overview.

Portal Configuration

1. To start, login to your InMobi CMP account here.
2. On the Properties page, select the property you wish to enable Consent or Pay for, and click the edit icon.

   

3. On the General Settings page, scroll down to ENABLE CONSENT AND PAY and select Yes.

   

4. On the pop up, select the countries where you want to implement Consent or Pay and the redirection URL settings.

   

   Note

   Consent or Pay will only be implemented for the selected countries. For the remaining countries, GDPR will apply.

5. Select OK to save your settings.

Themes 

Configuring Themes settings allows you to manage the look and feel of the consent screen.

1. Navigate to the Themes tab on the top of the page and click the edit icon next to the desired property.

   

2. Under Configure your theme, go to Consent and Pay Settings.

   

3. Choose the languages in which you wish to translate the consent screen and button texts.

   

4. Next, select the layout for your screen and buttons. InMobi CMP offers two layouts with the 'Subscribe' and the 'Subscribe and Login' buttons respectively.

   

5. Edit the button and consent screen texts as per the languages chosen earlier.

   

   Note

   Certain sections of the CMP banner text (L1, L2, L3, and L4) must remain unchanged to ensure compliance with IAB-TCF guidelines. However, you can add content before, after, or between these sections without requiring approval. If you attempt to edit these sections, a structured review request process will be triggered to ensure flexibility for you to have desired content but as per IAB guidelines.

6. To request a text change, click Need Changes? Request here. Add details of the required text changes and reason for change. 

   

   Note

   Once the request is raised:

   • You will receive an acknowledgment via email and a unique Ticket ID will be generated.
   • You cannot raise another request while one is in progress.
   • If they text is approved, you cannot raise another request for the next 15 days.
   • The advanced customizations will remain unaffected during the review process and will continue to have default text/settings.
   • You will see the updated consent banner text once it is updated from the backend after approval.
7. Click View Submitted Requests to view requests and their status.

   

8. Add your required footer links in the Custom Footer Links field.

   

9. Click Save Theme on the top of the page to save your settings.

   

SDK Implementation

 Android

For Android implementation and SDK-related changes, see Android.

iOS

For iOS implementation and SDK-related changes, see iOS. 

Web

For Web APIs, see Handling Consent APIs.

This document details the APIs to enable Consent or Pay on your app or website.

Android

1. To provide the login/subscription status to the CMP, use the following API with the appropriate value:

   Kotlin

   ChoiceCmp.setUserSubscriptionStatus(SUBSCRIPTION_STATE)
   

   Java

   ChoiceCmp.setUserSubscriptionStatus(SUBSCRIPTION_STATE);
   

    

   Note

   We recommend you use this API:

   • Just before initialising the SDK.
   • Once the login/subscription process is completed through the CMP. This enables the CMP to know the new status.
2. The method onActionButtonClicked will be triggered when the user clicks any of the Action buttons. The parameter actionButton will contain the info about whether it’s ActionButton1 or ActionButton2.

   Kotlin

   override fun onActionButtonClicked(actionButton: ActionButton) {
      /* code */
   }
   

   Java

   @Override
   public void onActionButtonClicked(@NonNull ActionButton actionButton) {
       // code
   }
   

iOS

1. To provide the login/subscription status to the CMP, use the following API with the appropriate value: 

   Objective-C

   [[ChoiceCmp shared] setUserLoginOrSubscriptionStatus:(BOOL)];
   

   Swift

   ChoiceCmp.shared.setUserLoginOrSubscriptionStatus(Bool)
   

    

   Note

   This API is recommended to be used:

   • Just before initialising the SDK (calling startChoice API).
   • Once the login/subscription process is completed through the CMP. This updates the status to the CMP.

   Objective-C

   - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
       // Initialise InMobiCMP
       [[ChoiceCmp shared] setUserLoginOrSubscriptionStatus:true];
       [self startChoice];
       return YES;
   } 
   

   Swift

   @main
   class AppDelegate: UIResponder, UIApplicationDelegate, ChoiceCmpDelegate, CCPADelegate {
       func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
           ChoiceCmp.shared.setUserLoginOrSubscriptionStatus(true)
           ChoiceCmp.shared.startChoice(pcode: "< YOUR PCODE >", delegate: self)
           return true
       }
   } 
   
   

    

2. Implement the following delegate function to receive the ActionButtons update.

   Objective-C

   (void) didReceiveActionButtonTapWithAction:(enum ActionButtons)action {  
     switch (action) { 
       case ActionButtonsAction1: 
       // Your implementation here.. 
       break;
       
       case ActionButtonsAction2: 
       // Your implementation here.. 
       break; 
       
       default:
       break; 
       } 
   } 
   

   Swift

   func didReceiveActionButtonTap(action: ActionButtons) {
     switch action {
       case .action1: 
       // Your implementation here..
       
       case .action2:
       // Your implementation here.. 
       } 
      } 
   
   

3. The method didReceiveActionButtonTap will be triggered when the user clicks any of the Action buttons. The parameter actionButton will contain the info about whether it’s ActionButton1 or ActionButton2.

   Objective-C

   (void) didReceiveActionButtonTapWithAction:(enum ActionButtons)action {  
     switch (action) { 
       case ActionButtonsAction1: 
       // Your implementation here.. 
       break;
       
       case ActionButtonsAction2: 
       // Your implementation here.. 
       break; 
       
       default:
       break; 
       } 
   } 
   

   Swift

   func didReceiveActionButtonTap(action: ActionButtons) {
     switch action {
       case .action1: 
       // Your implementation here..
       
       case .action2:
       // Your implementation here.. 
       } 
      } 
   

    

   Note

   If the user has consent or pay enabled, moves to more options screen, then rejects all the consents, and then saves and exits, it will be treated as action button 1 press, and the same delegate will be called with ActionButton value as action1.

Web

Signaling User Subscription Status to the CMP

To indicate whether the user is subscribed, the publisher can set a JavaScript variable in the global window object. This can be used by the Consent Management Platform (CMP) to determine whether or not to display the consent popup.

Method:

window.__user_status = 'subscribed';

• If the user is subscribed, the CMP will detect this signal and will not display the consent popup.
• Additionally, the CMP will automatically store the consent status as reject since the user has already made a subscription decision.

Workflow:

1. The publisher sets window.__user_status = 'subscribed'; when a user is confirmed to be subscribed.
2. The CMP reads this signal upon initialization.
3. If the user is subscribed (i.e., window.__user_status === 'subscribed'), the CMP skips the consent popup display.
4. The CMP registers the consent status as "reject" (no further consent required).

Advanced customization lets you modify the text for your GDPR consent screen and buttons in different languages.

Advanced Customization Settings

1. Login to your InMobi CMP account here. 
2. Navigate to the Themes tab on the top of the page and click the edit icon next to the desired property.

   

3. Under Configure your theme, go to Advanced Customization.

   

4. Choose the languages in which you wish to translate the consent screen and button texts.

   

5. Under Customise Content, edit the button and consent screen texts as per the languages chosen earlier.

   

   Note

   Certain sections of the CMP banner text (L1, L2, L3, and L4) must remain unchanged to ensure compliance with IAB-TCF guidelines. However, you can add content before, after, or between these sections without requiring approval. If you attempt to edit these sections, a structured review request process will be triggered to ensure flexibility for you to have desired content but as per IAB guidelines.

6. To request a text change, click Need Changes? Request here. Add details of the required text changes and reason for change. 

   

   Note

   Once the request is raised:

   • You will receive an acknowledgment via email and a unique Ticket ID will be generated.
   • You cannot raise another request while one is in progress.
   • If they text is approved, you cannot raise another request for the next 15 days.
   • The advanced customizations will remain unaffected during the review process and will continue to have default text/settings.
   • You will see the updated consent banner text once it is updated from the backend after approval.
7. Click View Submitted Requests to view requests and their status.

   

8. Add your required footer links in the Custom Footer Links field.

   

9. Click Save Theme on the top of the page to save your settings.

   

Ads.txt (Authorized Digital Sellers) is an IAB Tech Lab initiative. It is a simple, flexible, and secure method that you can use to publicly declare the companies you authorize to sell your digital inventory. 

During the real-time bidding process, the ad monetization space saw fraud in ad inventory offered to buyers with a misrepresented label and account. Typically, the webpage's domain, or the mobile app's ID, has been falsified to look like a site or app they do not have authorization to sell. Ads.txt and App-ads.txt enable buyers to spend only programmatic dollars through channels explicitly trusted and authorized by the originating publisher.

Create ads.txt File at the Root level of Your Website

Create your ads.txt file using the following file format and data record:

File Format

Data encoding details:

• Use 'text/plain' as the HTTP content type; treat other types as errors.
• Core syntax: Comma-separated format with three fields per line.
• Records are separated by an end-of-line marker.
• Records follow a specific line format.
  • <FIELD #1>, <FIELD #2>, <FIELD #3>, <FIELD #4>
    placeholder.example.com, placeholder, DIRECT, placeholder

Add Your Personalized Code Snippet

For the ads.txt setup, you must ensure to:

• Add business/payment info to generate entries. For more information, see Payment Settings.
• Use InMobi's personalized ads.txt entries.
  • Inmobi's line: This a mandatory line to be included in your ads.txt file to authorize Inmobi to sell your inventory.
  • Priority lines: This list includes the above mandatory line and the reseller lines to help you achieve optimal monetisation through Inmobi.
  • Maximum lines: This list includes Inmobi's line and all the reseller lines suggested by Inmobi to maximize your earning potential on Inmobi's platform.
• Append entries to your ads.txt file.

Follow the instructions below to get your personalized ads.txt entries, which include your InMobi payment ID:

1. Log in to InMobi.
2. Navigate to Inventory >> ads.txt.
3. Scroll down and download the ads.txt file.
4. Post the file in your website's root directory.
5. Ensure correct formatting and line breaks after updating InMobi’s entries into your ads.txt file.

Publish ads.txt File on your Website

InMobi's ads.txt crawler locates your file using the website URL provided for that inventory on the dashboard. Per ads.txt specs, the crawler checks the file at:

• https://<<hostname>>/ads.txt
• http://<<hostname>>/ads.txt

Determine the hostname from your website URL. It's the website's root domain, as explained below.

Refer to the table for examples where the InMobi crawler checks for an ads.txt file based on different website root domains.

The ads.txt specification outlines rules for root domains and subdomains. Crawlers will explore up to five redirections within a root domain and one outside the root domain.

To verify correct publication, ensure the ads.txt URL displays its content when accessed through your web browser. If it is visible in your browser, crawlers will probably locate it successfully.

Ensure Crawlable ads.txt File

Ensure the ads.txt is accessible via both HTTP and HTTPS.

Check Verification Status of ads.txt File

Monitor your ads.txt files in your InMobi account:

1. Log in at https://publisher.inmobi.com/.
2. Navigate to Inventory on the left menu.
3. Select ads.txt.
4. After you add the ads.txt with seller information, you can view the verification status loading below.

If your file wasn't located or verified, review the details in your InMobi account or explore troubleshooting tips for ads.txt issues.

First-time Setup Process

Upon creating your account on InMobi and establishing your inventory, access the verification status through Inventory >> ads.txt. Activation of the InMobi crawler occurs once any of the added apps has generated 10 thousand bid requests.

This topic explains GPP, its relevance for publishers to stay compliant with different regulations, and how InMobi Ad Exchange supports GPP through SDK and API integrations.

What is GPP?

The Global Privacy Platform (GPP) by the Interactive Advertising Bureau (IAB) is a standardized global framework for managing user consent in digital advertising. For more information, see GPP.

Why is it relevant to U.S. Privacy?

The GPP aims to simplify the conveyance of privacy, consent, and consumer choice signals from websites and applications to ad tech vendors. It empowers advertisers, publishers, and technology vendors to align with regulatory requirements globally. 

The GPP centralizes the management of diverse consent signals from various global privacy jurisdictions and additionally accommodates the Global Privacy Control (GPC), a browser-level signal enabling individuals to opt out of information sale or sharing. The GPP currently supports consent strings for the US Privacy and IAB Europe TCF.

The US Privacy String has been deprecated as of April 30, 2024. The legacy US Privacy signal does not support the four US states privacy signals —VA, CO, CT, and UT. For CCPA, only a few of the required consents are supported. In contrast, the new state signals for the other four states will only be supported by the GPP. 

How does InMobi support GPP?

InMobi Ad Exchange now supports GPP through InMobi SDK and API integrations. 

For SDK integrations, the app can store the GPP strings in Shared Preferences for Android and Managed under the key names for iOS, prescribed by IAB: The key names are : IABGPP_HDR_Version, IABGPP_HDR_Sections, IABGPP_HDR_GppString, IABGPP_GppSID. For more details, see In-App Key Names.

For API integration, you can now send GPP strings via regs → ext → gpp or directly under regs: regs → gpp.

InMobi Performance Solutions offers machine learning-powered end-to-end mobile performance advertising solutions through: 

• Programmatic buying on the open internet via InMobi DSP 
• Direct buying on InMobi’s owned and operated consumer platform, Glance 

The platform supports managed media buying and trading services, offering features such as ad serving, bidding, user signal enrichment, fraud prevention, brand safety, as well as comprehensive reporting and tracking. These services leverage unified audiences across InMobi’s owned and operated content platform, Glance, along with major ad exchanges like Google Ad Exchange, InMobi Exchange, AppLovin, Unity, Vungle, Digital Turbine, PubMatic, Chartboost, BidMachine, and others. 

Glance provides consumer content inventories on the lock screens of popular Android devices, including those from Xiaomi, Realme, Samsung, Vivo, Motorola, and more. 

The InMobi DSP supports the latest attribution frameworks, including SKAN, and integrates with leading Mobile Measurement Partners (MMPs) such as AppsFlyer, Adjust, Branch, Kochava, Singular, Airbridge, and Tenjin. Glance also offers integration with top MMPs to enhance attribution accuracy. 

In addition, the InMobi DSP provides a reporting dashboard and Cost API integration, allowing you to customize and access reports according to your specific needs. 

InMobi DSP topics

• InMobi DSP Overview
• Audience targeting
• Creative guidelines and specifications
• Ensuring fraud-free campaigns
• Pricing models
• Onboarding requirements
• MMP Integrations
• Audience segmentation and ingestion
• Reporting
  • Reporting dashboard
  • Cost API Integration
• Best Practices for InMobi DSP Campaigns

This page offers comprehensive instructions for implementing the InMobi CMP on a website using Google Tag Manager (GTM). This process uses a custom HTML GTM tag and additional GTM variables and triggers/trigger groups. Before finalizing your GTM setup, complete the site and consent configurations. 

Assumptions

• You have an InMobi CMP account with your website added and configured.
• The website where InMobi CMP will be added has GTM installed.
• This guide assumes that you import the provided GTM container file into your GTM environment to import the custom HTML tag and necessary variables and example triggers. We recommend that you import and merge the provided container into your existing container, creating a new workspace.

Method 1: Add InMobi CMP with GTM (JSON Container Import)

Importing the GTM InMobi Choice TCFv2 container is the most reliable way to add the custom HTML tag, all of the necessary variables, and sample triggers you can use to configure your container for consent management easily.

Download the GTM Container Import - Tag and Variables. Store it in a local directory on your computer.

1. On the Google Tag Manager user interface, click Admin in the top navigation.
2. In the Container column, click Import Container.

   

3. In the view that opens, click Choose container file.
4. In the file selector, browse the GTM-CONTAINER-IMPORT.json file in your local directory and select it for importing.
5. Choose to create a New workspace with the import or to merge it into an existing workspace. It is recommended to create a new workspace for this import.
6. In the overlay that opens, give the workspace a descriptive name.
7. Click Save in the top right corner to save the new workspace.
8. Choose Merge as the import option, and select Overwrite conflicting tags, triggers, and variables.
9. Verify that the import options are all fine. You can click View detailed changes to see what will happen when you confirm the integration.
10. Click Confirm when ready to import the container to the new workspace you created.

You have now added all the necessary tags, triggers, and variables to get you started. You will have to configure some variables, and you will have to create new triggers to enable consent management in the container. The next chapter will explain this process in more detail. 

InMobi CMP GTM Configuration

Here are the steps you need to take to configure the InMobi CMP web tag, and to create and modify the triggers and variables you’ll need for the integration to work.

1. Set the InmobiChoice - UTID constant value. Browse Variables in your container, and open up the InmobiChoice - UTID variable. Set the value to your UTID (pCode).
2. If subdomains are not selected, this value is False by default. Otherwise, a valid domain should be entered.

Google Advanced Mode Implementation

For publishers using our GTM implementation, there is an option to load default consents immediately after consent initialisation without waiting for page load event. To enable the same, follow the steps below:

1. Download the updated GTM Container Import file.
2. Follow the steps to upload this updated GTM container file into your GTM (See Add Choice with GTM (JSON Container Import). If you wish to add this change to your existing InMobi CMP GTM implementation, merge it to your existing workspace as described in step 5. If you overwrite it, you must define the UTID and datalayer push variables again.
3. Go to Tags Configuration. Open Inmobi Choice GBC Template tag and edit the consent values.
4. Move the purposes under Granted Consent Types or Denied Consent Types as per your choice and separate them by a comma. Save these values and then the Tag.
5. Preview the changes and see the default consents defined as in the screenshot below:

    

   Note

   These default values are set by you separately at the GTM level. If you make changes to the default values in the UI, you need to change them here as well.

   Once set, your default consents will load immediately upon consent initialisation without waiting for page load event.

   Note

   This feature is available for only those sites which are using InMobi CMP’s GTM integration. For other integrations, default consents will load only after page load event.

Method 2: Add InMobi CMP with GTM Template

1. Navigate to Template in Google Tag Manager. Click Search Gallery inside Tag Templates. Type in InMobi CMP Template. Add to your GTM workspace.

   

2. Once you add the template, go to Tags and click New. Select Tag Configuration and choose Inmobi CMP Template under Custom.

   

3. Fill in the details required by the CMP Template. If you wish to override the template values with the portal values, select the "Do you wish to override the portal default consents with GTM template?" checkbox.

   

   

4. Once you fill in all the details, add the GTM trigger (Consent initialization – All Pages).
5. Preview the changes before publishing them.

   

Enable CCPA Support

• You must have CCPA enabled on the website add at choice.inmobi.com/protect.
• You need an html container with a unique ‘id’ attribute set (likely in the footer) where the CCPA message will be appended to on the page.
• You can learn more about the html id attribute here.
• This html id can be anything you choose (valid html id value) as long as the container id (on the page) matches the InmobiChoice - CCPA msg id value in GTM. In the screenshot below the container in the footer of the website has the id of ‘choice-footer-msg’ and since we also set the value of InmobiChoice - CCPA msg id in GTM the CCPA footer message was appended to the container with JavaScript. You may need to have your dev team add an empty container (with a unique html id) to the footer of your website where the CCPA message can be appended.
• Add the InmobiChoice - CCPA msg id constant value. This is the html id of the footer dom element where the CCPA message/popup link will be appended. (See the explanation above about how to find/get an HTML id attribute).
• Set the InmobiChoice - CCPA constant to true to enable, false to disable.
• If CCPA is successfully enabled on your website you will see the CCPA msg with a link Do Not Sell My Data link in the footer (or wherever your html id div from step 2 a is located on the page). 
• When clicking on the Do Not Sell My Data link in the CCPA footer message a modal should pop up.

Push consent signals to the data layer

Set the InmobiChoice DataLayer Push constant to true to automatically push consent signals for IAB Vendors, Non-IAB Vendors, Legitimate Interests, and Publisher Consents. 

Find Your P-CODE

To initialize the SDK, you must provide your account's p-code for proper identification. After you log in to the InMobi CMP portal, you can see the p-code at the top right corner of the screen. However, as shown below, you must omit the initial two characters ("p-") when copying the code for use elsewhere.

Banner Ads

• Recommended formats: PNG, JPEG
• Supported formats: PNG, JPEG, DDS, GNF, KTX, GIF, TIFF, BMP, TGA
• Recommended aspect ratios: 4:3, 3:4, 3:2, 2:3, 6.4:1, 16:9, 6:5, 8.09:1​

CBA restricted ad formats

• No flashing animated ads​ 
• No call to action/ad interaction e.g. “click here” For more information about the Coalition for Better Ads Standards, see The Better Ads Standards.

Video Ads

• Recommended format: MP4 using H.264 codec is the most optimal format. In addition,  the formats below are supported as well:​
  • Android: mp4, m1v, m2v, mp2, mpg, mpeg, m4v, mov, qt, 3gp, 3gpp, sdv, 3g2, 3gp2​
  • Apple (iOS/osx/tvos): mp4, m1v, m2v, mp2, mpg, mpeg, m4v, mov, qt, 3gp, 3gpp, sdv,  3g2, 3gp2​
  • Windows/Xbox/UWP: wmv, mp4, asf, mov​
  • PS4: m4v, mp4, mov​
• Video Length: 3 to 30 seconds (6-15 seconds has the best results)​
• Video file size: 15 MB or less (bigger sizes are supported but not recommended)​
• Supported video frame rate: 30 frames per second or less​
• Recommend audio sample rate: 48KHz or less​
• Recommend audio codecs: PCM / MP3 / AAC​
• Supported Video layout:  Horizontal and vertical​
• Recommended aspect ratios: 16:9, 4:3, 9:16, 3:4​
• CBA restricted ad formats:​
  • No use of sound in videos​
  • No countdown to ad start​
  • No call to action/ad interaction e.g. “click here” For more information about the  Coalition for Better Ads Standards, see The Better Ads Standards.

Welcome to InMobi

Your go-to resource center for effortlessly monetizing your apps and websites with InMobi is here. This comprehensive guide will take you through every step of the onboarding process—from creating and configuring your account to maximizing your earnings potential. You'll also find essential information on compliance initiatives and key guidelines to ensure successful and sustainable monetization as an InMobi publisher. 

Here is your onboarding checklist:

1. Create InMobi Account
2. Add Inventory
3. Configure Payments
4. Integration
5. Test Your Integration

For any assistance, contact us through the Chatbox or reach out to your Customer Success Manager.

Now, let's get started.

Create InMobi Account

Sign up

1. Click here to visit the Sign-Up page.

   

2. Select Create Account and fill in details such as your name, company name, email address, etc.

   

3. Click Create Account. You will receive a verification email from InMobi to same the email address you provided.

   Note

   If you are unable to find the verification email in your inbox, check your Spam folder. If you haven’t received it, click Resend Email on the Sign-Up page and enter your email address.

4. Click Get Started in the verification email. Your browser directs you to set your password.

   

5. Enter your new password and click Set password. Your browser redirects you to the InMobi Login/SignUp page.

   

You have successfully signed up with InMobi. You can now login to your account with your new credentials.

Log in

1. Click here to visit the InMobi Login/Signup page.
2. Click Log In.
3. Enter your email address and click Next.

   

4. Enter your password and click Log In. You will be redirected to the homepage outlining the main steps you need to follow to set up your account.

   

Add Inventory

You must add at least one placement and ad unit for your apps or websites to generate ad revenue. A placement is a place and time displayed on the ad in your app, and the ad unit is the ad format. It is recommended to create multiple ad units to provide a varied user experience and sell more impressions.

Add Your App/Website

To register your published app, website, or unpublished app with InMobi, follow the instructions below.

1. Select Inventory Inventory Settings from the left navigation panel.
2. Click Add Inventory and select an inventory channel from the drop-down menu.

   

   • Mobile App: Enter your app's App Store or Google Play Store URL.

     

   • Unpublished App: Click the link next to 'App not published on Google Play Store or Apple App Store?' on the app details page.Enter details such as the App Name, Operating System, Category, and Rating.

     

   • Mobile Website: Enter details such as website URL, Name, Category, and Rating.

     

   • CTV App: Enter details such as App URL, Name, Bundle ID, Operating System, Category, and Rating.

     

3. Click Continue.
4. In the Compliance and Privacy section, select an appropriate setting to declare your app’s audience and update your Child Privacy Compliance setting. For more information, see Children’s Privacy Compliance.
5. To allow InMobi to collect and use the location data of your users, select Yes under the Location Permission section. 

   Note

   If you need help editing your compliance settings, contact support@inmobi.com.

6. Click Save and Create Placements.

You have successfully added your app or website.

Create Placements and Ad Units

To create a new placement, follow the instructions below.

1. Once you've added your inventory, you need to add a new placement. 
2. Select the Ad Unit and enter Placement Details. For more information about ad unit types, see Ad Units.

   

3. Click Create Placement. Once done, you can view the respective ad unit down below the page. Click Edit to make changes to the placement.

   

You have successfully created an ad unit and placement. Repeat the above steps to create multiple ad units.

Configure Payments

Update company and billing information

You must update your company details and payment information to receive payments from InMobi. Follow the steps below to configure payments.

1. Select Finance Payment Settings Payment Information, from the left navigation panel.
2. Enter the required details.

   screenshot-

3. Click Proceed.

You have successfully updated your company and billing information.

Select a preferred mode of payment and manage payouts

For payments to be made to you, you must add a mode of payment. You can receive your payouts via Electronic Fund Transfer or PayPal. To add your preferred mode of payment, follow the instructions below.

1. Select Finance Payment Settings Payout Settings.
2. Before you add a payment account, select a payment country.
3. Click Add a payment account and select your desired payment method from PayPal or Electronic Funds Transfer.
4. You can add multiple payment accounts. However, you can set only one of the payment accounts as your primary bank account for the payouts. The modes of payment vary based on the payment country selected.

Upload Tax Documents

You must upload the tax forms depending on the payment country.

• India: You should upload the GST details if the Payment Country is India.

• Japan/South Korea: In the case of Japan or South Korea as the Payment Country, you should enter the VAT/TIN details.
• USA: In the case of the USA, you must enter the IRS tax details.

To know more about the IRS tax form types, refer to the following table below:

Set a minimum payment threshold

We can process payments once your cumulative earnings exceed the minimum payment threshold set. The threshold range must be between $300 - $10000.

Integration

Method 1: Via InMobi SDK

Since you have already set up your account, first placements, and ad units on the InMobi UI, your next step is integrating the InMobi SDK into your app. It gives you access to InMobi’s exchange and ad network technology to serve in-app ads.

It is recommended that you always update to the latest version of our SDK to take advantage of newly launched features or performance fixes we might introduce.

Click here to download the latest InMobi SDKs (iOS and Android). You can review our integration guidelines for iOS and Android.

Method 2: Third-party Mediation

Mediation is a monetization solution that allows app developers to manage and optimize multiple advertising partners with just one SDK integration. Mediation gives publishers access to demand through multiple ad networks, creating an arena where the networks compete to serve their ads.

To integrate InMobi as a demand source on third-party mediation platforms, you must integrate the InMobi SDK adapter. You can integrate InMobi with:

• Unity
• Mopub
• Google Admob
• AppLovin MAX
• Unity LevelPlay
• Fyber

For more information about our integrations and the available formats, see Third-party Mediation Platform.

If you wish to use InMobi as your primary mediation platform, we recommend you to see Getting Started.

Audience Bidding

Header bidding goes by many names. At InMobi, we call it Audience Bidding. Essentially, Audience Bidding is in-app header bidding. It allows publishers to sell their inventory in a unified auction where ad sources bid for each impression in real time.

Publishers can enable Audience Bidding with InMobi as a demand source using all major header bidding solutions in the market, including:

• Amazon Publisher Services via Transparent Ad Marketplace (TAM)
• Prebid (via oRTB endpoint)
• Applovin Max (via SDK)
• Mopub (via SDK)
• Unity LevelPlay (via SDK)
• Fyber (via SDK)

For more information, see our Audience Bidding integrations.

For more information on the Open RTB integrations, see oRTB integrations.

Test your integration

Testing your integration is an important step for successful onboarding. We recommend testing your integration to ensure that placements and ad units are correctly displaying across your app without affecting the live traffic. To start testing using our Sandbox Testing tool, follow the instructions below.

1. Select Integration Integration Testing.
2. Click Add Test Device.

   

3. Enter the required information such as device type, platform, name, and advertising ID. Click Add Device.

   

You have successfully added a device for testing your integration. If you come across any issues, contact our support team to start troubleshooting your integration.

Best Practices

To maximize your monetization with InMobi, it is strongly recommended that you implement our best practices listed below.

• Adding InMobi as an authorized seller to your app-ads.txt file is recommended to protect your inventory and let your buyer know which sellers have legitimate access to selling your in-app inventory. The same applies to mobile web with ads.txt. Not completing this step will limit the number of DSPs able to buy your inventory.
• Additionally, ensure that you add your Domain when registering your App or Website, as highlighted in Step 2 above.
• Make your inventory compliant with all the privacy initiatives:
  • GDPR: Use a Consent Management Platform (CMP) to manage consent for your EEA users and safely transmit user preferences through the Transparency Consent Framework 2.0 (TCF 2.2). Learn more about our GDPR Guide for Publishers.
  • Update to iOS 14.5 and above and ATT: For more information, see Surviving and Thriving in a Post-IDFA World.

• If you have already configured your block settings, select your desired settings from the Block Settings drop-down list. For more information on how to configure your block settings, see Block Settings.

InMobi CMP offers granular analytics to help you optimize and maximize your consent rate. You can view consent data for different regulations such as GDPR, CCPA and MSPA, and their opt-in rates according to countries for your apps and websites.

The granular analytics feature can be found under the Reports tab with two sections: Dashboard and Analytics.

1. To start, login to your InMobi CMP account.
2. Navigate to Reports and select the property for which you want to view the analytics.

   

Now let’s take a detailed look at each section.

Dashboard

The dashboard offers a pre-built set of comprehensive trends and metrics. These are not customizable. 

The Summary allows you to view and compare data between specific periods of your choice.

You can use Filters to view in-depth data for a specific regulation, site, device type, OS and country during a particular time.

1. Select the start date and end date and click More Filters.

   

2. Choose your desired filters and click Apply Filter.
3. Once done, you can view graphs based on regulation and region-wise traffic, opt-in rates, and page-wise display count.

   

Country-wise Traffic and Consent

You can view country-wise traffic and consent rates during a specific period to understand which countries generate the most traffic and opt-ins.

Regulation-wise Consent Distribution

The two pie charts at the bottom of the dashboard reflect the regulation-wise consent distribution data between GDPR and CCPA. 

Analytics

The Analytics offers a visualization into custom reports generated after selecting dimensions, filters, and metrics of your choice. 

Dimensions

Dimensions are attributes by which you filter and group data. 

InMobi CMP supports the following dimensions:

• Regulation
• Country
• Page format
• OS
• Device Type
• Consent or Pay Enabled
• GBC Enabled

Filters 

Filters allow you to query data only for specific values/attributes of the Dimensions. Furthermore, you can also select a particular timeframe to run reports for deeper granularity. 

Metrics

Metrics is the quantifiable measure that you wish to see. InMobi CMP offers the following metrics:

• Total traffic
• Total session
• Total opt-in
• Total opt-out
• Bounce rate
• Partial opt-in
• Paid User

To understand better, let’s take an example. If you want to generate a report showing the opt-in rates of mobile devices in the USA in the last 30 days, it will look something like this. 

Here, Country and Device Type are the Dimensions, 30 days is the Time, Mobile is the Device Type filter, US is the Country filter, and opt-in rates is the metric.

Generate and Schedule Reports

You can view all your saved reports by clicking View All Reports.

1. To generate a custom report, select the dimensions, metrics and filters of your choice.
2. Click Run Report. If you wish to save the same report, name it and click Save Report. 

   

3. To download a report, click Export Report. Reports can be downloaded in CSV format.

You can also schedule recurring reports. These will be automatically sent at regular intervals to specific email addresses listed by you. Currently, InMobi CMP can scheduled reports on a custom, daily, weekly, and monthly basis.

1. To start run a report with the dimensions, filters and metrics of your choice. 
2. Click Schedule Report. Add the Report Name, Frequency, Time period, Start and End dates, and time.

   

3. To add recipients, click +Add New and list out the email addresses to which you wish to send the report. Click OK.

   

InMobi’s Ad Management APIs help you manage your inventory i.e., apps and placements you are monetizing or interested in monetizing through InMobi easily and efficiently. They reduce the manual effort of managing huge inventory individually through our platform. 

Authentication

For authentication, you need the following values in the header: 

List of Available APIs

The APIs are available for the following functionalities: 

Manage Apps

• Get the list of apps
• Get the details of a specific app
• Create a new app
• Update an existing app

Manage Placements

• Get the list of placements in an app
• Get the details of a specific placement
• Create a new placement in an app
• Update a placement in an app

Request Protocol

The request protocol of all APIs is https. 

Manage Apps

1. Get the list of apps 

   • Request URL: https://publisher.inmobi.com/rest/api/v2/apps
   • Request method: GET 
   • Request parameters (query): 

     Name	Description	Required	Type	Sample/Available values
     pageNum	page number	Optional	Integer	1, 2, 3 etc.
     pageLength	number of records per page	Optional	Integer	1, 2, 3 etc.  Default number of results: 10
     status	status of the app	Optional	String	Available values : ACTIVE, DRAFT, ARCHIVE, FLAGGED  Default value: ACTIVE

   • Request body: NA
   • Response format
     • Response body:

       { 
         "success": true, 
         "data": { 
           "totalRecords": 281, 
           "records": [ 
             { 
               "storeUrl": "string", 
               "appName": "string", 
               "platform": "string", 
               "bundleId": "string", 
               "childDirected": 1, 
               "appRating": "string", 
               "appId": 0 
             } 
           ] 
         } 
       } 
       			

     • Response body values:

       Name	Description	Type	Sample/Possible values
       Success	Determines success of the response	Boolean	true – request successful false – request unsuccessful with some error(s)
       storeUrl	App store/Play store URL of the app	String (url)	URL
       appName	Name of the app	String	Sample App
       Platform	Platform of the app	String	Android or iPhone (iOS)
       bundleId	Bundle of the apps as registered in the store	String	Com.org.app
       childDirected	Determines the audience type of the app	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
       appRating	Content Rating of the app	String
       appId	ID of the app on InMobi dashboard	Numeric

2. Get the details of a specific app

   • Request URL: https://publisher.inmobi.com/rest/api/v2/apps/{appId} (App ID should be mentioned in the request URL)
   • Request method: GET
   • Request parameters (query): NA
   • Request body: NA
   • Response format
     • Response body:

       
       { 
         "success": true, 
         "data": { 
           "storeUrl": "string", 
           "appName": "string", 
           "platform": "string", 
           "bundleId": "string", 
           "childDirected": 0, 
           "appRating": "string", 
           "appId": 0 
         }, 
         "status": "string", 
         "createdOn": "string" 
       } 
        
       			

     • Response body values:

       Name	Description	Type	Sample/Possible values
       Success	Determines success of the response	Boolean	true – request successful   false – request unsuccessful with some error(s)
       storeUrl	App store/Play store URL of the app	String (url)	URL
       appName	Name of the app	String	Sample App
       Platform	Platform of the app	String	Android or iOS
       bundleId	Bundle of the apps as registered in the store	String	Com.org.app
       childDirected	Determines the audience type of the app	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
       appRating	Content Rating of the app	String
       appId	ID of the app on InMobi dashboard	Numeric
       status	Current status of the app on platform	String	PENDING REVIEW, ACTIVE, FLAGGED, REJECTED, ARCHIVED
       createdOn	Date of app creation on platform	String

3. Create a new app

   • Request URL: https://publisher.inmobi.com/rest/api/v2/apps
   • Request method: POST
   • Request parameters (query): NA
   • Request body:
     • Schema:

       { 
         "storeUrl": "string", 
         "childDirected": 0, 
         "locationAccess": true, 
         "appName": "string" 
       } 
       			

     • Request body values:

       Name	Description	Required	Type	Sample/Possible values
       storeUrl	App store/Play store URL of the app	Required	String (url)	URL
       locationAccess	Specify if InMobi can access the location details	Required	Boolean	true – InMobi will be able to use the location data collected by this app. false – InMobi will not be able to access the location data collected by this app.
       childDirected	Specify the audience type of the app	Required	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
       appName	Name of the app	Optional	String	Sample App

     • Response format:
       • Response body:

         { 
           "success": true, 
           "data": { 
             "storeUrl": "string", 
             "appName": "string", 
             "platform": "string", 
             "bundleId": "string", 
             "childDirected": 0, 
             "appRating": "string", 
             "appId": 0 
           }, 
           "status": "string", 
           "createdOn": "string" 
         } 
         
         				

       • Response parameters:

         Name	Description	Type	Sample/Possible values
         Success	Determines success of the response	Boolean	true – request successful
         storeUrl	App store/Play store URL of the app	String (url)	URL
         appName	Name of the app	String	Sample App
         Platform	Platform of the app	String	Android or iOS
         bundleId	Bundle of the apps as registered in the store	String	Com.bundle.app
         childDirected	Determines the audience type of the app	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
         appRating	Content Rating of the app	String
         appId	ID of the app on InMobi dashboard	Numeric
         status	Current status of the app on platform	String	PENDING REVIEW, ACTIVE, FLAGGED, REJECTED, ARCHIVED
         createdOn	Date of app creation on platform	String

4. Update an existing app

   • Request URL: https://publisher.inmobi.com/rest/api/v2/apps/{appId} (App ID should be mentioned in the request URL)
   • Request method: PATCH
   • Request parameters (query): NA
   • Request body:
     • Schema:

       { 
       
         "childDirected": 0, 
       
         "locationAccess": true, 
       
         "appName": "string" 
       
       }
       			

     • Request body values:

       Name	Description	Required	Type	Sample/Possible values
       locationAccess	Specify if InMobi can access the location details	Required	Boolean	true – InMobi will be able to use the location data collected by this app. false – InMobi will not be able to access the location data collected by this app.
       childDirected	Specify the audience type of the app	Required	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
       appName	Name of the app	Optional	String	Sample App

     • Response format:
       • Response body:

         { 
           "success": true, 
           "data": { 
             "storeUrl": "string", 
             "appName": "string", 
             "platform": "string", 
             "bundleId": "string", 
             "childDirected": 0, 
             "appRating": "string", 
             "appId": 0 
           }, 
           "status": "string", 
           "createdOn": "string" 
         } 
         
         				

       • Response parameters:

         Name	Description	Type	Sample/Possible values
         Success	Determines success of the response	Boolean	true – request successful
         storeUrl	App store/Play store URL of the app	String (url)	URL
         appName	Name of the app	String	Sample App
         Platform	Platform of the app	String	Android or iOS
         bundleId	Bundle of the apps as registered in the store	String	Com.bundle.app
         childDirected	Determines the audience type of the app	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
         appRating	Content Rating of the app	String
         appId	ID of the app on InMobi dashboard	Numeric
         status	Current status of the app on platform	String	PENDING REVIEW, ACTIVE, FLAGGED, REJECTED, ARCHIVED
         createdOn	Date of app creation on platform	Optional

Manage Placements

1. Get the list of placements in an app 

   • Request URL: https://publisher.inmobi.com/rest/api/v1/placements 
   • Request method: GET 
   • Request parameters (query): 

     Name	Description	Required	Type	Sample/Available values
     pageNum	page number	Optional	Integer	1, 2, 3 etc.
     pageLength	number of records per page	Optional	Integer	1, 2, 3 etc.  Default number of results: 10
     appId	The ID of an app	Required	Integer
     placementType	The type of placement	Optional	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE

   • Request body: NA
   • Response format
     • Response body:

       { 
         "success": true, 
         "data": { 
           "totalRecords": 281, 
           "records": [ 
             { 
               "storeUrl": "string", 
               "appName": "string", 
               "platform": "string", 
               "bundleId": "string", 
               "childDirected": true, 
               "appRating": "string", 
               "appId": 0 
             }, 
             { 
               "placementId": 0, 
               "placementName": "string", 
               "placementType": "string", 
               "testMode": "string", 
               "status": "string", 
               "appId": 0, 
               "cpmFloor": 0, 
               "isAudienceBiddingEnabled": true, 
               "audienceBiddingPartner": "string", 
               "a9TagId": "string", 
               "a9AppId": "string", 
               "isFallbackPlacement": true, 
               "createdOn": "string" 
             } 
           ] 
         } 
       } 
       
       			

     • Response parameters:

       Name	Description	Type	Sample/Possible values
       Success	Determines success of the response	Boolean	true – request successful false – request unsuccessful with some error(s)
       storeUrl	App store/Play store URL of the app	String (url)	URL
       appName	Name of the app	String
       Platform	Platform of the app	String	Android or iPhone (iOS)
       bundleId	Bundle of the apps as registered in the store	String	Com.org.app
       childDirected	Determines the audience type of the app	Integer	1 – App is not directed towards children 2 – App is directed towards children and requires parental consent 3 – App is directed partially towards children and towards adults
       appRating	Content Rating of the app	String
       appId	App key on InMobi platform	Integer
       placementId	ID of the placement as on InMobi platform	Integer
       placementName	Placement name as on InMobi platform	String
       placementType	Type of placement	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE
       testMode	Test mode of the placement	String	On – Test mode is on for specific devices as mentioned in the integration testing in InMobi platform  Global – Test mode is on for all devices with this app  Off – Test mode is off for all devices with this app
       status	Current status of the placement	String	Available values : ACTIVE, DRAFT, ARCHIVE, FLAGGED
       cpmFloor	eCPM floor set on the InMobi platform	Number
       isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Boolean	true – Audience Bidding is on  false – Audience Bidding is off
       audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	String	Available values: MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS, GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
       a9TagId	Tag ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
       A9AppId	App ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
       createdOn	Creation date of the placement	String

2. Get the details of a specific placement in an app

   • Request URL: https://publisher.inmobi.com/rest/api/v1/placements/{placementId} (Placement ID should be mentioned in the request URL)
   • Request method: GET
   • Request parameters (query): NA
   • Request body: NA
   • Response format
     • Response body:

       { 
       
         "success": true, 
       
         "data": { 
       
           "placementId": 0, 
       
           "placementName": "string", 
       
           "placementType": "string", 
       
           "testMode": "string", 
       
           "status": "string", 
       
           "appId": 0, 
       
           "cpmFloor": 0, 
       
           "isAudienceBiddingEnabled": true, 
       
           "audienceBiddingPartner": "string", 
       
           "a9TagId": "string", 
       
           "a9AppId": "string", 
       
           "isFallbackPlacement": true, 
       
           "createdOn": "string" 
       
         } 
       
       }
       
       
       			

     • Response parameters:

       Name	Description	Type	Sample/Possible values
       Success	Determines success of the response	Boolean	true – request successful false – request unsuccessful with some error(s)
       appId	App key on InMobi platform	Integer
       placementId	ID of the placement as on InMobi platform	Integer
       placementName	Placement name as on InMobi platform	String
       placementType	Type of placement	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE
       testMode	Test mode of the placement	String	On – Test mode is on for specific devices as mentioned in the integration testing in InMobi platform  Global – Test mode is on for all devices with this app  Off – Test mode is off for all devices with this app
       status	Current status of the placement	String	Available values : ACTIVE, DRAFT, ARCHIVE, FLAGGED
       cpmFloor	eCPM floor set on the InMobi platform	Number
       isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Boolean	true – Audience Bidding is on  false – Audience Bidding is off
       audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	String	Available values: MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS, GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
       a9TagId	Tag ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
       A9AppId	App ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
       createdOn	Creation date of the placement	String

3. Create a new placement in an app

   • Request URL: https://publisher.inmobi.com/rest/api/v1/placements
   • Request method: POST
   • Request parameters (query): NA
   • Request body:
     • Schema:

       { 
       
         "appId": 0, 
       
         "placementName": "string", 
       
         "placementType": "INTERSTITIAL", 
       
         "cpmFloor": 0, 
       
         "isAudienceBiddingEnabled": true, 
       
         "audienceBiddingPartner": "string", 
       
         "a9TagId": "string", 
       
         "a9AppId": "string", 
       
         "isFallbackPlacement": true 
       
       }
       
       

     • Request body values:

       Name	Description	Required	Type	Sample/Possible values
       appId	App key on InMobi platform	Required	Integer
       placementName	Placement name as on InMobi platform	Required	String
       placementType	Type of placement	Required	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE
       cpmFloor	eCPM floor set on the InMobi platform	Optional (not appicable in case isAudienceBiddingEnabled is "true")	Number
       isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Required	Boolean	true – Audience Bidding is on false – Audience Bidding is off
       audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	Required (only if isAudienceBiddingEnabled is “true”)	String	Available values: MOPUB, MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS, GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
       a9TagId	Tag ID of Amazon TAM placement	Required (only in case of Amazon TAM as Audience Bidding partner)	String
       A9AppId	App ID of Amazon TAM placement	Required (only in case of Amazon TAM as Audience Bidding partner)	String

     • Response format:
       • Response body schema:

         { 
           "success": true, 
           "data": { 
             "placementId": 0, 
             "placementName": "string", 
             "placementType": "string", 
             "testMode": "string", 
             "status": "string", 
             "appId": 0, 
             "cpmFloor": 0, 
             "isAudienceBiddingEnabled": true, 
             "audienceBiddingPartner": "string", 
             "a9TagId": "string", 
             "a9AppId": "string", 
             "isFallbackPlacement": true, 
             "createdOn": "string" 
           } 
         } 
         
         				

       • Response values:

         Name	Description	Type	Sample/Possible values
         Success	Determines success of the response	Boolean	true – request successful  false – request unsuccessful with some error(s)
         placementId	ID of the placement as on InMobi platform	Integer
         placementName	Placement name as on InMobi platform	String
         placementType	Type of placement	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE
         testMode	Test mode of the placement	String	ON – Test mode is on for specific devices as mentioned in the integration testing in InMobi platform  GLOBAL – Test mode is on for all devices with this app  OFF – Test mode is off for all devices with this app
         cpmFloor	eCPM floor set on the InMobi platform	Number
         isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Boolean	true – Audience Bidding is on  false – Audience Bidding is off
         audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	String	Available values: MOPUB, MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS,  GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
         appId	App key on InMobi platform	Integer
         a9TagId	Tag ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
         A9AppId	App ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
         status	Current status of the placement	String	Available values : ACTIVE, DRAFT, ARCHIVE, FLAGGED
         createdOn	Creation date of the placement	String

4. Update an existing placement in an app

   • Request URL: https://publisher.inmobi.com/rest/api/v1/placements/{placementId} (Placement ID should be mentioned in the request URL)
   • Request method: PATCH
   • Request parameters (query): NA
   • Request body:
     • Schema:

       { 
       
         "placementName": "string", 
       
         "cpmFloor": 0, 
       
         "isAudienceBiddingEnabled": true, 
       
         "audienceBiddingPartner": "string", 
       
         "a9TagId": "string", 
       
         "a9AppId": "string", 
       
       }
       
       
       			

     • Request body values:

       Name	Description	Required	Type	Sample/Possible values
       placementName	Placement name as on InMobi platform	Required	String
       cpmFloor	eCPM floor set on the InMobi platform	Optional (not appicable in case isAudienceBiddingEnabled is "true")	Number
       isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Optional	Boolean	true – Audience Bidding is on false – Audience Bidding is off
       audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	Required (only if isAudienceBiddingEnabled is “true”)	String	Available values: MOPUB, MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS, GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
       a9TagId	Tag ID of Amazon TAM placement	Required (only in case of Amazon TAM as Audience Bidding partner)	String
       A9AppId	App ID of Amazon TAM placement	Required (only in case of Amazon TAM as Audience Bidding partner)	String

     • Response format:
       • Response body:

         { 
           "success": true, 
           "data": { 
             "placementId": 0, 
             "placementName": "string", 
             "placementType": "string", 
             "testMode": "string", 
             "status": "string", 
             "appId": 0, 
             "cpmFloor": 0, 
             "isAudienceBiddingEnabled": true, 
             "audienceBiddingPartner": "string", 
             "a9TagId": "string", 
             "a9AppId": "string", 
             "isFallbackPlacement": true, 
             "createdOn": "string" 
           } 
         } 
         				

       • Response body values:

         Name	Description	Type	Sample/Possible values
         Success	Determines success of the response	Boolean	true – request successful  false – request unsuccessful with some error(s)
         placementId	ID of the placement as on InMobi platform	Integer
         placementName	Placement name as on InMobi platform	String
         placementType	Type of placement	String	Available values : INTERSTITIAL, BANNER, REWARDED_VIDEO, NATIVE
         testMode	Test mode of the placement	String	ON – Test mode is on for specific devices as mentioned in the integration testing in InMobi platform  GLOBAL – Test mode is on for all devices with this app  OFF – Test mode is off for all devices with this app
         cpmFloor	eCPM floor set on the InMobi platform	Number
         isAudienceBiddingEnabled	Determines if Audience Bidding is enabled for this placement	Boolean	true – Audience Bidding is on  false – Audience Bidding is off
         audienceBiddingPartner	Audience Bidding Partner (applicable only if Audience Bidding is enabled)	String	Available values: MOPUB, MAX, AMAZON_TAM, GOOGLE_OPEN_BIDDING, CUSTOM_MEDIATION, IRONSOURCE, SPRINGSERVE, PREBID, FYBER, ADMOST, AEQUUS, GAMEANALYTICS_HYPERBID, CHARTBOOST, GOOGLE_SDK_BIDDING
         appId	App key on InMobi platform	Integer
         a9TagId	Tag ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
         A9AppId	App ID (applicable only in case of Amazon TAM as Audience Bidding partner)	String
         status	Current status of the placement	String	Available values : ACTIVE, DRAFT, ARCHIVE, FLAGGED
         createdOn	Creation date of the placement	String

Possible errors 

Following are the possible error scenarios that might arise while using these APIs:

 Rate limits 

The rate of requests for each publisher is capped to 500 requests in an interval of 15 minutes. 

In case of any unresolved queries, please reach out to your CSM or reach out to us at support@inmobi.com. You can also raise a ticket here: https://support.inmobi.com/mytickets. 

Even though Glance Smart Lock Screen is a managed-serve platform for buying ads on ad exchanges, you also need to follow some best practices to ensure you get the best possible Return on Ad Spent (RoAS). 

Creative best practices 

Read Glance Creative best practices. 

Measurement and attribution best practices 

For accurate measurement and attribution, it’s essential to fulfill the onboarding requirements. 

Mobile Measurement Partners (MMPs) are third-party attribution platforms that capture campaign data and attribute every user action. Advertisers use MMPs to track and analyze campaign performance across multiple ad partners.

To enable this tracking, advertisers need to embed the MMP’s software development kit (SDK) in their app. This SDK captures and receives user events (e.g., clicks, installs) using tracking links provided by Glance.

Because Glance is an appless content consumption platform on phone lock screens, the user journey differs from that of standard Android apps. To accommodate this unique flow, Glance has collaborated with leading MMPs to develop custom integrations. Follow all the specified steps to integrate your preferred MMP with Glance effectively.

How Glance-MMP integrations work

Glance and MMP integrations help advertisers validate the campaign attribution numbers on their MMP dashboards. 
1.    Sign a campaign contract with Glance Sales after providing all the required onboarding information.
2.    Configure your preferred MMPs for Glance. 
3.    Share the tracking URL with the Glance team.
4.    The Glance team adds those URLs to their campaign management tool and publishes the campaign.
5.    Find the campaign performance reports on your MMP dashboard.

Supported MMPs

Glance supports integration with the following MMPs:

• AppsFlyer
• Adjust
• Kochava
• Branch
• Singular

If AppsFlyer is your preferred MMP, you need to integrate it with Glance before the campaign starts. 

The integration starts with activating Glance as your partner on your AppsFlyer account, followed by changing the required configuration and enabling the pre-load attribution option. You can generate and share the attribution links with the Glance team.

Pre-requisites 

Before the integration, make sure you have: 

• An active advertiser account with AppsFlyer. 
• Received an advertiser ID from the Glance team. 

Integration steps

Follow the steps to integrate Glance and AppsFlyer to enable attribution for Android app campaigns:

Step 1: Activate Glance as a partner

The integration starts with the activation of the Glance on your AppsFlyer dashboard using the following steps:

1. Log in to your AppsFlyer advertiser account.

2. Go to Collaborate > Partner Marketplace in the left menu bar.

   

3. In the search bar, search for Glance and select it. You move to the Integration setup page.
   

4. Click Set up Integration.
5. In the Integration tab, select the app for the integration and turn Activate partner on.

Step 2: Configure Integration settings

After you activate Glance, you need to configure the integration setting for InMobi DSP as follows:

1. In the Integration tab, turn off Advanced Privacy.
2. In Advertiser Id, enter the Advertiser ID value provided by the Glance team. <Add screenshot>
3. In the Install attribution section, turn on the Install view-through attribution toggle.
   

4. Enable the Preload attribution toggle and keep the Preload lookback window to 90 days.<Add screenshot>

5. In the Default postbacks section, select All media sources, including organic against Install (Event Name) in the for users from drop-down.

   Note:

   Organic refers to the advertiser’s unattributed data.

6. Under the In-app event settings section, enter the Advertiser ID value provided by the Glance team, which is the same as in General settings.
   

7. Enable the In-app event postbacks toggle. Glance recommends the value to be Lifetime. The minimum value is 6 months.

8. Click Add event to add postbacks for in-app events. Add all the funnel events and their details.

   

9. Click Save integration.

Step 3: Generate attribution links

For user-acquisition campaign

You can generate the attribution link for UA campaigns, which the Glance team uses while creating the campaign, as follows:

1. Go to the Attribution Link tab. The Parameter name and Value fields are auto-populated.
2. Enable the Retargeting settings toggle for re-marketing campaigns.
3. Set the CTA and VTA values mentioned as follows:
   • CTA: 7 days
   • VTA: 24 hours
     
4. Share the CTA and VTA links with the Glance team.

For remarketing campaign

You can generate the attribution link for REM campaigns, which the Glance team uses while creating the campaign, as follows:

1. In the Attribution link tab, select Use Onelink in Choose your attribution link type. Refer to Appsflyer’s Help Center to learn how to create an Onelink template.
   
2. Select an Onelink template.
3. Check Deep linking.
4. Enter a value in Deep link value.
5. Add the required values of Parameter name and Value in the Attribution link parameters section.
   
6. Enable the Retargeting settings toggle.
   
7. Enter a value in the URI scheme, which is a raw deep link URL that directs users to the specific page you want them to land on within the app.
8. Toggle on Ignore active users for retargeting only when you need to set an inactivity window to filter out active users. Keep this option toggled off if not required, as leaving it on can negatively impact campaign performance.
9. In Re-engagement window, select lifetime.

Step 4: Enable permissions

You need to provide the following permissions to Glance on the AppsFlyer dashboard:

1. Go to the Permissions tab.

2. Switch on the Ad network permissions toggle.

3. Enable the following permission toggles:

   

Step 5: Save the integration

Check the settings done in the previous steps and click Save.

If you use Adjust as MMP, you need to integrate it with Glance before the campaign starts.

Pre-requisites

Before the integration starts, make sure you have 

• An active advertiser account with Adjust.
• Received your Advertiser ID from the Glance team.

Integration Steps 

Integrating Adjust and Glance is a one-time process applicable to all further campaigns.

Step 1: Enable Glance as the partner

Enable Glance on your Adjust account as follows:

1. Log in to your Adjust account.
2. Go to Campaign Lab > Partners from the left menu bar. You reach the Partner Selection page.
3. In the search bar, search for Glance and select it.
4. Click Next. You reach the App selection page.

Step 2: Select your app 

Select the app you want to run the campaign for as follows:

1. On the App selection page, find the name of your app and select it. You can also use 
2. Click Next. You reach the Data sharing page.

Step 3: Enable data sharing 

Enable data sharing between Glance and your Adjust account as follows:

1. On Enable data sharing for Glance card, click Edit.
2. Enter the Advertiser ID shared by the Glance team. Click Enable.
3. Check the Data from all attribution sources box. This option enables you to leverage Glance's Data science models, as the unattributed data enhances the DS models to target higher-quality audiences.
4. Check the Sessions box to enable Glance to collect the campaign session activities.
5. (Optional) Check the In-app revenue (from in-app purchases) box to share your revenue event data with Glance.
6. (Optional) Check the Parameters box to share the custom parameters you have created for the campaign. Read how to create custom parameters on the Adjust Help Center.
7. Click Map event in the Map your events section to collect the campaign results of each event. Make sure you map all the events you want to the campaign for.
8. In the Adjust event drop-down, select the event you want to map.
9. Enter the name of the event.
10. Click Apply.
11. (Optional) If you have configured custom parameters, click Map parameters. Read more on the mapping event on the Adjust Help Center.
12. Click Next. You reach the Link Structure page.

Step 4: Generate a tracking URL 

You need to generate an Adjust Ad tracking URL, which the Glance team uses while configuring the campaign on Glance. Generate the URL as follows:

1. On the Link Structure page, enter a name for the tracker in Link name.
2. In Campaign parameters, click Edit to add any parameter.
3. Click Next. You can find the tracker URL for all the events you have configured.

Step 5: Share the tracking URL 

Share the Adjust tracking URL with the Glance team. 

If you use Branch as MMP for your campaigns, you need to integrate it with Glance before your first campaign. 

Pre-requisites

Before you can start the integration, make sure you have:

• An active advertiser account with Branch. 
• Received your Advertiser ID from the Glance team. 

Integration steps  

Integrating Branch and Glance is a one-time process applicable to all the further campaigns. The integration steps are: 

Step 1: Enable Glance 

You need to enable Glance as a partner as the first step in the integration. 

1. Log in to your Branch Dashboard.
2. In the left menu bar, go to Ads > Partner Management.

3. In the Ad Partners drop-down, search for Glance and select it.

   Note:

   Do not select InMobi or InMobi DSP.

4. Under the Account Settings tab, enter the values of your Advertiser ID provided by the Glance team.

5. Click Save & Enable.

Step 2: Configure Postbacks 

Enabling Glance automatically enables the following postbacks: 

• INSTALL
• OPEN
• PURCHASE

You can add new postbacks using the following steps:

1. Click Add New Postback on the Ad Partner Settings page.

2. Select the event you want to create the postback for and click Save. The Branch app automatically generates the POSTBACK URL.

3. Click Save on the Ad Partner Settings page.

Step 3: Configure the attribution window  

An Attribution window is a period for capturing the valid attribution for an event. Branch has industry-standard attribution window values pre-set in the Attribution Windows tab.

Enable the attribution window as follows:

1. Go to the Attribution Windows tab.
2. Enable the Use ad partner attribution settings toggle.
3. Click Save.

Step 4: Generate Branch Ad Link 

The Glance team uses the Branch Ad Link you generate. The link allows you to receive the attribution data from Glance, which you can use to validate the campaign performance. Share the link with them after you generate it.

Read the Generate Branch Ad Link topic on the Branch Help to know the steps of generating the link.

Step 5: Verify the integration

When the campaign launches, the data exchange starts between Glance and your Branch account. Enable Glance data on your Branch Dashboard as follows: 

1. Go to Tools > Liveview in the left menu bar.
2. Click the WEBHOOK RECORDS tab.
3. Click Add Filter.
4. Search ad partner (3p) and select it.
5. Select equals.
6. Enter a_glance and press Enter/return on your keyboard.
7. Click Update Session. You can see the data in the WEBHOOK RECORDS tab.

If you use Singular as your preferred MMP, you need to integrate it with Glance before your first campaign starts.

Pre-requisites 

Before starting the integration, make sure you have

• An active advertiser account with Singular. 
• Received your Advertiser ID from the Glance team.

Integrating Singular and Glance is a one-time process applicable to all further campaigns. 

Step 1: Select Glance as the partner

Select Glance as the partner of Singular for your campaigns as follows: 

1. Log in to your Singular account.
2. In the left menu bar, click Attribution > Partner Configuration.
   
3. Search for Glance and select it. You can also use the search bar at the top if you don’t see Glace on the list.
4. Click + Add Partner.

Step 2: Add your App and Site

Add the app and site (app version) you want to run the campaign for as follows:

1. On the Partner Configuration page, click + Add App Site.
2. In the App drop-down, select the app you want to run the campaign for.
3. In the Site drop-down, select the version of the app. You must select the latest version of the app.
   
4. Mark the Include View Through Attributions box, if not selected. This option enables the attribution of impressions.
5. Mark the Enable Fraud Postbacks box, if not selected by default.
6. Mark the Send Postbacks to Glance on all installs box. This option enables you to optimize the Glance Data Science models for precise targeting by sharing the unattributed data.
7. Keep the Click-through attribution lookback window to the default value (7 days). This is an industry-standard value, and changing it may result in inaccurate reporting.
8. In the Send in-app events to Glance drop-down, select On. This option enables you to capture the attribution of all the events that happened through the Glance campaign.

Step 3: Configure postbacks

Stay on the same page and configure the postbacks on Singular as follows:

1. Scroll down to the Install & Re-engagement Postbacks section.
2. Select the required option based on your campaign goal in the Install or Re-engagement drop-down.
3. Enter a name for the tracker in Tracker Campaign Name Filter. Singular automatically populates the Postback URL.

   Note:

   Share the URL with the Glance team only after completing all the configuration.

4. Mark the Send View-Through Postbacks box.
5. Mark the Send postbacks to Glance on all installs box.
6. Scroll down to the Event Postbacks section.
7. Check if all the events planned for the campaign are configured in the Event Postbacks section. If not, configure the required event values. Make sure the Lookback value for all events is None.
8. Mark Send View-Through Postbacks and Send All on each event. Singular automatically generates the Postback URL, which you can share with the Glance team.
   
9. Click Done.

If Kochava is your preferred MMP, you need to integrate Kochava with Glance before the campaign starts. 

Pre-requisites 

Before starting the integration, make sure you have: 

• An active advertiser account with Kochava. 
• Received your Advertiser ID from the Glance team.

Integration steps  

The integration of Kochava and Glance is a one-time process and applicable to all the further campaigns. The integration steps are: 

Step 1: Set up 

1. Log in to your Kochava account. 

2. On the right side of the header, select your required account. Then, select the app for which you want to run the campaign.

Step 2: Create a tracker

You need to create a tracker link and share it with the Glance team. The team uses the Kochava tracker in your campaigns, which allows data postback from Glance to your Kochava account. 

1. Go to Links > Campaign Manager in the left menu bar. 
2. Click Add a Tracker. The New Tracker page opens. 

3. Under the Tracker & Network Set Up section, enter a tracker name.

   Note:

   The Tracker Name field fills up with a system-generated name when you click Add a Tracker. It’s suggested you change the name to your preferred name.

4. Select  Acquisition in the TRACKER TYPE drop-down. For the Re-engagement campaign, select Reengagement.

5. Select Glance in the MEDIA PARTNER drop-down.
6. (Optional) Select an option in the AGENCY PARTNER if applicable.

7. Under the Destination URL section, select Landing Page.

   Note:

   Refer to Kochava’s Landing Page Creation and Maintenance Support documentation for more information on creating and using Landing Pages.

8. (Optional) Enter required values in Custom Parameters.
9. Click Save & Create Postback to navigate directly to the Partner Configuration page.
   Alternatively, you can click Save and navigate to the Partner Configuration by going to Apps & Assets > Partner Configuration in the left menu bar.

Step 3: Configure Postbacks  

A postback—also called a callback—is data communication between two servers (Kochava and Glance in the current scenario) following an in-app event, such as an app installation or user activity. This system enables the Glance team to get real-time updates on user interactions, drops, or any issues regarding the campaign. Configure the postbacks for Glance as follows: 

1. Go to Apps & Assets > Partner Configuration in the left menu bar.

2. Click Add a Configuration.
3. In the MEDIA PARTNER drop-down, select Glance.

4. Click Go.

5. Click  Install > Postback Tools  (  •
   •
   •  ) >  Edit. The Edit Postback Install page opens.

6. Enter or select the Glance-recommended values in the following fields:

   Field	Glance recommended value	Description
   PROPERTY NAME	advertiser_id	Identifier for the Glance campaigns.
   IMPRESSION CONVERSION DELIVERY	-	Determines if impression-matched install postbacks are limited.
   PACKAGE NAME/BUNDLE ID	-
   DELIVERY DELAY	Realtime Delivery	Enables real-time postback delivery to Glance.
   RETRY ATTEMPTS	3	Configures the number of attempts for redelivery in case of a failure.
   DELIVERY METHOD	Deliver All	Provides unattributed data access to the Glance.

7. Save the postbacks.

Glance is a user-first content discovery platform developed in partnership with leading Android OEMs. It delivers an app-less experience on the Lock Screen, reaching over 400 million users globally. Glance offers full-screen ad inventory on the Lock Screen and Feed Screen, enhancing engagement with seamless content discovery. 

Unlike traditional app inventories, Glance delivers non-intrusive, native, fresh, high-quality, serendipitous, and contextual ad experiences. This approach creates lasting impressions and improves users’ Lifetime Value (LTV).

Read more about Glance ad inventories.

Glance creatives follow strict guidelines and specifications defined by the Glance team and integrated OEMs. These guidelines ensure a consistent, accessible user experience while promoting app discovery, user safety, and brand safety. They also enhance user interaction and simplify development, maintenance, and updates, leading to improved quality control and more efficient rollouts of new features and fixes. 

Glance offers user acquisition and re-marketing campaign capabilities backed by first-party data from Glance and other InMobi platforms. You can also leverage the Glance's machine learning models effectively by sharing your unattributed data with the Glance team.

Once you have signed the campaign contract with the Glance team, you need to fulfill the onboarding requirements for Glance. These requirements are necessary to run the campaign efficiently and achieve the campaign goals.

Before the campaign starts, you need to integrate your preferred Mobile Measurement Partner (MMP) with Glance to enable third-party measurement and validation. During and after the campaign, you can find campaign performance reports on your preferred MMP dashboard.

Glance performance campaign flows

Glance Smart Lock Screen performance campaigns can be of two types based on the user flow:

One-click Install (OCI) campaigns

Users can initiate app installation with one click on the CTA, without unlocking the phone and getting redirected to the Google Play Store or other OEM app marketplaces. The OCI flow has the following user flow

1. The user sees an ad on the Glance Lock screen with an Install CTA.
2. The app download queues in the background.
3. The user continues engaging with Glance content, such as news, games, or other cards.
4. The user unlocks the phone.
5. The app installs automatically, and the status is visible in the notification bar. If the internet is not available on the device, the download starts the moment the device gets the internet.

Playstore flow

The CTA of the ad leads the user to unlock their device and redirects them to Google Play Store or any other app source.

Benefits of opting for Glance OCI over Play Store flow

Glance OCI provides several key advantages compared to the traditional Play Store flow:

• Frictionless flow: The OCI flow simplifies user acquisition by removing unnecessary steps, making the CTIT (Click to install time) shorter. Users install apps directly from the Lock Screen with a single click, avoiding the need to navigate through the Play Store. This streamlined process boosts immediate app engagement.

• Install rejection: Glance ensures a privacy-safe, on-device attribution system. It is a deterministic attribution partner to AppsFlyer and Adjust, thus driving precise and fraud-free attributions.

• Access to alternate marketplaces: For advertiser apps facing stricter regulations on the Play Store, Glance OCI offers direct access to alternative marketplaces and direct APK downloads for app distribution, reducing dependency on Google Play Store policies.
• Distraction-free Installation: When users are redirected to the Play Store, they may encounter competing apps within the same category. Glance OCI prevents this by keeping the entire process on the Lock Screen, allowing conversions to happen in one click without distractions.

You can buy Glance Smart Lock Screen Inventories through direct deals with Glance to reach 400 million Glance users. The following inventories are available for performance ads on Glance:

• Lock Screen: Glance Lock Screen is the first screen of over one-third of Android mobile phones, visible when users pick up their phones. This screen is meant for premium static display ads, thus driving the fastest discoverability of advertisers’ products and services. 
  
• Feed: Glance Feed is another user destination of the Glance Smart Lock Screen platform which users can access after clicking the CTA on the Lock Screen, offering capabilities to run more engaging formats (full-screen display and video ads), thus driving additional conversions. 

OEM availability

Glance is available on the following mobile OEMs:

• Xiaomi
• RealMe
• Samsung
• Oppo
• Vivo
• Motorola

Glance, a consumer-first content platform, has access to over 400 million users worldwide. Every third Android device has Glance. These users consume diverse content on Glance, including news, health, lifestyle, food, sports, entertainment, automobiles, etc. This extensive user base provides valuable first-party data for targeted campaigns.

For performance campaigns, the Glance team uses these rich first-party data from its platform and other InMobi platforms as the foundation for the Glance Machine Learning models. Additionally, Glance also leverages advertisers’ data, real-time events, and past campaign data (advertiser-specific) to enhance targeting efficiency. The models dynamically create audience segments to target the right set of users.

The data required to improve the efficiency of the models comes from the following sources:

• For user acquisition campaigns (UA):
  • User-consented data from Glance and other InMobi platforms
  • Unattributed data shared by the advertisers
  • Real-time ad events
  • Past campaigns

• For remarketing campaigns (REM):
  • User-consented data from Glance and other InMobi platforms
  • Unattributed data shared by the advertisers
  • Advertiser audience
  • Past campaigns

Glance Lock Screen and Feed ad creatives are non-intrusive, native, high-quality, and contextual. Unlike standard mobile app ads, Glance ad creatives are moderated by Glance Creative Labs—a team of creative designers leveraging Glance Generative AI capabilities.

Once you sign a campaign contract with the Glance team, you share your existing creatives’ open files (.ai or .psd) with them. The Glance Creative Labs does a quality analysis of the creative and converts it into the Glance-compatible format for the campaign.

Based on the available inventories, Glance publishes full-screen display and video ads, which follow the Glance creative specifications and guidelines.

Glance creatives follow strict guidelines and specifications defined by the Glance team and integrated OEMs. These guidelines ensure a consistent, accessible user experience while promoting app discovery, user safety, and brand safety. They also streamline development, maintenance, and updates, allowing for quality control and efficiency in rolling out new features and fixes.

OEM-wise creatives

Glance has some basic differences in UI across OEMs. These differences are due to OEM partnerships and do not change the user experience. Here are some examples: 

Display ads

Glance offers premium full-screen display ad inventories on Lock Screen and Feed. 

Lock Screen

Advertiser’s requirements

Share the creative open files and copy of the ad (.ai or .psd format) with the following specifications:

• Format: .png or .jpeg
• Size: 1440x2560 pixels
• File size: Maximum 1 MB
• Advertiser name: Maximum 15 characters

Feed

Glance Feed is another user destination of the Glance Smart Lock Screen platform which users can access after clicking the CTA on the Lock Screen, offering capabilities to run more engaging formats (full-screen display and video ads), thus driving additional conversions.

Advertiser’s requirements

Share the creative open files and copy of the ad (.ai or .psd format) with the following specifications:

• Format: .png or .jpeg
• Size: 1440x2560 pixels
• File size: Maximum 1 MB
• Advertiser name: Maximum 15 characters

Video ads

Glance offers premium full-screen video ad inventories on Feed.

Advertiser’s requirements

Share the creative open files and copy of the ad with the following specifications:

• Format: .mp4
• Resolution:
  • 9:16 (recommended)
  • 16:9
• File size: Maximum 10 MB
• Advertiser name: Maximum 15 characters

Creative guidelines

Glance follows these creative guidelines to ensure effective and engaging ad experiences:

• Ensure the hero product, person, or text is centered on the screen to improve visual composition and user engagement.
• Lock Screen ad content should be limited within the following margins:
  • Top: 725 pixels
  • Bottom: 725 pixels
  • Left: 200 pixels
  • Right: 200 pixels
    
     
• Feed ad content should be limited within the following margins:
  • Top: 460 pixels
  • Bottom: 480 pixels
  • Left: 195 pixels
  • Right: 195 pixels
• Keep the design and the visuals minimalistic to reduce any clutter. Avoid a lighter background.
  
  • Avoid text if it’s not a must. Use minimal text on impactful visuals to create compelling stories. Leverage the space around the Lock Screen Title for any additional text.
    
• Do not add more than three focus visual elements in Lock Screen creative, to ensure effective brand message delivery.
  
• Use visuals that depict the ad or brand’s core message for better user attention.
• Create intriguing content for the Lock Screen, encouraging the users to explore more branded content on Glance Feed.
• The image composition should communicate the brand’s voice or benefits.
• Avoid explicit display of meats, religious symbols, blood, cuss words, calling out other rival OEMs and brands, sharp objects, skin shows, maps, and geopolitical conflicts.
  

Restricted categories

Glance ensures complete brand safety by adopting a rigorous approach to content evaluation. The Lock Screen serves as a personal and exclusive space to Glance users. Glance has restricted the following content categories in ads:

• Adult, obscene, or sexual content 
• Arms, ammunition, or military conflicts
• Death and injury
• Online piracy
• Illegal and spam content
• Hate speech or acts of aggression
• Terrorism, crime, or violent acts
• Sensitive social issue or human rights violation
• Illicit drugs, tobacco, cigarettes, or vaping

Glance is inherently safe and fraud-free because of strict content regulations, no user-generated content, OEM guidelines, SDK integration with the OEMs, and most importantly it can’t be downloaded as an app and only present on genuine devices. The ad content moderation and publishing on Glance inventories are managed directly by the Glance team.

Glance also offers third-party fraud safety and campaign measurement integrations for advertisers.

Third-party fraud safety and campaign measurement

Glance supports the following third-party fraud-safety and campaign measurement tools:

• IVT filtering and Fraud detection partners
• Campaign measurement: AppsFlyer, Adjust, Kochava, Singular, and Branch. 

Key actions for advertisers

You can take the following actions to avoid any fraud and maximize return on ad spend and get accurate attribution:

• Complete all the Glance onboarding requirements. 
• Keep your MMP SDKs updated to benefit from the latest security updates from Glance and your preferred fraud detection partners.
• Glance’s unique user flows are mostly supported on all fraud and measurement partners but check if Glance flows are whitelisted on your preferred third-party partners.  

Glance offers flexible pricing models to advertisers depending on the campaign goals, target audience, verticals, etc. Please contact the Glance team to understand more about pricing for your campaign.

InMobi recognizes and affirms the pivotal role of Data Subject Requests (DSR) in upholding individuals' privacy rights. Following global data protection laws, any individual who wishes to exercise their rights, including but not limited to, rectifying, erasing, restricting, or objecting to the processing of their personal or sensitive information can make a DSR. In line with our unwavering commitment to protecting the privacy of data subjects, InMobi undertakes to respond to all data subject requests within the prescribed timeframe. 

If you are partnering with InMobi or any of its affiliates(s), whereby you provide us with personal or sensitive personal information of data subjects for advertising purposes (such as IP address, advertising IDs, and precise location), you can use this InMobi Data Subject Rights (DSR) Request Form. This webform enables you to submit the following DSR(s) regarding the information that InMobi Exchange processes: 

• Right to erasure; 
• Right to opt out of sell or share of personal information; 
• Right to limit use/disclosure of sensitive personal information; 
• Right to opt out of processing

For more details and information about how we use and protect personal or sensitive information, please review your 'Agreement' with us. 

The purpose of this document is to help navigate publishers through the functioning of InMobi Data Subject Rights (DSR) Request Form.

Ingress Point

Follow these steps to access the InMobi Data Subject Rights (DSR) Request Form via the Data Subject Rights tab through the ⁠Publisher Dashboard.

1. Log in to the Publisher Dashboard using your credentials.
2. Navigate to Compliance on the left-side menu and select Data Subject Rights. On the right, a page will open explaining the purpose and importance of DSR.
3. Click Go to DSR Request Form.

   

Login

1. Upon redirecting, you will land on a page where the publisher ID will be automatically filled. Click Get OTP via Email. This will open a page where a message will display with the partial email ID where the OTP has been sent.

    

2. Once you receive the OTP, enter it and click Submit. This will open the user page where the DSR form is available.

   

   Note

   The admin email ID linked to the publisher account will receive the OTP. To check the email ID that will receive the OTP or to update your DSR email IDs, please raise a ticket at https://support.inmobi.com/mytickets. To do this, select InMobi Publisher Platform and choose Data Subject Rights as Category. 

   The support center is not meant to raise DSR Requests.

Fill in DSR Form

You can share your DSR data using the DSR form.

1. Once the DSR Form opens, enter the details in the following mandatory fields:
   • Select the OS type: Select as per your requirement of Android/iOS/Both.
   • Select the DSR Type: Choose user rights from the drop-down. Currently, only RTO and RTF are enabled through the portal.
   • Download Sample File: As per your selection in OS type, a preset format file will be downloaded. Use this file to upload the list of GPIDs/IDFAs back to the portal.
   • Upload CSV File with Device IDs: Click Choose File to upload the list back to the portal. The file format must be CSV and the schema should be as same as the sample file.
     • Sample in case of OS chosen as Android/iOS

       deviceId

       0f90686e-2153-4e37-933d-f06c01877cee

       e6cb0cbc-25d5-4257-9fce-750e66a70af7

     • Sample in case of OS chosen as both

       deviceId	deviceSubType
       0f90686e-2153-4e37-933d-f06c01877cee	IDFA
       e6cb0cbc-25d5-4257-9fce-750e66a70af7	GPID

2. [Optional] Select Privacy Law: Choose an applicable region from the drop-down with the privacy law under which uploaded DSRs are raised.
3. Once the file is uploaded, click Submit. When the upload is successful, you will receive the following message.

   

   The Request ID received here will be unique and can be tracked under the Request History tab.

Request History 

Select Request History from the left navigation to view and track all the requests with their status, type, and unique Request ID.

Status

• ACCEPTED: Status of your Request ID will change to Accepted with the successful submission of the DSR file.
• ACKNOWLEDGED: Status of the Request ID will change to Acknowledged when the submitted file becomes part of the central compliance table. Upon acknowledgment, you will receive an email to your registered email id.
• SUCCESS: Status of the Request ID will change to Success when your request has been executed completely. You will receive an email to your registered email id.
• DELAYED: Status of the Request ID will change to Delayed if due to technical issues we are unable to execute your request within 30 days from the date of submission. You will receive an email to your registered email id.

InMobi DSP allows advertisers to buy mobile in-app performance ad inventories across InMobi Ad Exchange and other leading ad exchanges. InMobi is integrated with the following ad exchanges:

Platform interoperability between InMobi DSP and Ad Exchanges

The DSP is integrated with multiple ad exchanges via APIs, enabling real-time bidding (RTB) and data exchange.

• User synchronization: To ensure accurate targeting, the DSP often synchronizes user data with ad exchanges. This involves matching identifiers (device and users), and other relevant signals.
• Real-Time Bidding (RTB) protocols: The DSP adheres to RTB protocols, such as OpenRTB, which standardizes the auction process. These protocols define how bid requests and bid responses should be formatted and processed.
• Ad creatives: The ad exchanges and SSPs programmatically receive the creatives from the DSP after winning a bid.
• Bid management and optimization: The DSP uses algorithms and machine learning models to determine how much to bid on each impression based on various factors, such as user data, past campaign performance, and Key Performance Indicators (KPIs).

Ads buying lifecycle on InMobi DSP

The ad buying process on InMobi DSP involves the following steps:

1. Receiving bid requests: When a user visits an app, the ad slot raises an ad request through an SSP. The SSP creates a bid request and forwards it to an ad exchange. The exchange optimizes the request and forwards it to the DSP. This request includes information about the user, the context of the ad placement, and other user-relevant details.
2. Ad slot request: Simultaneously, advertisers create an ad slot request (ad campaign) with InMobi DSP and share success metrics and creatives.
3. Processing bid requests: The DSP processes bid requests from the ad exchanges. It filters out fraud and invalid requests and analyzes the data using InMobi machine learning models to determine whether the user matches the target audience for the ad slot request.
   
4. Bid decision and submission: If the user is deemed a good match for the advertiser goal, the DSP calculates an optimal bid price and submits the bid response back to the ad exchange. This process happens in milliseconds.
5. Auction and winning bid: The ad exchange conducts an auction with all the bids it receives from various sources.
6. Ad delivery: Once the DSP wins the bid, it instructs the ad exchange to deliver the ad creative to the user as the ad response.
7. Tracking and reporting: InMobi DSP has partnered with the leading MMPs to track and validate the ad's performance in real-time, gathering data on impressions, clicks, conversions, and other metrics. Advertisers can use any of the InMobi-partnered MMPs for tracking and reporting.

How InMobi DSP’s bidding optimization works

InMobi DSP uses AI/ML-based bidding technology to improve user acquisition and re-marketing using the following processes:

• Target KPIs: The bidding process starts by identifying the target Key performance indicators (KPI), for example, Return on Ad Spent (RoAS) and Cost per Install (CPI).
• Compute bids: InMobi's AI/ML algorithms dynamically modify bids for each request. This process considers over 50 different attributes, moving beyond traditional metrics such as Click-Through Rate (CTR) for more accurate predictions and better outcomes.
• Calculating bids: Bids are calculated based on various factors, ensuring optimal spending. The AI/ML models consider attributes related to the user, the requirement, and the inventory:
  • Requirement-based: Factors include category grouping and product collection, which help tailor ads to specific product categories or collections.
  • User-based: User profiles, location, locality, and purchase frequency are analyzed to determine the user's value and conversion likelihood.
  • Inventory-based: The platform evaluates supply bundles, exchanges, device types, carriers, ad types, and the hour of the day to optimize ad placement and timing.
• User segmentation: The technology segments users based on their Lifetime Value (LTV) into high, medium, and low. This segmentation helps prioritize spending on high-value users while managing budget allocations for medium and low-value users.
• Optimization: By continuously analyzing user behavior and adjusting bids, InMobi DSP ensures that spending is optimized for conversions, achieving the best possible performance for the given KPIs.

InMobi DSP's Machine Learning models dynamically create and update audiences for precise targeting, ensuring advertising efforts are directed toward the most relevant user groups and optimizing engagement and conversion rates. The data required to improve the efficiency of the models comes from the following sources:  

• For user acquisition campaigns: 
  • InMobi’s first-party data from the Glance and other InMobi platforms 
  • Unattributed data shared by the advertisers 
  • Real-time ad events  
  • Integrated Ad Exchanges, including InMobi Exchange, Vungle, Google Ad Exchange, etc. 
• For remarketing campaigns: 
  • Advertiser’s audience  
  • Custom audience

Before the campaign can go live on InMobi DSP, advertisers must integrate their Mobile Measurement Partner (MMP) with the DSP. MMPs are third-party attribution platforms that capture campaign data and attribute every user action. Advertisers can track and analyze campaign performance across multiple ad partners on an MMP. 

Advertisers need to embed the MMP’s software development kit (SDK) in their app and capture and receive user events (Clicks, installs, etc.) using tracking links advertisers collect from InMobi DSP. Read more about MMP.

How InMobi DSP-MMP integrations work 

The DSP and MMP integrations help advertisers validate the campaign attribution numbers on their MMP dashboards.

1. Advertisers sign a campaign contract with InMobi Sales after providing all the required onboarding information.
2. Advertisers configure their MMPs for the DSP.
3. They share the tracking URL with the InMobi team. 
4. The InMobi team adds those URLs to their campaign management tool and publishes the campaign.
5. Advertisers can find the report on their MMP dashboard. 

Supported MMPs  

InMobi DSP supports integration with the following MMPs: 

• AppsFlyer
• Adjust 
• Kochava 
• Branch 
• Singular

If AppsFlyer is your preferred MMP, you need to integrate it with InMobi DSP before the campaign starts. 

For iOS campaigns 

For running campaigns on iOS devices, the integration starts with activating InMobi DSP as a partner and changing the required configuration on the advertiser’s AppsFlyer dashboard. Post configuration, enable Probabilistic attribution. Advertisers need to generate and share the attribution links with InMobi account managers. Considering InMobi's recommendation, advertisers must enable and configure SKAN (Store Kit Ad Network) for their campaigns. 

Pre-requisites 

Before the integration, make sure you have: 

• An active advertiser account with AppsFlyer. 
• Received a gpm_id from your InMobi Account Manager. 

Integration steps 

Follow the steps to integrate the InMobi DSP and AppsFlyer to enable attribution (Probabilistic and Deterministic) for iOS app campaigns:

Step 1: Activate InMobi DSP as a partner

The integration starts with the activation of the InMobi DSP on your AppsFlyer account using the following steps: 

1. Log in to your AppsFlyer advertiser account.

2. Go to Collaborate > Partner Marketplace in the left menu bar.

   

3. In the search bar, search for InMobi DSP and select it. You move to the Integration setup page.

   

4. Click Set up Integration.
5. In the Integration tab, select the app for the integration and turn on the Activate partner toggle.

Step 2: Configure Integration settings 

After you activate InMobi DSP, you need to configure the integration settings for InMobi DSP as follows: 

1. In the Integration tab, turn off Advanced Privacy. 

2. In gpm_id, enter the GPMID value provided by your InMobi Account Manager.

   

3. In the Install attribution section, turn on the Install view-through attribution toggle.

   

4. In the Default postbacks section, select All media sources, including organic* against Install (Event Name) in the for users from drop-down.

   

   Note:

   *Organic refers to the advertiser’s unattributed data.

5. Under the In-app event settings section, enter the GPMID value provided by your InMobi account manager, which is the same as in General settings.

6. Enable the In-app event postbacks toggle. InMobi recommends Lifetime as the value of the In-app event postback window. The minimum value is 6 months. 

7. Click Add event to add postbacks for in-app events. Add all the funnel events and their details. 

8. Click Save integration. 

Step 3: Enable Probabilistic attribution 

Enabling probabilistic attribution as follows: 

1. Go to Settings > App Settings in the left menu bar. 

2. Switch on the Enable view-through attribution via probabilistic modeling toggle.

   

Step 4: Generate attribution links

You can generate the attribution link, which your InMobi Account Manager uses while creating the campaign, as follows:

1. Go to the Attribution Link tab. The Parameter name and Value fields are auto-populated.  
2. Enable the Retargeting settings toggle for re-marketing campaigns. 
3. Set the CTA and VTA values mentioned as follows:
   • CTA: 7 days
   • VTA: 24 hours

   

Step 5: Enable permissions

You need to provide the following permissions to InMobi DSP on the AppsFlyer dashboard:

1. Go to the Permissions tab.

2. Enable the following permission toggles:

   

Step 6: Set up SKAN

You can activate the SKAN for your iOS campaigns as follows:

1. Go to Settings > SKAN Conversion Studio in the left menu. 

2. Click  •
   •
   •  and turn on the  SKAN measurement toggle.

3. Select one of the following measurement modes based on your requirement and click Continue:
   • SKAN: Measures fine and coarse-grained metrics across retention, revenue, and engagement.
   • Custom: Measures multiple metrics across retention, revenue, and engagement.
   • Revenue: Measures revenue ranges.
   • Conversion: Measures users' in-app events such as installs, registrations, and purchases.
   • Engagement: Measures users' in-app user interactions, such as likes, comments, and reviews.

4. After selecting the measurement mode, decide which in-app events you want to capture for campaigns. Select in-app events and their range.

   Note:

   You can add a maximum of six unique in-app events.

   

   Note:

   Learn more about configuring in-app events.

5. Click the Download mapping file to save the Conversion Value mapping locally.

   Note:

   Learn more about Conversion Value mapping.

6. (Optional) You can upload your custom Conversion Values by clicking Upload Custom Decode Mapping File.

   Note:

   Learn more about Custom Decode. Refer to AppsFlyer’s SKAN Conversion Studio help for more details on setting up SKAN.

Step 7: Save the integration  

Check the settings done in the previous step and click Save. 

InMobi’s recommendations for SKAN

InMobi recommends you set up SKAN Conversion Values as follows for the best attribution results: 

• Select Conversion or Custom model while selecting the measurement mode.
  • For the Conversion model, configure all events (recommended six) starting from the app open to your final KPI.
  • For the Custom model, click + Add measurement to add the six events.
• Configure Activity Window to measure the users' activity during an interval. This step is necessary for capturing attribution because the activity window may expire before the user performs a specific action. Read more about Activity Window for SKAN versions.
• In the Activity Window section, set the highest interval value for the in-app events (recommended six events). 

For Android  

The integration for the Android campaigns starts with activating InMobi DSP as your partner on your AppsFlyer dashboard and changing the required configuration. You can then generate and share the attribution links with your InMobi account manager.  

For any queries related to the integration, please contact your InMobi Account manager. 

Pre-requisites 

Before starting the integration, make sure: 

• You have an active advertiser account with AppsFlyer. 
• You have received a gpm_id from your InMobi Account Manager. 

Integration steps

Follow the steps to integrate the InMobi DSP and AppsFlyer to enable attribution for Android app campaigns:

Step 1: Activate InMobi DSP as a partner

The integration starts with the activation of the InMobi DSP on your AppsFlyer dashboard using the following steps:

1. Log in to your AppsFlyer advertiser account.

2. Go to Collaborate > Partner Marketplace in the left menu bar.

   

3. In the search bar, search for InMobi DSP and select it. You move to the Integration setup page.

   

4. Click Set up Integration.
5. In the Integration tab, select the app for the integration and turn Activate partner on.

Step 2: Configure Integration settings

After you activate InMobi DSP, you need to configure the integration setting for InMobi DSP as follows:

1. In the Integration tab, turn off Advanced Privacy.

2. In gpm_id, enter the GPMID value provided by your InMobi Account Manager.

   

3. In the Install attribution section, turn on the Install view-through attribution toggle.

   

4. In the Default postbacks section, select All media sources, including organic against Install (Event Name) in the for users from drop-down.

5. Under the In-app event settings section, enter the GPMID value provided by your InMobi account manager, which is the same as in General settings

6. Enable the In-app event postbacks toggle. Do not change the default value of the In-app event postback window.

7. Click Add event to add postbacks for in-app events. Add all the funnel events and their details.

   

8. Click Save integration.

Step 3: Generate attribution links

You can generate the attribution link your InMobi Account Manager uses while creating the campaign as follows:

1. Go to the Attribution Link tab. The Parameter name and Value fields are auto-populated.
2. Enable the Retargeting settings toggle for re-marketing campaigns.
3. Set the CTA and VTA values mentioned as follows:
   • CTA: 7 days
   • VTA: 24 hours

   

Step 4: Enable permissions

You need to provide the following permissions to InMobi DSP on the AppsFlyer dashboard:

1. Go to the Permissions tab.

2. Enable the following permission toggles:

   

Step 5: Save the integration

Check the settings done in the previous steps and click Save.

If you use Singular as your preferred MMP, you need to integrate it with InMobi DSP before your first campaign starts.

Pre-requisites 

Before starting the integration, make sure you have

• An active advertiser account with Singular. 
• Received your gpm_id from the InMobi team. 

Integration Steps 

Integrating Singular and DSP is a one-time process applicable to all further campaigns. 

Step 1: Select InMobi as the partner

Select InMobi DSP as the partner of Singular for your campaigns as follows: 

1. Log in to your Singular account.
2. In the left menu bar, click Attribution > Partner Configuration.
   
3. Search for InMobi DSP and select it. You can also use the search bar at the top if you don’t see InMobi DSP on the list.
4. Click + Add Partner.

Step 2: Add your App and Site

Add the app and site (app version) you want to run the campaign for as follows:

1. On the Partner Configuration page, click + Add App Site.
2. In the App drop-down, select the app you want to run the campaign for.
3. In the Site drop-down, select the version of the app. You must select the latest version of the app.
   
4. Mark the Include View Through Attributions box, if not selected. This option enables the attribution of impressions.
5. Mark the Enable Fraud Postbacks box, if not selected by default.
6. Mark the Send Postbacks to InMobi DSP on all installs box. This option enables you to optimize the InMobi Data Science models for precise targeting by sharing the unattributed data.
7. Keep the Click-through attribution lookback window to the default value (7 days). This is an industry-standard value, and changing it may result in inaccurate reporting.
8. In the Send in-app events to InMobi DSP drop-down, select On. This option enables you to capture the attribution of all the events that happened through the DSP campaign.

Step 3: Configure postbacks

Stay on the same page and configure the postbacks on Singular as follows:

1. Scroll down to the Install & Re-engagement Postbacks section.
2. Select the required option based on your campaign goal in the Install or Re-engagement drop-down.
3. Enter a name for the tracker in Tracker Campaign Name Filter. Singular automatically populates the Postback URL.

   Note:

   Share the URL with the InMobi team only after completing all the configuration.

4. Mark the Send View-Through Postbacks box.
5. Mark the Send postbacks to InMobi DSP on all installs box.
6. Scroll down to the Event Postbacks section.
7. Check if all the events planned for the campaign are configured in the Event Postbacks section. If not, configure the required event values. Make sure the Lookback value for all events is None.
8. Mark Send View-Through Postbacks and Send All on each event. Singular automatically generates the Postback URL, which you can share with the InMobi team.
   
9. Click Done.

On Ad exchanges, InMobi DSP supports all popular mobile in-app ad formats. You can buy the following ad formats through InMobi DSP on ad exchange inventories:

Display ads

Display ads are static or animated images with standard dimensions. InMobi DSP supports the following sizes: Small banners, Medium banners, Interstitials, and Native Display. 

Small banners

Small banners are small-sized rectangular ads placed at the top, between paragraphs, and at the bottom of an article or a page. They are nonintrusive, cost-effective, frequent, contextual, and efficient formats that can reach a wider audience with minimal loading time and precise measurement.

The specifications of small banners are: 

• Dimensions: 640 x 100 pixels
• Media format: .jpg or .gif
• Maximum file size: 500 KB

Medium rectangle banners

Medium banners are rectangular ads of medium size. These ads can be placed between the content, loading page, reward pages, etc. They are nonintrusive, cost-effective, frequent, contextual, and efficient formats that can reach a wider audience with minimal loading time and precise measurement.  

The specifications of small banners are: 

• Dimensions: 600 x 500 pixels
• Media format: .jpg or .gif
• Maximum file size: 500 KB

Interstitials

Interstitials are rectangular ads that cover the screen on which they are displayed. These are high-impact ads.  The specifications of interstitials are: 

• Dimensions: 640 x 960, 960 x 640, 640 x 1136, and 1136 x 640 pixels
• Media format: .jpg or .gif
• Maximum file size: 500 KB

Native ads

Native ads blend in with the content on which they appear, providing a more seamless and less intrusive user experience. These ads mimic the look, feel, and function of the media format in which they are seen, such as articles, videos, or other media. These ads offer higher engagement rates, improved CTRs, stronger brand affinity, reduced ad fatigue, and better ad rendering, along with contextual and personalized targeting.

There are three types of native: Rich display, Rich video, and Icons.

Rich display ads

These are medium rectangle, fullscreen portrait, and wide rectangle ads. You can provide the ad creatives for the rich display ads based on the following specifications:

• Primary asset type (Mandatory): Image (1200 x 628 pixels)
• Secondary Asset (Mandatory): Icon (300 x 300)
• Text character limits:
  • Title: 20
  • CTA: 20
  • Sponsored By text: 20
  • Description: 140 characters

Rich video ads

These are medium rectangle, full-screen portrait, and wide rectangle video ads. You can provide the ad creatives for the rich video ads based on the following specifications:

• Primary asset type (Mandatory): Video
  • Full-screen landscape:
    • Aspect ratio: 4:3 to 16:9
    • Video resolution: 1080p or 720p
  • Full-screen portrait:
    • Aspect ratio: 9:16 to 3:4
    • Video resolution: 1080p, 720p
• Secondary asset (mandatory): Image
  • Wide rectangle: 1200 x 628 pixels
  • Square: 300 x 300 pixels
• Text character limits:
  • Title: 20
  • CTA: 20
  • Sponsored By text: 20
  • Description: 140

Icon ads

Icon ads in mobile apps are small, square-shaped, visually appealing ads typically displayed as icons within the app interface. These often appear in menus, navigation bars, or as part of a feed. You can provide the ad creatives for the icon ads based on the following specifications:

• Primary asset type (Mandatory): Icon image (300 x 300 pixels)

• Text character limits:
  • Title: 20
  • CTA: 20
  • Sponsored By text: 20
  • Description: 140 characters

Video with end cards

Video ads with end cards are short video ads displayed over the content or a page and followed by a static or animated display CTA card. The specifications of video ads are:

• Dimensions: 1920 x 1080 (16:9) and 1080 x 1920 (9:16)
• Media format: .mp4 or .mov
• Maximum file size: 100 MB
• Recommended range: <20 seconds

Playable ads

Playable ads are interactive micro-game formats in which users can interact and play game previews. After the game ends, users can click the CTA to install the app. These games are meant to engage users and motivate them to install the app for the complete experience. These ads are best suited for gaming advertisers but can also be incorporated into other verticals. The specifications of playable ads are:

• Dimensions: Portrait and landscape full-screen
• Recommended: Responsive
• Media format: HTML5 and JS tags
• Maximum file size: 5 MB

Important components of an ad unit

The important components of an ad unit are as follows:

• App icon or brand logo: Ensure clear visibility of your brand.
• Product showcase: Highlight key features or products.
• Primary tagline: Deliver a concise and compelling message.
• Secondary messaging: Provide additional information supporting the primary message.
• Call to Action (CTA): Make the CTA clear and prominent to drive user action.
• Background: Use a background that complements the overall design without distracting from the main content.
• Sub-headline: Offer additional supporting information.

Creative best practices

Adhere to the following creative best practices to ensure the DSP campaign leverages high-quality ad creatives that drive user engagement and deliver effective results.

Content must have the highest priority

The ad content is the most critical element of an ad campaign, as it directly engages the audience, conveys the brand message, and drives user actions. Make sure you:

• Keep copy short and concise, suitable for mobile consumption.
• Use images that are relevant to the content and context of the ad to enhance engagement.
• Ensure branding is clear and persistent throughout the creative.
• Use animation and bright colors to draw user attention and enhance recall if the creative format allows.
• Make icons and buttons distinct, large enough to be readable, and easy to tap.
• Include trust builders such as App or Play store ratings, review numbers, and logos.

Clear call-to-action

A clear call to action (CTA) directs users to what to do next, driving conversions and ensuring the ad achieves its intended goal.

• Ensure the CTA is prominent, with contrasting colors and enough white space to stand out.
• Use strong, action-oriented language in the CTA (For example, Order Now, Install Now).
• Make the CTA button similar to Play or App Store controls to increase familiarity and ease of use.

Effective video strategy

Optimum video length and effective content benefit a video campaign by maximizing viewer engagement and completion rates, ensuring the message is effectively delivered within the audience's attention span.

• Videos of 7-15 seconds typically achieve a 90% completion rate.
• Hook users within the first 2-3 seconds to maintain engagement.
• Focus on one main objective to guide creative execution.
• Use clear and concise messaging to prompt quick actions.

Interactive zones

• Place the most interactive elements or CTA in areas of the screen that are within reach of the thumb.

Format performance

• The 320x50 slot size is the best performer, offering cost efficiency and scalability.
• Static interstitials (320x480, 480x320, 320x568, 568x320) and medium rectangles (300x250) drive strong clicks and are effective for re-engagement efforts.
• Videos with end cards drive high clicks and are excellent for re-engagement.
• Users prefer vertical videos, as 94% of users hold their phones vertically. Horizontal videos disrupt user experience.

InMobi content guidelines

Refer to InMobi content guidelines to learn about what type of content you can run through ads.

Enabling GPP and MSPA for Existing and New Signatories

1. Before you begin enabling GPP and MSPA, upgrade to v54 or latest.
2. For GDPR, select TCF, GPP, or Both (recommended).

   

3. Applicable only for Websites: Enabling both GPP and TCF doesn't work for AMP sites where only the GPP string will be stored. To extract the TCF string from GPP, use the code below:

   /**  
    * 1. Get the key from localStorage which start with amp-store
    * 2. Parse the value and convert into JSON.
    * 3. Once parsed, access the property 'amp-consent:inmobi'
    * 4. Split the GPP string, and retrieve the TCF string which you can use.
    * 5. Add proper handling and test before pushing the below code to production
    * 6. For more details on how to access local storage, please look at amp-script documentation (https://amp.dev/documentation/components/amp-script)
   */
   let consent = JSON.parse(atob(localStorage.getItem('<key-from-domain-local-storage>'))); //looks like this amp-store:https://deranged-humorr.surge.sh
   if (consent && consent.vv) {
       const gppString = consent.vv['amp-consent:inmobi'].v.r;
   
       const gppStringArray = gppString.split('~');
       
       for(let i = 0; i < gppStringArray.length; i++) {
           if (gppStringArray[i].startsWith('CP')) {
               console.log('TCF String is ', gppStringArray[i]);
           }
       }
   }
   	

4. To implement MSPA, update your signatory status and regulatory path.

   

   Note

   Only MSPA signatories can mark transactions as Covered. You can check your signatory status and sign the MSPA here.

5. Select the relevant opt-outs among personal, sensitive, and child data consents.

   

   

6. The end-user is shown the consent screen based on the consents selected by you.

   

   

7. The GPP string is stored under the key name (IABGPP_HDR_GppString).

SDK Integration Changes

Android

For Android Implementation and SDK-related changes, see Android.

iOS

For iOS Implementation and SDK-related changes, see iOS.

Portal Configuration and Setup for MSPA

To configure MSPA in the InMobi CMP portal, see Portal Configuration and SDK Changes.

APIs to Trigger MSPA Consent Screen

This section outlines the various APIs and callbacks that publishers can use to trigger the MSPA consent screen once they are integrated with GPP.

Display MSPA Screen

After initializing the SDK, you can present the MSPA screen by invoking the following method from ChoiceCmp class and pass in the delegate object for registering CCPA callback.

ChoiceCmp.shared.showUSRegulations(ccpaDelegate: self)

Once the user has given the consent, didReceiveUSRegulationsConsent(usRegData: USRegulationsData) delegate will be fired.

Callbacks

Manage MSPA consent

The callback didReceiveUSRegulationsConsent is triggered when the user gives consent to MSPA. You will get consent details in usRegulationsData.

func didReceiveUSRegulationsConsent(usRegData: USRegulationsData) { 
   print("\(#function), gppString: \(usRegData.gppString)") 
} 

User Location Changed

The callback userDidMoveToOtherState is triggered when the user changes location accompanied by the change in regulations. You can retrigger the MSPA popup if you want to retrieve new consent as per the new location.

func userDidMoveToOtherState() { 
    print(#function) 
}

You can retrieve MSPA related strings in the following keys:

InMobi performance reporting dashboard gives you a comprehensive view of your performance campaign on InMobi DSP. You can monitor your campaign performance using different combinations of metrics, countries, and media costs. You can also download overall and event-wise reports in CSV format. Any campaign event update takes 1 day to reflect on the Dashboard, and the updating happens in the UTC time zone.

Pre-requisites

• You have an active campaign on InMobi DSP. 
• You have received the invitation link from the InMobi team. 

Access

You can create an account as follows: 

1. Click the Dashboard invitation link shared by the InMobi team to reach the login page. 
2. Click Login Now.

3. If you are logging in for the first time, enter the email ID you provided to the InMobi team. Click Next.

   Note:

   If you use a different email ID, you don’t receive any response after clicking Next.

4. Enter your password. 
5. Click Log In. The Dashboard landing page opens with the list of the apps for which you have run a campaign on the DSP.  

Generate reports

You can generate reports for past or existing campaigns as follows: 

1. Log in to your DSP Dashboard. You reach the Advertiser List page.
   

2. Search for the advertiser.

3. Click your app. You land on the Overview page.

   Note:

   The dashboard view is for Android Campaigns by default. If an advertiser is not running Android campaigns, the dashboard shows No Campaigns are Live on Android for this Advertisers. It shows a similar message if the advertiser does not have an iOS campaign.

4. In the filters section, apply filters to generate the report accordingly.
   1. Select the campaign for which you want to view the performance report. You can select multiple campaigns.
   2. Select the data range for the report.
   3. Switch the toggle to Android and iOS based on the campaign’s target OS.

      Notes:

      For Japan,

      • The toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from Dollars.
        
   4. Click Apply Filter to see the intended report.
5. You can find the following report views:

   • Performance:  Generates a report by combining  Campaign Name,  Country, and  Creative Type  with  Impressions,  Clicks, and  Installs. You can download the report in SVG, PNG, and CSV format by clicking  —
     —.
     —

   • Country Vs Install: Displays a pie chart showing the country-wise installs throughout the campaign. This is visible only for Android campaigns.
   • Country Vs MMP Installs: Displays a pie chart showing the country-wise MMP installs throughout the campaign. This is visible only for iOS campaigns.
   • Media Cost vs Campaign: Provides the billable cost of the campaign. You can download the report in SVG, PNG, and CSV format by clicking  —
     —
     —

   • Overview report: Provides comprehensive data of all the performance metrics based on OS and Country. The available metrics are Clicks, Impressions, Media Cost, SKAN Installs (For iOS), MMP Installs (For iOS), Installs (For Android), CTR, eCPC, and eCPM.

     

     • You can filter the data by selecting the columns, applying operators, and entering a value, if any.

     • You can export the data in CSV or PDF format by clicking Export.

       

   • Event report: Provides KPI events data, which helps to understand the campaign performance based on user events. The available columns are Campaign Name, Event Name, Country, OS, and Total Events (Number of times users complete an event).

     

      

     Note:

     You can also sort and filter by clicking the ellipsis on the column header.

     

     • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
     • You can export the data in CSV or PDF format by clicking Export.

Generate Publisher Report

Publisher report provides you with a list of the top publishers (a maximum of 500) of your campaign. These publishers are sorted based on the number of installs. You can see which app bundles (apps where DSP published the ads) give you the best performance and scale in a date range. You can work with the InMobi team to optimize your campaign based on the publisher data.

You can generate the Publisher Report as follows: 

1. In the left menu bar, click Publisher App Report.

   

2. In the filters section, apply filters to generate the report accordingly.
   1. Select the campaign for which you want to view the Publisher report. You can select multiple campaigns.
   2. Select the data range for the report.
   3. Switch the toggle to iOS or Android based on the inventory (OS) for the campaign.

      Notes:

      For Japan,

      • The toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from Dollars.
        
   4. Click Apply Filter to get the intended report.

      • The publishers' reports are segregated into the following columns: Campaign Name, App Bundle (refers to the publisher app), Country, OS, Clicks, Impressions, Media Cost, Installs, CTR, eCPM, and eCPC.

        

      • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
      • You can export the data in CSV or PDF format by clicking Export.

      • You can also sort and filter by clicking the ellipsis on the column header.

        

Generate Creative Report

This report provides insights into the top-performing creatives for your campaign. These creatives are sorted based on the number of installs through their ad slots. You can view the creative type (creative formats such as Banner, Video, etc.) that gives the best perfrmance and scale in a date range. Work with the InMobi team to further optimize your campaigns based on the Creative report insights.

You can generate the Creative Report as follows:

1. In the left menu bar, click Creative Report.

   

2. In the filters section, apply filters to generate the report accordingly.
   1. Select the campaign you want to see the performance for. You can add multiple campaigns.
   2. Select the data range for the report.
   3. Switch the toggle to iOS or Android based on the inventory (OS) for the campaign.

      Note:

      For Japan,

      • The inventory toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from Dollars.
        
   4. Click Apply Filter.

      • The publishers' reports are segregated into the following columns: Campaign Name, Creative Name, Creative Type, Country, OS, Clicks, Impressions, Media Cost, Installs, CTR, eCPM, and eCPC.

        

      • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
      • You can export the data in CSV or PDF format by clicking Export.

      • You can also sort and filter by clicking the ellipsis on the column header.

        

       

      Note:

      Every time you change the filter values, click Apply Filter to bring the intended report.

Generate Raw Event Report

Raw Event Reports provide information on all the raw events in a live campaign. The raw events are the non-KPI events, which advertisers can refer to optimize their KPIs and understand user behavior.

You can generate the Raw Event Report as follows:

1. In the left menu bar, click Raw Event Report.
2. In the filters section, apply filters to generate the report accordingly.
   1. Select the campaign you want to see the performance for. You can add multiple campaigns.
   2. Select the data range for the report.
   3. Switch the toggle to iOS or Android based on the inventory (OS) for the campaign.

      Notes:

      For Japan,

      • The toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from Dollars.
        
3. Click Apply Filter.
   • The Raw event reports are segregated into the following columns: Campaign Name, Country, Raw Event Name, and Raw Attributed Events.
     
   • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
   • You can export the data in CSV or PDF format by clicking Export.
   • You can also sort and filter by clicking the ellipsis on the column header.
   • You can also sort and filter by clicking the ellipsis on the column header.
     

    

   Note:

   Every time you change the filter values, click Apply Filter to bring the intended report.

Generate Week-on-Week (WoW) Report

Week-on-week (WoW) reports provide weekly insights into the campaigns. The weekly insights help you understand the campaign's current performance and if any strategy change is required to uplift the performance.

You get two types of WoW reports:

• Week-On-Week Detail Report: It has detailed numbers and an option to filter and export.
  
• Week-On-Week Overview: It has a graphical overview of the weekly campaign performance based on metrics such as Clicks, Installs, Impressions, and KPI Event Count.
  

You can generate the WoW report as follows:

1. In the left menu bar, click WoW report.
2. In the filters section, apply filters to create the report accordingly.
   1. Select the campaign for which you want to see the performance. You can add multiple campaigns.
   2. Select the quarter and the year for which you want the weekly report.
   3. Switch the toggle to iOS or Android based on the inventory (OS) for the campaign. 

      Note:

      For Japan,

      • The inventory toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from dollars
        
3. Click Apply Filter.
   • The WoW reports are segregated into the following columns:
     • For iOS and SKAN campaigns: Campaign Name, Country, Impression, Clicks, MMP Installs, SKAN Installs, MMP Events, Media Cost, OS, Week Number, and Year.
     • For Android and Non-SKAN campaigns: Campaign Name, Country, Impression, Clicks, Installs, KPI Event Count, Media Cost, OS, Week Number, and Year.
   • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
   • You can export the data in CSV or PDF format by clicking Export.
   • You can also sort and filter by clicking the ellipsis on the column header.
     

Generate Day-on-Day (DoD) Report

Day-on-Day (DoD) reports provide daily insights into the campaigns. The daily insights help you understand the campaign's performance at a more granular level and adjust ad spending or strategy if required.

You can generate the DoD report as follows:

1. In the left menu bar, click DoD Report.
2. In the filters section, apply filters to create the report accordingly.
   1. Select the campaign for which you want to see the performance. You can add multiple campaigns.
   2. Select the date range for which you want the daily report.
   3. Switch the toggle to iOS or Android based on the inventory (OS) for the campaign.

      Notes:

      For Japan,

      • The toggle has Non-SKAN and SKAN options.
      • You can switch the currency to Yen from Dollars.
        
   4. Click Apply Filter.
      • The DoD report are segregated into the following columns:
        • For iOS and SKAN campaigns: Campaign Name, Date, Country, OS, Clicks, Impression, Media Cost($), MMP Installs, SKAN Installs, CTR, Total eCPE, Total eCPI, MMP MMP eCPI, SKAN eCPE, SKAN eCPI, eCPC, and eCPM.
          
        • For Android and Non-SKAN campaigns: Campaign Name, Date, Country, OS, Clicks, Impression, Media Cost($), CTR, eCPC, eCPM, eCPE, and eCPI.
          
      • You can filter the data by selecting the columns, applying operators, and entering a value, if any.
      • You can export the data in CSV or PDF format by clicking Export.
      • You can also sort and filter by clicking the ellipsis on the column header.
        

       

      Note:

      Every time you change the filter values, click Apply Filter to bring the intended report.

When managing ad campaigns on InMobi DSP and collaborating with a Mobile Measurement Partner (MMP), it is crucial to adopt industry best practices that protect your investment and optimize performance. InMobi DSP employs a comprehensive approach to fraud prevention, ensuring campaigns reach authentic users.

Key considerations for advertisers

You need to adhere to the following considerations to keep your campaigns fraud-free:

Choose your partners wisely

You need to choose your partner based on which stage you need their service.

Stage 1: Ad request

In the initial stage of ad buying on a DSP, the ad request is filtered to ensure it is genuine and safe. This stage has the following processes:

• IVT filtering: This step filters out invalid traffic (IVT) and ensures that only genuine ad requests are processed, reducing the chances of fraud. The DSP supports mFilterIt for IVT filtering.  
• Fraud detection: This step identifies and blocks fraudulent activities right at the beginning. 

Stage 2: Ad placement

Once the ad request is verified, the next stage involves placing the ad in viewable slots. The DSP supports DoubleVerify (DV) and Integral Ad Science (IAS) for verifying the viewability of ads. These tools ensure that ads are placed in locations where they are likely to be seen by users, enhancing their effectiveness and reducing the risk of ad fraud. 

Stage 3: Post ad rendering

After the ad is placed, the focus shifts to measuring its performance and ensuring accurate attribution.

• Audience measurement: The DSP supports Comscore and Nielsen to measure audience engagement and the impact of ads post-rendering. This stage helps in understanding the reach and effectiveness of the ads.
• Attribution partner: InMobi DSP supports integration with AppsFlyer, Adjust, Kochava, Singular, and Branch to accurately track and attribute ad interactions and conversions. You can use these MMPs to ensure that ad campaign performance is correctly measured and reported. 

Understand mobile ad fraud types

Awareness of common mobile ad fraud types helps in securing campaigns:

• Click spam: Generates fake clicks to steal attribution.
• Click injection: Injects clicks during app installation to claim last-click attribution.
• SDK spoofing: Mimics SDK communications to fake app installations.
• Fake installs: Uses bots and emulators to simulate non-existent app installs.

Implement robust fraud detection mechanisms

You should implement strong fraud detection mechanisms (or tools like mFilterIt) and continuously monitor campaign metrics beyond installs, focusing on post-install behaviors.

Some of the common fraud behaviors are:

• Scenario 1: The overzealous fraudster
  High-quality user traffic outperforming reliable sources by a large margin can be a fraud.
• Scenario 2: The flat funnel
  Significant discrepancies in the events or installs funnel from standard patterns can be a fraud.
• Scenario 3: The limits of in-app engagement
  Bots relying on a weak SDK authentication often show imbalanced engagement, signaling non-human traffic.

Key actions for advertisers

You can take the following actions to avoid any fraud and maximize return on ad spend and accurate attribution:

• Set clear fraud terms: To ensure accountability, define explicit fraud terms with all media sources and discuss those terms with the InMobi team prior to launching a campaign.
• Monitor engagement patterns: Regularly analyze in-app engagement and raw data reports for anomalies.  InMobi regularly checks for anomalies, but please flag any that you find.
• Use secure SDK providers: Choose SDK providers known for robust security measures.
• Update measurement SDKs: Keep your measurement SDKs updated to benefit from the latest security updates of InMobi DSP and your fraud detection partners.

InMobi DSP offers a dynamic pricing structure that caters to your campaign requirements. The campaign starts with the Dynamic Cost-Per-Mille (dCPM) model. dCPM adjusts the cost of the campaign based on real-time optimizations, user engagements, and performance.   

The benefits of using the dCPM model are: 

• Flexibility: Offers flexible pricing adapting to various campaign stages.
• Efficiency: InMobi DS models continuously optimize the campaign to achieve optimal costs and Customer Acquisition Cost (CAC).