Our datacenters are in US East and Singapore.
Our RTB platform supports the standards set by OpenRTB Version 2.5.
InMobi oRTB server currently supports both app objects and site objects. Please reach out to your customer success manager for any queries.
Yes, publishers can send bidfloor to denote the minimum bid for an impression, expressed in CPM.
We currently support banner, video, interstitial, and native ad formats. Please reach out to your respective customer success manager for updates.
InMobi abides by the tmax value provided by a publisher in the bid request. The ideal time to send a bid response would range between 400 - 500 milliseconds. This time range includes internet latency and is needed to maximize the bid rates offered.
The publisher needs to ensure the following:
Once the above steps are complete, the publisher can start sending ad requests to the oRTB endpoint. The request should have the placement id in imp.tagid field and should follow the norms as per the oRTB guidelines. Reach out to your customer success manager for more details.
Yes, our UI reports net revenue.
InMobi sends net bids I.e the net payable to partner/publisher. Partner/publisher need not make any further deductions/calculations.
Placement IDs are mandatory and need to be created on InMobi’s website/interface. Please reach out to your customer success manager for more details.
InMobi supports First Price Auction only.
The oRTB platform is GDPR compliant and supports boolean consent, TCF v1.1, TCF v2.0, TCF 2.1, & TCF 2.2 consent strings. However, the publisher needs to pass the string into user.ext.consent as per the OpenRTB guidelines mentioned above.
Yes, we do support SKAdNetwork 2.0. For more information, see BidRequest.imp.ext.skadn (InMobi supports SKAdNetwork 2.0 only). Additionally, you can send unhashed device IDFV (Identifier for Vendors) as device.ext.idv. Please refer to the oRTB guidelines or reach out to your customer success manager for more details.
InMobi's Global Vendor List ID is 333 (TCF V2.0 Operational).
We do not support any real time ad blocking i.e. changes to your blocked ads list will not be updated in real-time and immediately removed from your app. However, publishers can provide us the block list and we can update it on InMobi portal.
We do not support the following:
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 firstname.lastname@example.org.
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.