Conversation
Member
Author
|
The directives in the GA4 CSP docs don't include these hosts, but they do seem to be used (if not necessary):
|
Member
Author
|
Turns out we actually had Google Signals enabled in our analytics config, which was responsible for the additional hosts. I've disabled it, so we shouldn't need them in our policy anymore. |
This file contains hidden or 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
1 participant
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.
FID is deprecated and we're not actively monitoring it, so let's remove it from our analytics pipeline.
This fixes an unnecessary limitation in our LoAF attribution that required LoAFs to have script entries. Some data is better than none, so we will beacon whatever is available.
This also improves CSP for SpeedCurve and GA: