YALB-1565: Set Google Analytics to scope to subdomain #451
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
vinmassaro
changed the title
nJim
approved these changes
Oct 10, 2023
This was referenced Jan 2, 2024
Merged
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.
YALB-1565: Set Google Analytics to scope to subdomain
Description of work
Our current D7 Google Analytics config is causing GA cookies to be scoped to .yale.edu, which is causing too many yale.edu cookies accumulating in client browsers. This is causing issues with some services that do not ignore tracking cookies, resulting in “400 Bad Request – Request Header Or Cookie Too Large” when a user tries to access other services hosted on yale.edu.
This config change toggles the Google Analytics module config to set the cookie_domain to subdomain instead of top level domain.