Addition of GTM Data Layer to SearchBar2024. Props passed from Chall… #4237
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
…ngesHomeFilter to only fire on Challenges page.
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.
…engesHomeFilter to only fire on Challenges page.
What github.com/wevote/WebApp/issues does this fix?
This adds a data layer and Google tag every time a using types in the search bar on the Challenges Page. It captures both the key word and user ID and sends them to Google Analytics.
Changes included this pull request?
Additions to HandleKeyPress() function in SearchBar2024 including trackSearch prop from ChallengesHomeFilter to localize functionality to the challenges page