raise support ticket
BACK

Additional Reading

Overview

Getting Started

The InMobi RTB platform follows the standards set by OpenRTB Version 2.5.

Note

  • You can use the following endpoint to communicate your OpenRTB ad requests: Endpoint URL: https://api.w.inmobi.com/ortb
  • To enable forwarding of DSP-specific cookie identifiers to our demand partners, the mobile web publishers must hit our sync pixel endpoint and pass the returned ID in subsequent ad requests to InMobi in 'user.buyeruid' attribute. Sync Pixel endpoint URL (only for Mobile Web): https://sync.inmobi.com/oRTB
  • InMobi only accepts requests sent over a secure HTTPS connection.

Objective

The purpose of this section is to provide you the information and guidelines to implement an OpenRTB integration with InMobi. This document outlines ad requests, response structures, object specifications, and request parameters specific to InMobi. For more information, see OpenRTB API Specification V2.5.

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

oRTB Impression Counting for Banners

The impression counting logic varies across DSPs for banner ads, as explained below:

  • Logic 1: Some DSPs can only count viewable impressions, i.e., when the ad is visible on the screen.
  • Logic 2: Some DSPs count impressions when the ad markup is loaded into the web view.

Publishers integrated with InMobi via oRTB connections need to know the counting logic DSPs use to know whether they support viewable or non-viewable impressions and avoid reporting discrepancies.

You must ensure to use the following process at InMobi to align with DSPs that count only viewable impressions:

  1. Check whether the inventory has MRAID capabilities, represented through oRTB signal imp.api = 3 or 5.
  2. If MRAID capabilities are present, our ad markup contains tag < script src="mraid.js" > and checks for MRAID APIs during ad-load.
  3. Ensure that the impression is counted only when mraid.viewable() is true.

Note

The counting logic remains the same for Android and iOS.

Version History

Version Number

Features

Release Date

1.0

The first version of InMobi OpenRTB 2.5 Specifications (for Supply Partners)

Mar’2020

2.0

Additions to the oRTB 2.5 specification

  • Support for the NATIVE object in the bid request and bid response. Turn to ‘Section 4’ for more details.
  • Support for SKAdNetwork 2.0
  • Support for OMID using API [7]
  • Supply Chain Object
  • Support Site Objects

May’2021
3.0 Additions to the oRTB 2.5 specification
  • Support for SKAdNetwork 2.2
  • Support Blocked Categories and Domains
 Nov'2021

On This Page

Last Updated on: 09 Jan, 2023
✕

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