Index Exchange (Index) uses the IAB's Open Measurement Interface Definition (OMID) to measure impressions for mobile app banners. OMID allows billing notifications to be sent to Index and DSPs when at least one pixel of an ad enters the user’s viewport. We encourage all mobile app Media Owners to adopt OMID because it standardizes the measurement of impressions and reduces reporting discrepancies between all parties. To start using OMID with Index, send API = 7 in the Banner object of your OpenRTB bid requests.
In the mobile app banner example below, the following steps describe how OMID works in an OpenRTB interaction between a publisher, Index, and a DSP.
| The ad SDK generates an ad request and sends it to your ad server. The ad server then makes a bid request to Index. |
| Index sends a bid request to the DSP. |
| The DSP sends a bid response to Index that includes the following fields in the bid response object:
|
| Index injects our OMID measurement script into the |
| Index sends a bid response to your ad server that includes the Index OMID script. |
| Your ad server conducts the final auction and if the bid wins the auction, the ad is displayed to the user. |
| When at least one pixel of the ad enters the viewport of the device, Index's OMID script determines that a billable event has occurred and fires both the Index impression notification and the DSP Note: Index uses a time to live (TTL) of three hours for our impression notifications. Our impression notification, as well as the DSP’s, are fired when the OMID measurement script runs, regardless of the DSP’s TTL for impression notifications. Index recommends against pre-rendering creatives in order to reduce discrepancies with all parties. For more information about TTL, see How Index counts impressions. |
