Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GA4 may continue working using legacy UA setup #1253

Open
janbrasna opened this issue Jul 13, 2024 · 0 comments · May be fixed by #1254
Open

GA4 may continue working using legacy UA setup #1253

janbrasna opened this issue Jul 13, 2024 · 0 comments · May be fixed by #1254

Comments

@janbrasna
Copy link
Contributor

In #1213 updating mkdocs & dep versions a new GA/GTM setup needed to be used. Without a proper GA4 migration all the previous GA3 config was omitted under the impression it can't be gathering data anymore.

Fortunately Alphabet migrated GA3 UA properties to GA4 for those who never migrated it themselves. https://support.google.com/analytics/answer/11583528#zippy=%2Cwhat-happens-to-my-ua-connected-site-tag :

"For Google Analytics 4 properties that rely on Universal Analytics tagging for data collection, there is no additional risk when those Universal Analytics properties are shut down and deleted by Google. Once Google deletes your Universal Analytics property we’ll automatically continue to use your Universal Analytics tagging for your Google Analytics 4 property, however only if your UA tags are still on your website. If you decide to remove your UA tags, you can replace them with a Google tag."

There's even continued (limited) support for legacy analytics.js:

GA3-UA-GA4

The template here overrides the defaults providing its own GA snippet based on the old analytics.js anyways, so this legacy path is still valid, just needs reconfiguring. (Expecting the GA3 being auto-migrated to GA4 and the analytics.js ingestion enabled by default as a result.)

@janbrasna janbrasna linked a pull request Jul 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant