Repository navigation
Fix: unify Debate Me Play Store campaign across hero and details CTAs - #132
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.
GSC low-CTR page
https://appdevelopsk.com/support/debate-me/had 82 impressions, zero clicks over Nov 10–12. On inspecting source, hero CTA trackedutm_campaign=support_debate_me_herowhile details CTA usedsupport_debate-me; both were from the same support page, splitting campaign performance. Standardizes hero UTM and encoded Play Install Referrer campaign tosupport_debate-me. Keepsdata-position="hero"/detailsand the existingdownload_clickGA4 event so placements remain distinguishable. Adds Node source regression testscripts/test_debate_me_campaign.mjschecking exact HTTPS Play host, ID, source, medium, campaign, nested referrer and placements. Static test on exact branch HTML: 2 store anchors and both campaign/referrer/placement combinations validated. Node test and production GitHub Pages deployment not run/verified. Does not guarantee SERP CTR, Android install or real-user growth.