Skip to content

fix(analytics): separate actual editorial-guide referrals from shared category links - #76

Merged
appdevelopsk merged 2 commits into
mainfrom
fix/catalog-guide-attribution-20261107
Nov 7, 2026
Merged

appdevelopsk merged 2 commits into
mainfrom
fix/catalog-guide-attribution-20261107

Conversation

@appdevelopsk

Copy link
Copy Markdown
Owner

The current catalog_filter_landing labels every /apps?goal=... load as source=editorial_guide, including direct, bookmarked, and shared URLs. This falsely attributes traffic to our four guides. New logic compares only same-origin document.referrer path to the specific allowed guide matching the goal; reports source=editorial_guide only when matched and otherwise direct_or_shared, including suppressed/malformed referrers. No raw referrer URL or search text is sent to GA4. Existing 92 Play cards, five detail links, and manual category events unchanged. Update offline source regression test and add matching-guide guard; now ten Python test methods in that module, not executed in container. Locally executed a Node.js equivalent logic test with 9/9 cases (four guide types, missing/invalid/cross-origin/wrong guide cases). No GitHub Actions, deployment, or proof of GA4 delivery.

@appdevelopsk
appdevelopsk marked this pull request as ready for review November 7, 2026 00:06
@appdevelopsk
appdevelopsk merged commit 7eeec68 into main Nov 7, 2026
1 check failed
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