AMP-Ads can not reach 100% Viewability

[Pubstream]

Description

Every AMP ad has a viewability tracking issue. They only track up to 50% but never 100%. The reflective attribute "mtos" always transports "0,0,1009,1009,1009" regardless of whether the image was 100% in the viewport or not.

This only happens with AMP ads (id=ampim), the regular (id=lidar2) ads reach 100% viewability

Reproduction Steps

1. Open the Chrome developer toolbar, "Network" tab.
2. Go to the AMP Ad demo page
   https://amp.dev/documentation/examples/advertising-analytics/amphtml_ads_vs_non_amp_ads/
3. Scroll to the AMPHTML Display section
4. Look at Network tab for ActiveView ping https://pagead2.googlesyndication.com/pcs/activeview
5. We now see an incorrect MTOS value (0,0,1006,1006,1006
6. Scroll to Regular View
7. Check the network tab for ActiveView again
8. We now see a valid MTOS value (1009,957,51,331,65).

We would also expect 100% for AMP advertising.

This visibility problem occurs everywhere, not just on the demo site!

Relevant Logs

No response

Browser(s) Affected

Chrome

OS(s) Affected

Mac and Windows

Device(s) Affected

No response

AMP Version Affected

No response

[erwinmombay]

@powerivq @calebcordry would y'all mind triaging this

[erwinmombay]

@powerivq could you give your input on this?

[powerivq]

Upon checking the example, the amp-analytics config in the creative is
https://pagead2.googlesyndication.com/pcs/activeview?xai=AKAOjsvKTWtDz6XD17r-tqdrNRMbOPGIEfFOWbsQhSSXeeoSfJe51V_m_v3LPHA2YIbunajmSXSc7OE9O2pf7E2W54qOS-6U9NYEpbSq36oG16RJ42uxftxHhLi8lVlo2aXpfyg&sig=Cg0ArKJSzJEw-l6TlUUkEAE&id=ampeos&o=${elementX},${elementY}&d=${elementWidth},${elementHeight}&ss=${screenWidth},${screenHeight}&bs=${viewportWidth},${viewportHeight}&mcvt=${maxContinuousVisibleTime}&mtos=0,0,${maxContinuousVisibleTime},${maxContinuousVisibleTime},${maxContinuousVisibleTime}&tos=0,0,${totalVisibleTime},0,0&tfs=${firstSeenTime}&tls=${lastSeenTime}&g=${minVisiblePercentage}&h=${maxVisiblePercentage}&pt=${pageLoadTime}&tt=${totalTime}&rpt=${navTiming(navigationStart,loadEventStart)}&rst=${navTiming(navigationStart)}&r=de&isd=${initialScrollDepth}&msd=${maxScrollDepth}&avms=ampa

mtos is set to 0,0,${maxContinuousVisibleTime},${maxContinuousVisibleTime},${maxContinuousVisibleTime}. Therefore it always starts with 0,0. It appears that AMP is transmitting as directed.

[Pubstream]

Yes, it was always 0,0
But it should be represent the 75 - 100% viewability.

See https://support.google.com/admanager/answer/6123557?hl=en

We have huge issues in our AdManagers because of to low Viewability values, impossible to optimize without a fix.

[powerivq]

@Pubstream I see. AMP fires analytics events according to the ad's configuration. In this case, the ads instructs AMP-AD to send 0,0,x,x,x to activeview. It do not have visibility into why the creative is configured this way. You will need to contact your Google Ads POC to find out why, and what effects it has on your GAM account.

[Pubstream]

@powerivq thx you for the input, i will ask again my GAM Account Manager (he send me initial to you 🤷 )

Could you tell me where i can see the current configuration ? Where can you see the Analaytics Template with these variables?

That would help me to point my Account Manager directly to the problem.
thanks a lot!

[powerivq]

@Pubstream I was looking at the raw creative HTML. There was a section of amp-analytics. To be clear, this should be set by the advertising network (in your case GAM) and you should not need to interfere.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.