Migrate to GA4 (Google Analytics) #109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replacing the previous GA code (UA-XXXXXXXX-X) with the GA4 code (G-XXXXXXXXXX) in the .env settings did not properly link the site to Google Analytics.
Jim Lacy at UWisconsin shared this code, which he came up with to migrate GeoData@Wisconsin to GA4: https://github.com/WIStCart/GeoData/commit/b95385bc7034a6a5c22d9b521e440043e5788ef2.
Key files changed:
Jim reported that the previous analytics file (app/assets/javascripts/analytics.js) is no longer being used. This contains the old Big Ten analytics code that collects custom events.