AMP in GA4 does not working

Hi,

AFAIK, Google Analytics 4 doesn’t fully support Google AMP yet. There are some workarounds but isn’t officially supported at the moment.

So, does the AMP support mentioned in the description only refer to UA?

Yes, maybe the description is unclear, I will have a look and modify it accordingly if necessary.

Just a follow up, digging further, it looks like there is a way to do AMP tracking on GA4, so keep an eye on future versions, I decided to introduce it as an experimental feature. I’ve tested it and it works, the basics. I just need to figure out some stuff about more complex tracking features like events and stuff. I want it to be fully functional at release.

@luisbarroslcp you should test 5.8 and see how it goes, it has GA4 support for AMP pages.

Hi Alin! I am now at the point in my setup where getting AMP working is my top priority, and I got a chance to try out this new feature.

So far it’s working in terms of inserting the <amp-analytics> code into the AMP pages, but I’m not seeing the hits in GA DebugView screen, nor the Realtime report. I confirmed that in the same browser, hits to the normal view of a post register in DebugView, but when I go to /amp/ there’s no events being logged.

I tried it with two different local sites/profiles. Both are using the official AMP plugin: https://www.ads-software.com/plugins/amp/

Here’s the output I get in the footer (formatted in VS Code for readability):

<amp-analytics type="googleanalytics" config="https://amp.analytics-debugger.com/ga4.json" data-credentials="include" class="i-amphtml-layout-fixed i-amphtml-layout-size-defined" style="width:1px;height:1px" i-amphtml-layout="fixed">
	<script type="application/json">
		{
			"vars": {
				"GA4_MEASUREMENT_ID": "G-YR9TXEGJ6E",
				"GA4_ENDPOINT_HOSTNAME": "www.google-analytics.com",
				"DEFAULT_PAGEVIEW_ENABLED": true,
				"GOOGLE_CONSENT_ENABLED": false,
				"WEBVITALS_TRACKING": false,
				"PERFORMANCE_TIMING_TRACKING": false,
				"documentLocation": "${canonicalUrl}",
				"config": {
					"G-YR9TXEGJ6E": {
						"groups": "default"
					}
				}
			}
		}
	</script>
</amp-analytics>

Here’s what’s inserted in the header:

	<script src="https://cdn.ampproject.org/v0/amp-analytics-0.1.mjs" async="" custom-element="amp-analytics" type="module" crossorigin="anonymous"></script>
	<script async nomodule src="https://cdn.ampproject.org/v0/amp-analytics-0.1.js" crossorigin="anonymous" custom-element="amp-analytics"></script>

And there’s some CSS mentioning analytics:

		amp-analytics,
		amp-auto-ads,
		amp-story-auto-ads {
			position: fixed !important;
			top: 0 !important;
			width: 1px !important;
			height: 1px !important;
			overflow: hidden !important;
			visibility: hidden
		}

		amp-story {
			visibility: hidden !important
		}

		html.i-amphtml-fie>amp-analytics {
			position: initial !important
		}

I am using the Template Mode “Reader”, I am not sure if that is the problem. I will try changing that and report back.

Ok, I tried setting the AMP plugin to “Template Mode: Transitional” and now I’m not seeing the <amp-analytics> tag at all.

I went back to “Template Mode: Reader” and tried changing the theme. I originally had it on the “AMP Legacy” theme, which is where I was at least seeing the <amp-analytics> code. When I switched it to twenty-seventeen (to match the test site I’m working on) the AMP was working, but the <amp-analytics> code was still missing.

It seems like for me the only way to make the <amp-analytics> code show is to use “Template Mode: Reader” along with the “AMP Legacy” theme.

Can you describe the setup you have where you got it working? What type of AMP theme is it and how is AMP configured? Maybe you were using a different AMP plugin?

Honestly I want to just get rid of AMP entirely! But first I have to finish this Analytics stuff before the deadline ??

Template Mode: Reader with AMP Legacy theme

OK I think I found the problem! For some reason the normal “GA Debug” Chrome extension doesn’t work for sending AMP traffic to the DebugView the way it does for normal traffic.

I tried adding ?_dbg=1 as recommended in the GitHub of the author of the hack you incorporated, and that made it work!

I’ll keep testing and let you know if I find anything else.

My next goal is to insert a custom dimension to identify the hit as AMP. If you have any advice about that, I would love to hear it ????

Already fixed for all AMP modes and themes: https://github.com/deconf/Analytics-Insights/commit/ca59d886f50e890c7035e0227ed5e2b69e8d766e

I haven’t had time to fully test it, but it passed all the basic tests up now. A few more and is ready for release.

Cool! I guess the note is just to mention in the docs when they exist that to test you can use ?_dbg=1.

Any plans to add a parameter/dimension to identify AMP traffic to AIWP? I would love to just use yours, as well as to see how you did it so I can add more parameters.

I could, you should open a feature request on github for that. Please note that all dimensions are functional on AMP too. So if you have them enabled you could take a look at the tracking code to see how they are structured.

You know what, I got it working with the help of the Thyngster docs!

With this hook I can insert all my normal parameters, including my “Screen Type” one, which has a post-amp one for AMP!

add_action('aiwp_analytics_amp_config', array($this, 'action_aiwp_analytics_amp_config_to_insert_global_parameters'));

…

public function action_aiwp_analytics_amp_config_to_insert_global_parameters(AIWP_Tracking_GA4_AMP $aiwp_amp) {
		
		$config = $aiwp_amp->get();

		$parameters = $this->get_all_global_parameter_values();

		foreach ($parameters AS $parameter => $value) {
		
			$config['extraUrlParams']["event__str_$parameter"] = $value;
		}

		$aiwp_amp->set($config);

		return;
	}

Beautiful work on this plugin! Everything was ready to go once I parsed the somewhat-confusing docs from Thyngster!

Now I just need to figure out how/if I can have a second tracker in there!

• This reply was modified 1 year, 11 months ago by Jer Clarke.

it worked, thanks!