Repository navigation
feat(analytics): attribute editorial-guide visitors to filtered app results - #73
Merged
Merged
Conversation
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
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.
The four editorial guides now deep-link into allowlisted catalog filters, but automatic filter selection emits no distinct GA4 event. Add
catalog_filter_landingonce on page load for valid non-'all' goals, with only the allowlisted goal, visible result count and source=editorial_guide. This is distinct fromcatalog_filter_used(manual taps) and never sends search terms or PII. Add one static source-check test (5 tests inscripts/test_guide_catalog_links.py), preserve 92 Play cards and five app-detail links. GitHub branch source checks passed; Python test execution and real GA4 DebugView are not claimed. No GitHub Actions, deployment or published-store changes.