raise support ticket
BACK

Additional Reading

Prebid

Introduction

At InMobi, we believe in supporting the needs of our Publishers and Advertisers by listening to them and delivering a better experience. Our DSPs and buyers are looking for a holistic mobile strategy that goes beyond their in-app success. With mobile web still accounting for a sizeable 21% share in a premium market like the US, InMobi is now extending its monetization solutions to mobile web to solve this marketer challenge and enable our publishers to make the most out of their mobile ad inventory. For more information, see Mobile Web On InMobi Exchange.

InMobi will transact with Prebid via the oRTB protocol. If you have any questions or require further clarity on the integration specifications, reach out to your InMobi Customer Success Manager or write to us at developer@inmobi.com.

Integration Contract Specifications

InMobi has only a Prebid Server Adapter and we support all Prebid server to server integrations. We are yet to support Prebid.js adapters. However, if publishers on Prebid JS/SDK/AMP integrations have a Prebid Server setup, which is either hosted locally OR hosted by managed solutions (offered by Pubmatic OW, Xandr PSP, Rubicon, or Index Exchange) then it would be feasible for mobile web publishers to integrate with InMobi Servers. Publishers connecting to the Prebid server via GAM could also integrate with InMobi Servers.

Refer to the following table for more clarity.

S. No 

Prebid Integration Type 

Request- Response Route 

Inventory Type 

Supported by InMobi? 

1 

Prebid JS + Prebid Server 

Prebid JS à Prebid Server à InMobi Server 

Browser 

Yes, via Server adapter 

2 

Prebid SDK + Prebid Server 

Prebid SDK à Prebid Server à InMobi Server 

In-app 

Yes, via server adapter 

3 

AMP Tag + Prebid Server 

AMP Tag à Prebid Server à InMobi Server 

Browser 

Yes, via server adapter 

4 

Prebid JS only 

Prebid JS à InMobi Server 

Browser 

No 

Note

Bidding needs to happen on a Prebid Server (Server-Side Header Bidding).  InMobi doesn't have support for Client-Side Header Bidding, where Prebid Server is not involved.

The following steps need to be followed to complete the integration set up with InMobi’s adapter.

  1. Get the latest version of the InMobi-Prebid adapter. Publishers using their own local server can access the latest version of the adapter by using the following link:  Click Here (Use this link to update the adapter’s YAML file) Or you can update to the latest Prebid server code to any release version post (and including) 0.167.0. (Refer here for more details)
  2. Publishers then need to visit InMobi UI and create the Ad Placements which then need to be mapped to their inventory. The detailed steps to create Placement IDs have been mentioned below (Section 4: InMobi UI workflow).

    Note

    The placement ID needs to be configured on InMobi’s adapter. Kindly refer to Adapter Repo to understand the steps to pass it as a bid parameter.

  3. Publishers can now start sending traffic via InMobi Adapter.

InMobi UI Workflow

Follow these steps to create mobile web placement IDs on InMobi UI.

  1. Click the Add Inventory Tab available on the Home Page and select “Mobile Website”.
  2. Enter Website Details on the new Media UI.
    • Enter all the required website details with the right categories.
    • Ensure that the categories provided are applicable as per IAB taxonomy.
    • Refer to the following table for the Rating Details. Enter a rating as applicable.
  3. Enter Compliance Details and finalize the Block Settings.
  4. Ensure that the block setting template attached to this website is selected.
  5. Create a new Placement by selecting Prebid as a partner and switching on the Audience Bidding toggle.

Note

Ensure to “Switch On” InMobi on your Prebid Platform and benefit from high bid density, fill rate, and revenue. You are all set to begin monetizing now!

Frequently Asked Questions (FAQs)

What ad formats would be supported by InMobi for mobile web supply?

Banner (display), In-stream (video), and Native.

How will InMobi handle the Ads.txt and Sellers. Json file?

Publishers will need to list InMobi.com as DIRECT in the ads.txt file and InMobi will list the publisher as PUBLISHER in the Sellers. Json file. Note that there is no change required vis-a-vis the in-app flow.

Does InMobi honor all the category and domain blocks in the oRTB request?

We do not support category and domain blocks sent to us via the oRBT request. Publishers will need to add blocks while creating the placement field in the Media UI setup. 

On This Page

Last Updated on: 16 Dec, 2022
✕

You are almost there...

By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.

I AGREE