Amphtml: [Google Tag Manager] AMP Container preview mode, doesnt work through amp-analytics

Created on 14 Dec 2018  路  4Comments  路  Source: ampproject/amphtml

What's the issue?

Google Tagmanager preview mode doesnt show up on AMP pages, using normal tagmanager containers, pressing "preview" lets you then visit the site amd you can see an iframe keeping track of what and how different tags are triggering.

Using an amp container when you enter preview mode and visit your amp website, the preview mode iframe doesnt show up, no console error or anything eigther.

i am using amp canonically and using tagmanager through the amp-analytics component

How do we reproduce the issue?

go to Google Tag Manager and click the preview button:
image

afterwards go to the amp page where you are using google tag manager, and there wont be a giant iframe waiting for you with a bunch of useful infomation.

What browsers are affected?

all of them

Which AMP version is affected?

any version, this had been an issue atleast since march when i encountered this the first time.

Bug analytics

Most helpful comment

Reopening for the team to look into as AMP now has the potential for <amp-script> and therefore there could be some progress towards a solution. I'm not saying it should work currently, but this issue can be revisited, no?

All 4 comments

Triaging to @jeffjose 馃槃

@jeffjose Feel free to assign one of us if this is an issue on our end 馃槃

AMP containers in Google Tag Manager (GTM) do not support the debug window you are referring to. Preview mode will still let you preview your changes prior to publishing.

For a bit more context, Google Tag Manager AMP containers are built using the functionality provided by amp-analytics. This currently relies on providing configuration, but does not enable injecting script or an iframe into the page that is currently necessary for the debug window.

Feature request, duly noted. :)

Thanks for chiming in, @benjamingram. Looks like this is working-as-intended considering some of the restrictions AMP puts in place (no 3p javascript). Closing this out, but feel free to reopen @SimonHogstromRonbol if you think otherwise.

Reopening for the team to look into as AMP now has the potential for <amp-script> and therefore there could be some progress towards a solution. I'm not saying it should work currently, but this issue can be revisited, no?

Was this page helpful?
0 / 5 - 0 ratings