fix(csp): allow GA via Tag Manager #10715
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
caugner
changed the title
argl
approved these changes
Mar 15, 2024
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.
Summary
(Extracted from #10687.)
Problem
We're migrating to GA4 and have connected our UA Property, which causes the
analytics.jsto loadgtag.js, but that origin (as well as the origins used bygtag.jsfor measuring) are not in our CSP, so we're seeing very low numbers in GA4.Solution
Add the GA4-related origins to
script-src,connect-srcandimg-srcrespectively.Ref: https://developers.google.com/tag-platform/security/guides/csp#google_analytics_4_google_analytics
How did you test this change?
#10687 is deployed on stage, and we don't get any CSP errors there.