TagSentry — Analytics & Consent QA

About

Stop shipping analytics setups that are quietly broken.

Consent Mode v2 has been mandatory in the EEA since March 2024 — and most implementations are subtly wrong. The cookie banner shows, the tag fires, the GA4 dashboard looks green… but the consent signal never actually reaches Google. No analytics dashboard tells you. TagSentry does.

TagSentry watches the analytics beacons a page sends, decodes them in real time, and gives you a one-glance verdict on whether your tags respect consent.

WHAT IT CHECKS
• GA4 / GTM — every event, measurement ID, and parameter, as it fires
• Meta Pixel & TikTok Pixel — pixel IDs and events, including POST/JSON beacons
• Google Consent Mode v2 — decodes gcs, gcd, dma & dma_cps into the four signals (ad_storage, analytics_storage, ad_user_data, ad_personalization)

WHAT IT CATCHES
• GA4 firing with no Consent Mode signal at all
• v1-only tagging (missing the mandatory v2 signals)
• A missing or late consent default (the classic silent failure)
• Missing DMA parameter for EEA traffic
• gcs / gcd disagreement (partial or double-wired consent)

BUILT FOR PEOPLE WHO DO THIS FOR A LIVING
• DevTools panel with a live feed and full parameter inspector
• At-a-glance popup verdict + toolbar health badge
• One-click white-label audit report — Print / Save as PDF, branded with your agency's name, logo, and colours — ready to send a client

PRIVATE BY DESIGN
TagSentry observes only the analytics endpoints (Google, Meta, TikTok). It has no backend and no analytics of its own — nothing you capture ever leaves your browser.

GOOD TO KNOW
Because TagSentry deliberately requests access to nothing but the vendor endpoints, tags routed through server-side / first-party domains (e.g. server-side GTM on the site's own subdomain) are outside its view and won't appear. Universal Analytics and Measurement Protocol traffic are decoded but excluded from Consent Mode verdicts.

Free.