-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Migrate to Google Analytics 4 (GA4) #2181
Comments
I'll also either need access to your Netlify account, or have someone able to add an environment variable for me when the time comes (stage 2). |
@chalin Sure, could you let me know your email address for both of these? Feel free to send to julius.volz@gmail.com. |
Hello @juliusv, @chalin and the rest, I'm sure this is not the right place, but I wanted to bring to your attention that Google Analytics is not a privacy-friendly service. Would you consider moving to privacy first analytics solution like https://usefathom.com/? This would bring a lot of benefits for users, as it is faster than Google Analytics and also respects the privacy of the users. |
@LKaemmerling Well personally, I totally agree and only use plausible.io these days, which also aims to be a GDPR-compatible and very ligh-weight alternative to GA. However, it seems like the LF / CNCF uses GA to track all their different project websites. But maybe you can convince them to switch at some point :) |
Right. For the moment, the CNCF will continue using GA. |
Migration stages 2 & 3 are complete. GA4 ID is now setup via snippet injection. |
This is part of a CNCF-wide effort to upgrade project websites to GA4 since Google has deprecated Universal Analytics (UA). For more details, see:
which we've used to migrate a few CNCF projects already.
Tasks: stage 1 (no code changes are necessary)
The new GA4 stream measurement ID is:
G-80ZM8LGB96
Tasks: stage 1b - upgrade to use
gtag.js
Use GA4 setup assistant to "reconnect" the two tags.Can't use the GA4 setup assistant to connect site tags from different accounts it would seem.UA-58468480-1
, is still receiving eventsTasks: stages 2 & 3
</head>
:UA-58468480-1
, is still receiving events:Related
More:
/cc @nate-double-u @caniszczyk
Current website analytics info:
UA-58468480-1
, main and actively used tag.UA-58468480-2
: a tag planned for use over a separately deployed blog, but it seems that it never used in production AFAICT, only during test deploys from 2015-2016 (GA screenshot to be added shortly).UA-58468480-3
is the tag actively used for promcon.ioHugo layout relevant for the main tag:
docs/layouts/footer.html
Lines 9 to 18 in 918a965
Previous issue on this topic: #2175.
The text was updated successfully, but these errors were encountered: