Tracking Health Scanner
A real Chromium browser loads the page and records every network request. You get a graded report of what fired, what fired twice, and what fired before it should have.
Public pages only. Initial load, desktop viewport, US locale, no clicks. Reports get a shareable link; 10 scans a day per person.
What it checks
- Duplicate page_views
Two Google tags, a hardcoded gtag next to GTM, or a container loaded twice — the three ways GA4 double-counts.
- Consent gaps
Is there a CMP? Does it actually talk to Google Consent Mode? Does the Meta pixel fire before anyone clicks Accept?
- PII in hits
Email addresses in GA4 or ad-platform requests — a terms violation that can get the property terminated.
- Dead tags
Universal Analytics hits still firing years after the shutdown.
- Every vendor
70+ signatures: GTM, GA4, Ads, Meta, TikTok, LinkedIn, Clarity, Hotjar, HubSpot, Klaviyo, Segment, consent platforms and more, with IDs, request counts, weight and first-byte timing.
- Server-side detection
First-party endpoints for gtm.js and /g/collect, so you can see whether server-side tagging is really in play.
Whether add_to_cart carries value, whether the purchase event fires once on the thank-you page, whether tags behave after Accept. That needs a scripted journey replayed on a schedule — which is the monitor we're building next.