Migrate to Google Analytics 4 (GA4)

[chalin]

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:
  • A suggested migration process,
    which we've used to migrate a few CNCF projects already.

Tasks: stages 1, 2 & 3

• Create a GA4 site tag under the CNCF projects account.
  The new GA4 stream measurement ID is: G-5Z1VTPDL73
• Connect the following UA IDs from the GA4 web data stream:
  • Main site - UA-105170809-1
  • Blog - UA-105170809-1 - same as main site
  • CD - UA-105170809-2
  • cd.apps.argoproj.io - UA-105170809-6, console. The site ID appears in argo-cd-cm.yaml. Look into GA4 for React apps. @alexmt says it isn't required
  • Events - UA-105170809-9
  • Rollouts - UA-105170809-3
  • Workflows - UA-105170809-7
• Register domains for cross-domain tracking:
  • Exactly match domain name: argo-cd.readthedocs.io
  • Exactly match domain name: argoproj.github.io -- all projects other than CD are served from this domain
• Use GA4 site tag via gtag.js:
  • Main site - UA-105170809-1 - Enable UA and GA4 analytics #107
  • CD
    • Prerequisite: Support migration to Google Analytics 4 (GA4) - upgrade mkdocs-material to v7.1.8+ argo-cd#10850
    • docs: Use new Google Analytics 4 ID (latest) argo-cd#11291
    • docs: Enable Google Analytics 4 for 2.5 (stable) argo-cd#11323
    • 2.4
    • 2.3
    • 1.8?
  • Events - UA-105170809-9 - docs: Use new Google Analytics 4 site tag argo-events#2237
  • Rollouts - UA-105170809-3 - docs: Use new Google Analytics 4 site tag argo-rollouts#2299
  • Workflows - UA-105170809-7 - docs: Use new Google Analytics 4 site tag argo-workflows#9766
• Confirm that the GA4 site tag is receiving events from:
  • Main site
  • CD
  • Events
  • Rollouts
  • Workflows
• Confirm that the UA site tag(s) are still receiving events:
  • Main site - UA-105170809-1
  • CD
  • Events - UA-105170809-9
  • Rollouts - UA-105170809-3
  • Workflows - UA-105170809-7

Later

• Google Analytics migration follow up #118

/cc @nate-double-u @caniszczyk

---

Current website analytics info:

• GA console https://analytics.google.com/analytics/web/#/report-home/a105170809w198079555p192782995
• UA site tag prefix seems to be UA-105170809 with
  • UA-105170809-1: used by ...
    • This repo? Well, it was at some point, see 8edd65d.
    • blog.argoproj.io - which seems to be a custom domain over Medium
  • UA-105170809-2 used by CD
  • UA-105170809-3 was assigned to argo-rollouts, but isn't currently used.
  • UA-105170809-7 is used by argo-workflows:
    https://github.com/argoproj/argo-workflows/blob/3a32b1b4ef30edf02340cbd92004109d1ae1c143/mkdocs.yml#L26-L28
  • UA-105170809-9 (and previously UA-105170809-2?) used by argo-events (docs: Set-up Google Analytics tracking argo-events#1406):
    https://github.com/argoproj/argo-events/blob/38f5e249cd030935081b5c71fb8129a38e1d2ea9/mkdocs.yml#L12-L14
• The following doc sites don't appear to have GA enabled:
  • https://github.com/argoproj/argo-cd: https://argo-cd.readthedocs.io
  • https://github.com/argoproj/argo-rollouts: https://argoproj.github.io/argo-rollouts

[chalin]

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).

[chalin]

Recording here that @alexmt requested that we consolidate accounts (which is the preferred way of managing analytics under GA4).

[chalin]

@alexmt - Do you have a preference for the account I use to create the GA4 site tag? The choices are either (a) the CNCF projects account, or (b) your current argo-site account (105170809).

Edit: was talking with @caniszczyk, and the CNCF strongly recommends option (a) for all CNCF projects. I'll assume that you're ok with this option and create the account next week if I don't hear from you before then.

[chalin]

@alexmt et all: Can you grant me contributor access to the Argo Netlify account? As mentioned elsewhere, given the Argo website setup, I think that it will be simpler to use Netlify snippet injection to setup GA4. Oops, scratch that. You're not yet using Netlify.

[chalin]

@alexec @sarabala1979 @whynowy - I see that you are editors for the blog, which is hosted by Medium. Could you change the config to use the following Google Analytics ID: G-5Z1VTPDL73 instead of the UA site tag? Thanks. /cc @alexmt

[chalin]

Recording here that @alexmt requested that we consolidate accounts (which is the preferred way of managing analytics under GA4).

@alexmt - do you want the events of the CD app (cd.apps.argoproj.io) to also be consolidated together with the rest page view events for the Argo project docs? The app's path is distinct from doc site pages.

[alexmt]

Hello @chalin . I think it is not required. We've configured GA for https://cd.apps.argoproj.io/ mostly to get Google Analytics integration feature of Argo CD, not to track how many people visit https://cd.apps.argoproj.io/.

[chalin]

I'll assume that you've backported GA4 ID to the older versions of the docs that you felt it necessary for. Closing this issue since latest, stable and v2.5 have been successfully migrated 🎉