Skip to content

Fix: unify Debate Me Play Store campaign across hero and details CTAs - #132

Merged
appdevelopsk merged 2 commits into
mainfrom
fix/debate-me-store-attribution-20261115
Nov 15, 2026
Merged

appdevelopsk merged 2 commits into
mainfrom
fix/debate-me-store-attribution-20261115

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

GSC low-CTR page https://appdevelopsk.com/support/debate-me/ had 82 impressions, zero clicks over Nov 10–12. On inspecting source, hero CTA tracked utm_campaign=support_debate_me_hero while details CTA used support_debate-me; both were from the same support page, splitting campaign performance. Standardizes hero UTM and encoded Play Install Referrer campaign to support_debate-me. Keeps data-position="hero" / details and the existing download_click GA4 event so placements remain distinguishable. Adds Node source regression test scripts/test_debate_me_campaign.mjs checking 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.

@appdevelopsk
appdevelopsk merged commit 2b705b7 into main Nov 15, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant