Verify Active View

  • The IMA SDK leverages Active View reporting to determine ad visibility and send corresponding signals to the ad server.

  • Publishers need to designate a video element during StreamManager creation for Active View to measure viewability.

  • Verifying successful viewability signal capture involves checking for specific parameters within HTTP requests and network logs.

  • A sample stream with CMS ID "2556080" and video ID "tears-of-steel-omid" is available for testing viewability implementation.

  • Publishers with custom video displays might need layout adjustments to ensure accurate metric returns and can consult the IMA support forum for assistance.
Select platform: HTML5 Android iOS

The IMA SDK must be able to tell when ads are visible to users so that it can send the correct signals back to the ad server. IMA uses Active View reporting to measure the viewability of ads. This guide explains how Active View reporting works with IMA, as well as how to verify that the SDK is able to correctly capture viewability signals.

How Active View reporting works with the IMA SDK

  1. The publisher designates a video element when creating the StreamManager.

  2. As long as the video element is viewable and unobstructed when the StreamRequest is made, Active View receives measurements on that element.

Verifying that the SDK can measure ad viewability

To check whether that the SDK is able to capture viewability signals, look for network requests sent to https://pagead2.googlesyndication.com/pcs/activeview and check for the mtos parameter. For more information, see Monitor Active View measurement.

The following sample stream is available for viewability testing:

CMS ID: "2556080", video ID: "tears-of-steel-omid"

To test using this stream, first check the network logs for ima-test-verification.js to be downloaded and then a ping fired to https://pagead2.googlesyndication.com/pagead/gen_204 at the start of ad playback.