You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: the UA tag can't be connected from the GA4 tag because it isn't using the gtag.js library, but even if it was, we'd want to avoid sending main-site events to the promcon UA tag and so it is easier to avoid connecting them than to setup filters (that would be useful only for a short period anyways, until UA is dropped by Google).
@juliusv - I've setup GA4 via Netlify snippet injection, while keeping the UA site tag as it is currently -- so no code changes were necessary.
All that will be left to do later is to drop the UA-specific code from the website (#246), once you've decided that you don't want to use that property anymore, or it stops receiving data (in 2023).
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 (stages 1, 2 & 3):
G-80ZM8LGB96
), configure cross-domain measurement to promcon.io.</head>
:UA-58468480-3
, is still receiving eventsNotes
/cc @nate-double-u @caniszczyk @juliusv
Current website analytics info:
UA-58468480-3
Hugo layout relevant for the main tag:
website/layouts/default.html
Lines 58 to 67 in 0cf826e
The text was updated successfully, but these errors were encountered: