AI-generated Key Takeaways
-
The IMA SDK utilizes Active View reporting to determine ad visibility and send signals to the ad server.
-
Active View reporting relies on the
StreamDisplayContainer
andVideoStreamPlayer
for viewability measurements. -
Developers can verify viewability signal capture by checking for
active_view_vide_measurable_impression
in HTTP requests and themtos
parameter. -
A sample stream (CMS ID: "2556080", video ID: "tears-of-steel-omid") is available for viewability testing.
-
Custom video display implementations may require layout adjustments to ensure accurate viewability metrics are returned.
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
The
StreamDisplayContainer
is created by passing in an instance ofVideoStreamPlayer
.Active View receives measurements on that
VideoStreamPlayer
(getLocationOnScreen
andgetGlobalVisibleRect
).
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.
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.