-
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) #2175
Comments
I'd be glad to create a new GA4 site tag under the GA CNCF-projects account if you'd like. We could then link the UA tags to the GA4 tag (and back). |
Hey, thanks! That would be helpful if you have time! |
CC @juliusv |
I'm fine with switching off the tracking! I think mainly the CNCF still wanted it though? |
Yes. I think the foundation would need the data |
This sounds like a quote from a cyberpunk thriller TV show :) Sounds good to me for now in any case if you want to change things over to the new GA and CNCF account. |
Sure...happy to lead this effort @juliusv |
Sounds good to me. I think all current GA code on the site is just this, so it should be easy to replace: Lines 9 to 18 in 918a965
|
Hi all. I'm leading the GA4 migration effort for CNCF. FYI, I'll be taking over this effort from @thisisobate. Thanks @thisisobate for kicking things off! I'm going to open another issue so that I have edit access. |
Please close in favor of: |
Closing as requested. |
Google is deprecating the Universal Analytics tag over Google Analytics 4. This effect will commence on July 1, 2023. You can learn more here
This issue is part of a CNCF-wide effort to upgrade project websites to GA4 since Google has deprecated Universal Analytics (UA). For more details, see:
Migrate CNCF websites to GA4 cncf/techdocs#108, including reference to:
We should migrate the Prometheus website to GA4 as soon as possible so that by 2023Q3, when UA data collection stops, we will already have 1+ year of historical data.
Tasks, stage 1 (no code changes are necessary)
Tasks, stage 2 (optional, can be done later)
The text was updated successfully, but these errors were encountered: