Track Lunr search queries and search-result clicks #1519
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
Signed-off-by: Patrice Chalin <[email protected]>
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Patrice Chalin <[email protected]>
harshit-gangal
approved these changes
Jul 6, 2023
| event_category: lunrSearchEventCategory, | ||
| event_label: 'Search-result Click', | ||
| search_term: searchTerm, | ||
| value: searchResultURL, |
There was a problem hiding this comment.
from the documentation value can be a number only, so it cannot be set to string
https://developers.google.com/tag-platform/devguides/events#gtag.js_1
There was a problem hiding this comment.
For a preliminary analysis, see:
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.
searchevent to GA4 with the search term as an attribute, at no more than the debounce rate.clickevent handler to each search-result item. When a user clicks on a search result, aclickevent is sent to GA4 with the destination link and associated search term as attributes.A note about the deploy preview: the site preview will allow you to confirm that search is still functional, but it won't generate GA4 events, since analytics is only enabled in production. When
_debugis enabled (which it was for my original commit, but has since been disabled), you can at least see that the tracking functions get called, like this:I've locally built a "production" version of the site, and can confirm that GA4 is receiving both
searchandclick(related to search) events. Notice thesearch_termattribute in both events:searchevent with event count of 1:click-event screenshot/cc @harshit-gangal @thisisobate @nate-double-u