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

• Create a GA4 site tag under the CNCF projects account.
  The new GA4 stream measurement ID is: G-60C6Q1ETC1
• Configure GA4 website ID (gtag.js) through Netlify snippet injection, "Google Analytics 4 - only in production", just before </head>:

  {% if CONTEXT == 'production' %}
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-60C6Q1ETC1"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
  
    gtag('config', 'G-60C6Q1ETC1');
  </script>
  {% endif %}

• Confirm that the GA4 site tag is receiving events
• Confirm that the UA site tag is still receiving events

Notes:

• Corresponding subdomain issues:
  • blog.dapr.io: Migrate to Google Analytics 4 (GA4) blog#92
  • docs.dapr.io: Migrate to Google Analytics 4 (GA4) docs#2861
• Followup: Drop Universal Analytics (UA) #72

/cc @caniszczyk @nate-double-u

---

Current website analytics info:

• UA site tags, all registered via analytics.js:
  • UA-149338238-1, main site tag
  • UA-149338238-2: blog
  • UA-149338238-3: docs

[chalin]

GA4 is up and running for the main site. Later cleanup will be tracked via #72.

[chalin]

I'm going to reopen this issue until I can find out where the blog sources are and how the blog gets published -- @yaron2 can you help?

[msfussell]

@chalin - Work with me and @greenie-msft or @nyemade-uversky on this. For the blog site you should have access to all the sources now in the repo. Can you confirm?

[chalin]

Thanks @msfussell. I confirm that I have access.

[chalin]

Closing once again since the main-site migration is done. Migration for subdomains (blog and docs) is tracked separated. For links to their issues, see the opening comment.

[chalin]

FYI, I've created, for illustrative purposes, a custom report that shows only docs.dapr.io page views. This illustrates how we can generate reports for separate subdomains (mimicking the UA property setup that existed before):