For Google Ad Manager Active View, an eligible impression is assumed to be measurable and not viewable until we hear otherwise from the browser using a "pingback" URL. A pingback is sent to Ad Manager at the following times:
- Impression found to be "not measurable": Pingback sent at the beginning of the user session.
- Impression confirmed as "viewable": Pingback sent as soon as 50% of a creative's pixels have been in the browser viewport area for 1 continuous second for display creatives. For video creatives, the requirement is 2 seconds.
Use Chrome DevTools to see Active View pingbacks
All viewability pingbacks can be seen in Chrome Developer Tools. The URL is typically lengthy and similar to the following viewability pingback:
https://pagead2.googlesyndication.com/pcs/activeview?
xai=Bwsd_l538U8bVPMvulAeVQBoAYWqBOAAQ&id=osdim&ti=1&r=v&adk=992535377&tt=1018&bs=1896,804&mtos=1017,1017,1017,1017,1017&tos=1017,0,0,0,0&p=119,308,219,1588&mcvt=1017&rs=3&ht=0&tfs=1398&tls=2415&mc=1<e=1&bas=0&bac=0&avms=geo&bos=1921,1374&ps=1896,9737&ss=2560,1600&pt=1397&deb=1-3-3-4-16-4-78-12&tvt=2360&op=1&uc=34&tgt=DIV&cl=1&cec=13&clc=1&cac=0&cd=1280x100&v=r20180425- Open a new Chrome browser window or tab.
- Open Chrome DevTools. Select the Chrome menu at the top-right of your browser window, then select Tools
Developer Tools. The Chrome Developer Tools window loads in the bottom half of your screen.
- Click the Network tab.
- In the Chrome browser, navigate to the URL of the page for which you would like to track viewability. As the page loads, you'll see many lines populating the Network tab.
- Click Filter
.
-
In the text field that appears, you can filter to search for specific requests, including Active View pingbacks:
- Type
activeviewto see display and video Active View pingbacks.
You can also type
pubadsto only see your page's GPT requests. - Type
- After you filter, click one of the lines in Chrome Developer Tools. In a right panel, you'll see more detailed information about that line.
What to look for in Active View pingbacks
| Parameter | General rule | Examples |
|---|---|---|
&id= Measurement ID |
This parameter helps you see whether Active View was measuring a GPT tag. | &id=osdim: GPT Tag/Request or AdXSometimes, you may see lidar even with GPT requests if the creative is from Campaign Manager 360. In this case, the pingback is likely a Campaign Manager 360 Active View pingback, and not relevant to Ad Manager. id=lidarv is the ping type used for Actve View measurements for video creatives. |
&adk=Ad Slot ID |
This ID allows you to see exactly which ad slot correlates to your Active View pingback. Filter your session by this ID to discover the match. | &adk=992535377: Pairing this ID with the GPT's ID is helpful for seeing the size of the slot and the returned line/creative. |
&bs= Browser Size |
The pixel dimensions of the browser viewport. If the values are negative numbers, the ad was probably not measurable. | &bs=1896,804: Browser viewport was 1896x804.&bs=-12245933,-12245933: Cross-domain iframe issues.&bs=-1,-1: No document.body was defined. |
&mtos=Time on Screen in Milliseconds |
This parameter's listed value contains data about the continuous length of time, in milliseconds, that a % of a creative was on-screen. List: 100%,75-99%,50-74%,25-49%,1-24% If the third list value is at least 1000, then the ad was probably viewable. |
&mtos=1002,1004,2004,2056,4099:100% on screen for 1002 ms 75-99% on screen for 1004 ms 50-74% on screen for 2004 ms 25-49% on screen for 2056 ms 1-24% on screen for 4099 ms |
&p= Position |
This list reflects the pixel coordinates of the creative as displayed on the page. Make sure these coordinates match the rendered creative size dimensions. This size may differ from the "Target ad unit size" set in the UI. If these values are negative numbers, the ad is likely outside the browser viewport and probably not viewable. |
A common reason for this is |
