Support App + Web properties on Google Analytics (gtag)

[jeffjose]

App + Web properties is a new feature that Google Analytics that unifiies measurements on app and web properties.

Support this in gtag.js

cc/ @avimehta @zikas @zhouyx

[dgtmas]

Did you notice official website amp.dev was deindexed by Google? They are progressively hiding this technology so that it dies on its own and they don't need to assume its death.

[katsar0v]

I agree with @dgtmas, AMP is dead and currently used only by low quality online news websites.

[sethjico]

Google has NOT YET killed amp it seems. I continue to receive notifications with the subject - "New AMP issue detected for site xyz.com" - which would have stopped if Google had killed AMP.

However, silence of Google ppl is really really irritating. At least they can show some responsibility, and at least come up and tell honestly what they plan to do with AMP (in relation to this GA4 drama that has been started.

[aleballe]

I just wanted to point out that the assignee (@kristoferbaxter) of this issue doesn't seem to work at Google anymore, according to his Linkedin.

So all our feedback may fall on deaf ears.

[Zerototh]

This just keeps getting better and better. We've stopped working on AMP and are slowly removing it from our sites. What we've learned is that there's no reason to waste precious resources when you can basically achieve the same results without it...

-------- Original message -------- From: Alexander Ekman @.> Date: 28/06/2022 13:37 (GMT+01:00) To: ampproject/amphtml @.> Cc: Zerototh @.>, Manual @.> Subject: Re: [ampproject/amphtml] Support App + Web properties on Google Analytics (gtag) (#24621)

I just wanted to point out that the assignee @.***) of this issue doesn't seem to work at Google anymore, according to his Linkedin. So all our feedback may fall on deaf ears.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1168607316", "url": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1168607316", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[sethjico]

After 6 years of hardwork, and true obedience to the Gods at Google - this is what one gets. :-((

Zero accountability - from the largest internet company of the globe.

Abiding to AMP rules forced us to structure the data of our site such that it became easy for anyone to clone it. And now, no response at all from the Almighty!

Shame

[99coder99]

After the long wait on this issue (and still counting), I did the following:

Each of my site is using Google Analytics with a different Google account. So around a month back, I simply removed the Google Analytics tracking code from two of my sites which covered similar topic, and had similar traffic and similar earnings. One account was migrated to this non-AMP GA4, and other was continuing on the old Universal Analytics. Both of the analytics tracking code was removed, and AMP functionality was retained. A third site, having lower income and lower traffic, I made it GA4 and thus it got converted to non-AMP.

After a month of observation, the earnings and traffic on the first two sites remains the same as it was before the Analytics code removal. However, the third site has seen almost 40% drop in incoming traffic from Google, although the search trend on that topic indicates steady queries.

So in a way it looks like Google is penalizing you if you move from AMP to non-AMP. Eliminating the tracking code of Analytics, (thereby retaining AMP), retains the status.

Will update further after one more month.

Any other observations please?

PS: I am getting inclined to dropping Analytics code and retain AMP. If one is NOT using Analytics data extensively, what's the point? You using Analytics code on your site is actually more for Google, rather than for you. :)

[Zerototh]

@99coder99Please keep us posted!You seem to have done this right about the same time as the may core update.Have you taken the possibility of that affecting your non-amp site into account when analyzing the results?But I'm nevertheless very interested in getting an update from you in a month or so.

-------- Original message -------- From: 99coder99 @.> Date: 29/06/2022 17:26 (GMT+01:00) To: ampproject/amphtml @.> Cc: Zerototh @.>, Manual @.> Subject: Re: [ampproject/amphtml] Support App + Web properties on Google Analytics (gtag) (#24621)

After the long wait on this issue (and still counting), I did the following: Each of my site is using Google Analytics with a different Google account. So around a month back, I simply removed the Google Analytics tracking code from two of my sites which covered similar topic, and had similar traffic and similar earnings. One account was migrated to this non-AMP GA4, and other was continuing on the old Universal Analytics. Both of the analytics tracking code was removed, and AMP functionality was retained. A third site, having lower income and lower traffic, I made it GA4 and thus it got converted to non-AMP. After a month of observation, the earnings and traffic on the first two sites remains the same as it was before the Analytics code removal. However, the third site has seen almost 40% drop in incoming traffic from Google, although the search trend on that topic indicates steady queries. So in a way it looks like Google is penalizing you if you move from AMP to non-AMP. Eliminating the tracking code of Analytics, (thereby retaining AMP), retains the status. Will update further after one more month. Any other observations please? PS: I am getting inclined to dropping Analytics code and retain AMP. If one is NOT using Analytics data extensively, what's the point? You using Analytics code on your site is actually more for Google, rather than for you. :)

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1170121338", "url": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1170121338", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[99coder99]

@Zerototh - will share.

From your earlier post, I see that you've "stopped working on AMP and are slowly removing it from our sites."

1 - Would you like to share your observations post the change you implemented? 2 - Specific reasons for sticking to Analytics (instead of sticking to AMP)?

[Zerototh]

@99coder99We've opted to remove AMP completely from one of our sites that serves Sweden where we live. Its a newish site so the traffic wasn't there to be affected :)Why I bring it up as an example is because I feel so much more free when developing without AMP and the speed/UX/Mobile usability etc doesn't suffer at all. As someone mentioned earlier, AMP helped out a lot a few years back but now...We're also working on removing AMP gradually from our main swe site but it's slow going. Especially when I read about your experience when removing AMP...We also have a more globally targeted site that we've opted to keep AMP for now. It's just too much work to migrate it rn. I really went overboard developing that one...AMP really does help out with its caching when you got users from all over the place. So that's another reason we stick with it.But when it comes to solid info about how our migration might affect rankings/traffic etc we won't see that for a few more weeks. If this issue is still here I'll post an update of our experiences then.I have no specific reasons for sticking to GA4, my reasoning is more about removing AMP as we can do everything without it and the fear of waking up one day and realizing that G discontinued AMP. And not supporting GA4 for AMP is a very strong warning for me at least. Enough that I'll do the work needed to sleep better.Although I have to say that I like GA4. It was a welcome upgrade. I'll be using GA4 going forward for sure. Long post... sorry about that!

-------- Original message -------- From: 99coder99 @.> Date: 30/06/2022 11:47 (GMT+01:00) To: ampproject/amphtml @.> Cc: Zerototh @.>, Mention @.> Subject: Re: [ampproject/amphtml] Support App + Web properties on Google Analytics (gtag) (#24621)

@Zerototh - will share. From your earlier post, I see that you've "stopped working on AMP and are slowly removing it from our sites." 1 - Would you like to share your observations post the change you implemented? 2 - Specific reasons for sticking to Analytics (instead of sticking to AMP)?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[sethjico]

Thanks a lot @99coder99 and @Zerototh for the inputs. Love the idea of ditching Google Analytics as mentioned by 99coder, if it is not of too valuable use.

When I use GA, I simply look at most visited pages of my website and the city/country from where traffic comes. That's all. Rest of the data is being stored and used by Google God, not used by me. I think most of us have similar minimal requirement, so I am ok to discontinue GA.

Does anyone know of any other AMP compatible alternative to GA? (I just need data on most visited pages and city/country).

Thx in advance.

[gerardorn]

Looking through Search Console, on the Discover tab, I saw this. Has anyone seen something similar? Somehow it is not showing AMP articles anymore

[cnxsoft]

@gerardorn It's still showing AMP articles on my website.

[sethjico]

Its wrong to assume that AMP is dead. It remains ambiguous.

Yesterday, I received AMP error mail as follows:

And after fixing it, in less than 24 hours I received AMP Fix mail:

Plus...

AMP is clearly showing up as a "Dedicated Section" on Console.

So you see, AMP is not yet dead. Most probably the GA4 team and AMP team were not in sync when they launched GA4. Since deadline of 2023 is still far away, they may as well make GA4 compatible with AMP.

Really ridiculous on part of Google to not come up and tell what's going on.

[Zerototh]

@99coder99 @sethjico

I promised to get back to you when we made the move and removed AMP.

So...we made the move and removed AMP 10 days ago. So here's what we've learned so far.

Keep in mind it's been 10 days. So things might change drastically in the future :)

GSCPerformance Clicks, Imp, CTR and avg position basically all the same as before. No change during these 10 days compared to the 10 days before. Page experience Good URLs for mobile is now 100%. We went down to as low as 96,9% during 3 days after the migration but it’s back up to 100% now. Core web vitals The same as with PE, we went down a few days (about 25% down) in Good URLs but spiked up again to the same level we had before migration. Mobile usability No change in mobile usability at all. All pages = mobile-friendly pages. 10 days in it seems we’re still ok with Mobile CWV SC Insights Reset due to migration to GA4. So if you enjoy/use the SC insight, be sure to save/use the data before you switch over to GA4. Page Speed Insights This is were we see the most effect. We went down a lot. From 98-100 score independent of page to 70+ depending on if we have ads enabled or not. With AMP (and server side optimization) we saw no discernible difference between pages with or without ads. Without AMP there’s a big difference. When using our site as regular users we don’t see this drop at all. The site feels a lot faster without AMP but that might just be confirmation-bias from our part ofc.

Time will tell!AdSense We moved from manual ads to auto-ads and have seen a +26% jump in ad revenue and impressions. During the years we’ve had AMP we’ve tried enabling auto-ads on AMP several times but never got it to serve ads properly. So it’s a welcome revenue boost.The traffic was basically the same so even though it isn’t a perfect comparison it’s enough for us to count it as a success from a revenue standpoint. GA vs G4 I enjoy using GA4. We’ve been using GA for so long that we basically, over time, stopped using more and more of its features. With GA4 we’ve rediscoveredand also discovered new features. So it might be the ”I got a new toy” effect but nevertheless I enjoy the UI and I also use it a lot more than before.We’ll be using GA4 going forward in all our sites (hopefully with our AMP sites as well come July 2023). Summary, overall impression It seems our migration has been a success this early in the process but we’ll have to keep an eye out for a few more weeks. We did not request reindexing of our content through GSC but let G crawl our content and figure out we don’t have AMP on our pages by itself. We've "lost" about 50% of our AMP enhancements in GSC during our first 10 days. I have not removed the AMP code from the server so if it turns out we crash and burn with this experiment we can simply go back to serving AMP again without too much hassle. it would be a shame though as the new site looks so much better and is a dream to develop. The dips in different metrics described above I believe are in large part caused by myself and some bugs that I had to fix after launching the non-amp version of the site. Without #development=1 you’re left to reacting on data after the fact instead of being able to test it before launch/publishing. The html-validator like W3C’s Markup Validation Service is wonderful though. We still have AMP implemented on our international sites so I’ll be following this thread. Good luck with your sites!

1 juli 2022 08:47:21 +02:00, skrev sethjico @.***>:

Thanks a lot @99coder99 https://github.com/99coder99 and @Zerototh https://github.com/Zerototh for the inputs. Love the idea of ditching Google Analytics as mentioned by 99coder, if it is not of too valuable use.

When I use GA, I simply look at most visited pages of my website and the city/country from where traffic comes. That's all. Rest of the data is being stored and used by Google God, not used by me. I think most of us have similar minimal requirement, so I am ok to discontinue GA. Does anyone know of any other AMP compatible alternative to GA? (I just need data on most visited pages and city/country). Thx in advance.

— Reply to this email directly, view it on GitHub https://github.com/ampproject/amphtml/issues/24621#issuecomment-1171997845, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARUJCG3V572GFQ65W4THNALVR2H7TANCNFSM4IYEIGZA. You are receiving this because you were mentioned.Message ID: @.***>

[sethjico]

Thanks @Zerototh for the inputs. A week ago, I removed AMP but only from part of my website. Specifically the Britain section.

Result - google search traffic dropped to less than 50%, adsense earnings dropped almost 60%. Rest of the sections (USA, Australia, Canada, etc. which are AMP) continue to maintain the usual traffic and earnings. So in my case, AMP removal is hitting hard. Will run the experiment for a total of one month on the British section of website to see if anything changes or at least returns to normal.

Also note, after 1 week of switch to non-AMP, I also made adsense code to go with auto-ads during this weekend. What's worse is that ads have stopped showing altogether on that British section for most of the times (last 2 days observation). Obviously earnings have dropped further.

Anyone else has any other observations? It is sick to see that Google continues to remain silent on AMP and GA4.

[sethjico]

One more important thing that I want to add:

I recently learnt that new-age browsers (like Brave Browser) are becoming very popular because they don't support AMP, and above all, they don't show any online ads including Adsense ads Adsense ads are simply cutoff.

Basically, its a loss on both fronts if one continues with AMP and hosts Adsense ads.

If push comes to shove, then in the long run, I'm planning to make my site with paid login only. No more AMP or non-AMP nonsense, no more adsense dependency, and no more GA4 this or that.

[Zerototh]

@sethjicoAdd to that the removal of third party cookies that removes the possibility to follow a user.My thought:If you're able to go paid login (which by the way is amazing!) then you might look at first member login to be able to leverage the data generated by your users without relying on third party cookies. For example you should then be able to feed that data to your ad provider and get better targeting or even sell ads manually to businesses interested. And again, well done with building a brand where you have the option of going paid login! Got me thinking on how we could do that in the future :)/ZerotothSent from my Samsung device

-------- Original message -------- From: sethjico @.> Date: 19/07/2022 17:15 (GMT+01:00) To: ampproject/amphtml @.> Cc: Zerototh @.>, Mention @.> Subject: Re: [ampproject/amphtml] Support App + Web properties on Google Analytics (gtag) (#24621)

One more important thing that I want to add: I recently learnt that new-age browsers (like Brave Browser) are becoming very popular because they don't support AMP, and above all, they don't show any online ads including Adsense ads Adsense ads are simply cutoff. Basically, its a loss on both fronts if one continues with AMP and hosts Adsense ads. If push comes to shove, then in the long run, I'm planning to make my site with paid login only. No more AMP or non-AMP nonsense, no more adsense dependency, and no more GA4 this or that.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.> [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1189180794", "url": "https://github.com/ampproject/amphtml/issues/24621#issuecomment-1189180794", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[milindmore22]

@sethjico Just wanted to add that the so-called new age browser has 0.05% market share, it blocks Adsense and AMP but it displays their partner ads and affiliations, so users are more a target audience for them, I will advise you to learn about your audience using Analytics before concluding to any decision.

[zoolyka]

I think this topic is going to the wrong way, please discuss unrelated things elsewhere, here we only want to hear about GA4 AMP support progress, instead of how to drop AMP completely. Thanks.

[sethjico]

Good morning - Woke up to all great thoughts!

@zoolyka - if "this topic is going wrong way," its because the great Google God (or none of its legal representatives) have bothered to say a word. They set the rules, then they break them of their freewill with complete silence without any clarity leaving everyone in the lurch.

In the absence of clarity, people have no choice left, but to look for alternatives - including taking off AMP altogether. (If that's what Google wants, let them speak clearly).

@milindmore22 - I (and anyone else) can't argue on which browser has what market share today, & how soon things will change in near future - as the tech world moves very fast. We webmasters can't control what users use. But looking at the buzz on social media (especially Twitter), it seems that users (especially in EU & Asia) are moving to Brave in masses (and there are other browsers).

To me (as a webmaster), the end result is loss of earnings - all this despite being obedient to the strict rules set by Google.

Biggest issue here is Google's continued & absolute silence on this important matter. In the absence of clarity, we are left with no options but to experiment to see what clicks.

[newmuis]

Agreed with @zoolyka, let's please keep this on topic. Cleaning up this thread from mostly off-topic comments.

We also would like to have a solution to provide continued support of Google Analytics within AMP, but until we have found a way for this to work, there are no meaningful updates to share in this thread.

[yasinturkdogan]

I made the GA4 integration using the guide described in here but the numbers are not matching with the regular Google Analytics. I am guessing it is due to the Google AMP cache. Clearing the cache for each page will be something we will have to consider as well. Its really frustrating not to have any official update from Google. Time is ticking and we won't be able to collect enough historical data when the Google Analytics stops working.

[newmuis]

Thank you for your report @yasinturkdogan. Just to clarify: are you aware that Google Analytics 4 reports things a bit differently?

It would be great to understand whether the discrepancies you see are based on the differences in the products themselves vs. differences in the instrumentation.

Thanks again!

[Lovntola]

My solution is very simple to integrate GA4. I set up GA 4 in Tag Manger (Web not AMP) and simply added the code. (My fist idea was put only the

Bernd Note: I have a AMP only site.

[99coder99]

@newmuis - thanks for finally putting some thoughts as a Google representative.

This issue is now more than 2 years old, and there seems to be no clue yet about what (if any) is the way forward for AMP. After reading your messages, I assume that you are from the GA4 team (and not the AMP team).

Can you please connect with a Google AMP team person, and suggest if Google AMP validator (in Search Console & other functions) can simply ignore the GA4 code portion, and pass an AMP webpage by checking only the non-GA4 AMP code? That will be a win-win for everyone in the interim till this clears up.

Whatever the final fate of AMP comes out to be (whether AMP stays alive or is killed) - at least the above GA4 code bypass will be a suitable fix. Thanks

[newmuis]

Hi @99coder99, I am actually an engineer on the AMP project, not from Google Analytics. I understand the length of time that the issue has been open, but as I mentioned in a comment above, unfortunately until a viable solution has been found, there aren't many updates to be shared in this thread.

[sethjico]

Everyone is thoroughly confused with Google, and it approach. Not just this GA4 issue, even the AUTO-ADS on AMP continue to be a long running problem, with the standard "they aren't able to provide ETA" See this issue: https://github.com/ampproject/amphtml/issues/28254#issuecomment-630988350

[ghost]

I have no Idea why the AMP project comes up and tell the community what the status of the project is. There has been no tweets, blogposts, youtube content in over a year now. Thats not a good sign for an active project. Most of the members of the project have left. I until a good enough reason from the amp team declare the project as DEAD. This project is what beating a dead horse feels like..... for 3 years. Move on people , the world has already

[ghost]

This has been a Greedy-Google project from day one , from amp-email, to amp-web to stories. This was all to keep users on the google platform which covered by the mask of speed, which really was just preloaded pages served via the cache. long live open web.

[stephengardner]

Auto Ads:

@sethjico AMP auto ads works for us.

Sometimes it takes a few days for the Ads to show up, but we have no issues, provided you have set it up properly in your AdSense account and added the proper AMP auto-ads code. We've implemented it on numerous sites.

"AMP is dead" comments:

There are also a few comments here that are speculative and incorrect, including one that said the amp.dev site was being de-indexed, which is obviously false based on a Google search. And while I don't work for Google, it has been relayed to me directly by Google employees that AMP is not going away or being de-indexed.

AMP is a "greedy Google project"

@neerajklite's concerns are the popular anti-AMP approach, however, the entire Google "removing the lightning bolt and not requiring it for top-stories" anymore approach is to counter that opinion. It's literally not getting priority except the obvious priority of being faster than any other type of webpage you can possibly create and thereby boosting your Core Web Vitals, speed, user retention, lower bounce (due to speed) and thereby your SEO, significantly. Yes, that's true, because it's being Cached and Pre-loaded. Is caching and pre-loading a "favoritism approach"? No. Why? Here's why:

You can remove the entire Google caching infrastructure by hosting your own AMP cache with the "Signed exchange" approach (https://developers.google.com/search/blog/2019/04/instant-loading-amp-pages-from-your-own). Google has intentionally removed the whole "we are the arbiter of your pages" argument.

Despite what critics say, it's significantly more pleasant to click on a fast-loading webpage on mobile, even for me, in the USA. And a significant portion of the world doesn't have 4g+ in practical application.

Why can't Google just cache and pre-load non-AMP pages?

There's a security context that also matters here, as well as an overhead context on Google's end. AMP pages are inherently secure, and inherently guaranteed to be fast, based on a simple AMP validation scan that Google can perform on the backend. Google doesn't want to cache your slow Wordpress generated pages with a dozen plugins necessarily. Google will probably end up caching and pre-loading notoriously "mobile-friendly" pages, but at a certain base of why AMP was created pertains to these factors which allows it an ease of caching and preloading.

This gives the Google search engine an advantage over others like DuckDuckGo and Brave, but specifically because it's legitimately more user-friendly. They want users to have a better experience. And, as mentioned, a large part of the world isn't on your ultra-fast mobile connection.

Conclusion

It's ridiculous that Google hasn't properly responded to this thread more frequently, even to say that GA4 is not supported yet. They should have said what @newmuis said, multiple times, because even saying "Sorry, we have no ETA" is better than saying nothing.
But they haven't. Nonetheless, other comments here have shown that it is POSSIBLE (albeit less-than-ideal) to support GA4 without an official guide.

But the comments here diverting the entire conversation should be skipped such as to not burden this thread with irrelevant information and polluting the point.

At the core, the negative comments should be a signal that we need more communication, so please, Google, communicate better, in whatever channel is appropriate.

Cheers

[ghost]

Google saying they are not killing AMP just means they will continue to support the existing pages which includes amp only websites people invested a lot in making. Its a liability more than anything else. And for God sake top carousels loads amp pages 99% of the times, you can have an html only page and amp will still supersede that coz its from the cache coz they can preload it. So please top misleading.

So please kill this project already and stop fooling users. This project has failed

[sethjico]

@stephengardner - with all due respect, some of your comments are not in sync.

• "Sometimes it takes a few days for the Ads to show up" - If it takes a few days, you still call it "working"? That too from a giant like Google? Unexpected?
• The official github thread on AUTO AMP ADS indicate they aren't working, and there is no response from Google. Yet, you are confidently saying that they work (?)
• Everyone here realizes how much time & effort goes in building an AMP site. Now everything has shattered with GA4. Still there is no response from the big G, or at the most - "as I mentioned in a comment above, there aren't many updates to be shared in this thread."
• To stay AMP compliant, site owners ended up structuring the webpage which made it easy for scammers to copy entire site easily, and float multiple copied versions of their own. The original site owner gets hit always - first by putting in effort to stay AMP compliant, then when the site content is easily copied over, and then (the most painful part) - complete silence & irresponsibility on part of the big G.

Now the masters will simply delete these comments citing "Cleaning up this thread from mostly off-topic comments."

Better if they declare that AMP is dead, and close it altogether.

[99coder99]

Hello @stephengardner, appreciate you putting up your thoughts & observations in a nice way. Helpful.

But beg to differ on many points, like "it takes a few days for the Ads to show up" There is no logic to why it take few days?

Also, forget about AMP-AUTO-ADS, even their RESPONSIVE ads don't work. Here's the response confirming the same - https://github.com/ampproject/amphtml/issues/28554#issuecomment-640712400

I've also added to the other github discussion about ADS and how a webmaster should be careful to selectively serve ads rather than blindly following Google's recommendation. If anyone is interested - it is https://github.com/ampproject/amphtml/issues/28254#issuecomment-1229404936.

No update from Google is really disappointing - whether it is on AMP or on AUTO-ADS.

[newmuis]

Let's try to keep this thread about one thing (GA4 support in AMP). It will greatly help to keep the discussion organized. For issues with auto-ads, please comment in the thread(s) on that topic. This will help members of the project determine how they can help, and will also help future searchers discover the problem and solution, as the conversation will be in one place.

As for support for GA4, this is still something that is being investigated. In the interim, you may consider:

• Using GA4 in AMP workarounds that are available from the wider developer ecosystem
• Including the GA4 JavaScript snippet on the page and allowing the page to be invalid AMP
• Using of any of the analytics vendors already supported by AMP

Once there is any further update to share, I will provide it in this thread.

Now the masters will simply delete these comments citing "Cleaning up this thread from mostly off-topic comments."

I am trying to keep this thread organized and on-topic, so people can tell what's going on. Note that I intentionally did not delete the comments. I've marked them as off-topic, but they may still be expanded and read by those who do want to read that conversation.

[Lovntola]

FYI: I found this: https://www.thyngster.com/how-to-track-amp-pages-with-google-analytics-4

[tajstar]

Looks like it's been about six months since there was an update. With UA support ending in July, I wanted to see if there was any update to AMP support in GA4. Even just to know it was still being worked on would be helpful.

[tripledm]

I think its the end of AMP it will stop along with GA3, the writing is beyond on the wall

[Beethoven]

I'm using Zaraz from Cloudflare for all analytics. Since it loads third-party tools in the cloud it works perfect for AMP pages, and all pages is valid AMP.

[NashIlli]

Im using Google Tag Manager with AMP. But it's strange because in GTM, when you select an AMP container, GA4 doesnt appear available. So I suppose it doesnt work well.

[dgtmas]

If you look at amp-wp plugin for WordPress, they are struggling to keep users onboard since its core AMP is abandoned. Their code is full of fallback patches because there is no response from AMP project on multiple topics (like GA4 and amp-img transition to native img). So we need an official statement about the future of AMP, silence is plain stupid.

[99coder99]

@newmuis - I guess it is still the same standard "there are no meaningful updates to share in this thread." status, even after such a long wait?

[newmuis]

Yes, that is still the current state, unfortunately. Updates will be shared to this thread as they happen.

[Jhkier]

I've read the summary above - And just wanted to clarify...

I really don't have time for the back/forth and will need to make a call... So, we should just abandon AMP?

[joshcp]

In Google Analytics, there's a banner now that says:

On July 1, 2023, this property will stop processing data. Starting in March 2023, for continued website measurement, you should create a new Google Analytics 4 (GA4) property, or one will be created for you based on your original property and reusing existing site tags.

Does this automatic migration apply to AMP properties as well? Is there a better place to ask this question?

[newmuis]

@joshcp this disclaimer unfortunately does not apply to AMP properties.

[Jhkier]

@newmuis - So, at what point to we just disband AMP Altogether?

[pabloaugusto]

News?

[pabloaugusto]

My solution is very simple to integrate GA4. I set up GA 4 in Tag Manger (Web not AMP) and simply added the code. (My fist idea was put only the part, but I tried the whole code. Okay the AMP Validator says not valid. BUT there is no error in GSC since 4 week. Maybe Google not longer interested to check AMP? So I collect both GA and GA4 data and will wait for a official solution. If there will no one come, and it looks so. I have a not vaild AMP page but in the end of the day AMP work with this solution with all the AMP benefit. That is why I choice AMP for speed benefit not for Google benefit, this is history. No change in ranking, visitor behaviors etc since this 4 weeks.

Bernd Note: I have a AMP only site.

@Lovntola Still have no warnings at GSC or rank drops?

[sethjico]

u guys still believe that amp will remain supported? chatgpt has killed google... adsense income is hitting rock bottom..... mass layoffs at google continue... n u ppl still believe google will continue with a tiny piece called amp which has flipflop past....like so many products google will announce its end anytime. That person claiming to be from google keep copy-pasting only 1 thing "unfortunately. Updates will be shared to this thread as they happen." n he has done that since last 1 year. Before that someone else said that same thing. wake up n move on....ppl at google cant be trusted...they themselves r not confident of their jobs ....n u expect amp to continue feeling sorry for wasting so many yrs of hard work to make amp site.. will it be ok if I too wish that karma to hit back at google ppl for wasting our hard work n keeping in uncertainty even till now?