How Index counts impressions

Depending on the ad format The format of the ad space on the publisher's site. Banner and video are kinds of ad formats., Index Exchange (Index) counts an impression from a publisher The owner of a website or app where advertisements are served. when the impression notification meets the impression counting criteria provided in the following table. The table also includes the Media Rating Council (MRC)'s recommended best practices for each format type.

Format Impression counting criteria MRC counting best practice

Web banner

Index expects to receive the billing notification in the adm field within the time to live (TTL) of 600 seconds.

The MRC recommendation is that an impression is considered billable when the ad markup (adm) “begins to render” on the user’s browser. For more information about ad impression measurements, see the MRC's Desktop Display Impression Measurement Guidelines.

Mobile app banner

  • Index prefers that mobile app publishers support OMID for measuring impressions because Index receives the billing notification when at least one pixel of the ad renders, which reduces impression count discrepancies. The TTL for OMID-based impression measurement is three hours. For more information on OMID, see Measuring impressions with OMID.

  • If you use burl to send billing notifications, Index expects to receive the billing notification within the TTL of three hours.

  • If you do not use burl or OMID to send billing notifications:

    • Index expects to receive our adm-based notification within the TTL of 600 seconds.

    • Index recommends against pre-rendering creatives in order to reduce discrepancies.

The MRC’s recommendation is that an impression is considered billable when at least one pixel of the banner is painted in the viewport of the user’s device. As a result, Index strongly recommends that publishers integrate with the OM SDK so that Index can measure impressions using OMID and avoid adm-based notification. For more information about ad impression measurements, see the MRC’s Mobile Application Advertising Measurement Guidelines.

Video (instream A video ad that displays before (pre-roll), during (mid-roll), or after (post-roll) video content that the user is consuming. The video ad plays within video content, similar to watching TV with commercials. and outstream An ad placement where the video is not the focal point of the screen and plays with sound-off by default. They can display before, between, or after text, or accompanying streaming content (pre-roll, mid-roll, and post-roll ads), as an interstitial ad, or display as a standalone ad such as slideshows or native feeds.) on web, mobile app, and STV Streaming TV (STV). Video content that is shown across any device with an internet connection, for example a Connected TV (CTV).

Index expects to receive the billing notification from our VAST Video ad-serving template (VAST). A communication standard between ad servers and video players in XML-format that describes the video player's expected behavior. adm within the TTL of:

  • One hour for video (instream and outstream) on web.

  • Three hours for mobile app and STV.

The MRC’s recommendation is that an impression is considered billable when the first frame of the video creative A digital ad made available in various creative types, defined by their size in pixels such as 300x250px. is rendered on the player. For more information about ad impression measurements, see the MRC’s Digital Video Impression Measurement Guidelines.
Native on web and mobile app

Index expects to receive the billing notification in the imptrackers[] array or eventtrackers[] array in the native adm within the TTL of 300 seconds.

Not available

 

Index does not count impressions in the following situations: