Add discovery_engine_attribution_token to GA4 pageview #3951
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
leenagupte
approved these changes
Mar 25, 2024
andysellick
force-pushed
the
add-discovery-token
branch
from
832b8fb
to
80a75fd
Compare
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.
What / why
Adds a new parameter to the GA4 page view,
discovery_engine_attribution_token. This is a unique token generated by each search result, used for debugging purposes in search. Additional work will be done infinder-frontendto add this token as a meta tag so this code can read it - on all non-search pages this attribute will be undefined in the page view.Visual Changes
None.