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

• From the website data stream (G-60C6Q1ETC1),
  configure cross-domain measurement for domains ending with docs.dapr.io
• Connect UA-58468480-3 from GA4 stream
• Configure GA4 website ID (gtag.js) for each release:
  • v1.10 - Use Google Analytics 4 ID for v1.10 #2945
  • v1.9 - Use Google Analytics 4 ID for v1.9 #2941
  • v1.8 - Use Google Analytics 4 ID for v1.8 #2950
  • v1.7 - Use Google Analytics 4 ID for v1.7 #2962
  • v1.6 - Use Google Analytics 4 ID for v1.6 via head-end hook #2963
  • ... (list to be completed) ...
• Confirm that the GA4 site tag is receiving events -- tagassistant.google.com was used to confirm
• Confirm that the UA site tag, UA-58468480-3, is still receiving events

Notes:

• For the main repo issue, see Migrate to Google Analytics 4 (GA4) website#71
• Each doc version is under it's own branch, and each is separately configured to use the UA ID
• Related: Ensure that page-feedback events are usable with Google Analytics 4 #2943

/cc @caniszczyk @nate-double-u

---

Current website analytics info: UA-149338238-3 registered via old analytics.js library.

[chalin]

/assign

[chalin]

Each doc version is under its own branch, and has its own individually configured UA ID. It'll be tedious to update all of those.

Do maintainers know if Azure Static Web Apps supports something like Netlify snippet injection? That would make the update to GA4 much easier for now, and in the future if the ID needs to be updated.

[chalin]

Done:

✅ Connect UA-58468480-3 from GA4 stream

Per @msfussell's 👍 given in #2941 (comment).

Also done:

✅ From the website data stream (G-60C6Q1ETC1),
configure cross-domain measurement for domains ending with docs.dapr.io

[chalin]

Docs Analytics for the past 6 months (2022/05/08 - 2022/11/08):

@msfussell @greenie-msft:

• What's the suggested cutoff point in terms of doc versions, beyond which we don't update the GA ID? Or do you want to do all in the list above?
• The rank of v0.11 in that list surprised me, given that it's pre v1.

[chalin]

I've created a doc-pages-only custom report. For a screenshot, see: dapr/website#71 (comment).

[msfussell]

I've created a doc-pages-only custom report. For a screenshot, see: dapr/website#71 (comment).

We do not need to go back more than three releases. 1.7, 1.8 and 1.9 are enough. Then 1.10 is the upcoming release in Feb 2023. Those 4 releases.

[msfussell]

Resolved