Migration to GA4 - 3863

[t-will-gillis]

Fixes #3863

NOTE: To be reviewed only by Product Manager.

As of 9 pm on 6/30/23, by creating the new GA4 property and linking it to the UA, plus the goal conversions, it appears that the website is already connecting to GA4 without making the suggested changes. Assuming that the data keeps flowing correctly, we may not want to make the proposed changes.

What changes did you make?

• Goals in UA were automatically converted to GA4
• The position of the Google tag (gtag.js) property has been placed above Google Tag Manager as recommended by Google.
• The Google tag (gtag.js) has been identified and reformatted for easier reading.
• A new GA4 property has been setup for the HfLA website. Because this new GA4 property is tied to the previous UA property, we can continue using the previous property.
• The Google Tag Manager has not been changed- Google indicates that if Google Tag Manager is already setup it can continue to be used without changes.

Why did you make the changes (we will use this info to test)?

• Google has discontinued Universal Analytics (UA), now using Google Analytics 4 (GA4)

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

No visual changes to website.

Post migration, will need to monitor Google Analytics to confirm data is being collected as previously.
Data should be available until the end of the year, but will save remaining data.

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

From your project repository, check out a new branch and test the changes.

git checkout -b t-will-gillis-migration-to-GA4-3863 gh-pages
git pull https://github.com/t-will-gillis/website.git migration-to-GA4-3863

[ExperimentsInHonesty]

@t-will-gillis so are you suggesting we don't merge this PR and close it? Or do you want to wait longer before deciding?

[t-will-gillis]

@ExperimentsInHonesty I believe we should merge this PR. The main change is to switch the locations of the "gtag.js" and "Google Tag Manager" in _includes/head.html so that "gtag" appears first.

• The only argument to do this is because one of the Google documents mentions that this should be done.
• The counter-argument not to do this is that everything appears to be working without making this change.
• _layouts/redirect.html already is configured in this way.

The other, minor changes are adding comments and reformatting the code snippets for easier reading.

[roslynwythe]

Hi @t-will-gillis I apologize for the delay. My only request is that under "What changes did you make?", could you edit the 4th bullet point, about adding the GA4 property in config, since that change was not in the final commit?

[t-will-gillis]

Hi @roslynwythe - thanks for the comments! I edited the 4th bullet point as you suggested.

[roslynwythe]

Thank you @t-will-gillis for your research and documentation re: the GA4 migration, and updates to the head and redirect pages. All of us at Hack for LA learn so much from your contributions.