Amazon Publisher Services (APS)

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 details, please refer to the following document Mobile Web On InMobi Exchange.

If you have any questions or require further clarity on the integration specifications, please contact your InMobi Customer Success Manager or write to us at developer@inmobi.com.

Integration Contract Specifications

InMobi supports all mobile web publishers available on the APS platform. Once the contract with InMobi has been signed, the following steps need to be implemented:

InMobi Adapter Integration

1. Generate Site IDs for your inventory on the APS dashboard. This Site ID needs to be mapped to the InMobi Site ID on InMobi's customer interface (CI).
2. Create Ad Placements that must be mapped to your inventory. 

3. There won't be any Tag IDs for APS mobile-web supply. You must create one fallback placement each for banner and in-stream videos. All request objects sent from APS will be mapped to the fallback placements.

   Note

   There should only be one fallback placement for each banner and in-stream video.

4. Switch on InMobi on your APS dashboard, post which you can start sending traffic via InMobi Adapter.

InMobi UI Workflow

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

1. Navigate to Inventory Settings and click Add Inventory. Select Mobile Website from the drop-down menu.

   

2. Enter all the required website details such as Name, URL, Category and Rating.
   • Refer to the following table for Rating Details. Enter a rating as applicable.

     

3. Select Child Compliance and Block Settings. Ensure the block setting template attached to this website is selected.

   

4. Select the Ad Unit and proceed.

   

5. Create a new placement and select Amazon TAM as a partner and switching on Audience Bidding. Select the “Is Fallback Placement” checkbox to create fallback placements as there is no TAG ID for M-web placements.

   

Frequently Asked Questions (FAQs)

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

We currently support only display and video ad formats but plan to extend our support to native ad formats in H2’21.

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 support viewability metrics like Moat, IAS?

Viewability will be supported in upcoming versions.

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.

If you have any questions or require further clarity on the integration specifications, please reach out to your InMobi Customer Success Manager or write to us at developer@inmobi.com.