TagSentry — GA4 & Consent Mode Debugger icon

TagSentry — GA4 & Consent Mode Debugger

by andreas.nelvik.engebretsen · Developer Tools
Manifest V3 in_app
View in Chrome Web Store Data as of 16 Oct 2026

Debug GA4, GTM, Google Ads, Meta & TikTok tags live. Check Google Consent Mode v2 gcs/gcd signals are actually correct.

Users
8
+1 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#215K
#180K among extensions
Version
0.3.1
updated 25 Sep 2026

Users

monthly, 3 months
048Jul 2026Sep 2026Oct 2026
Latest, 16 Oct 2026: 8 usersMove the mouse over the chart for any month

Ratings count

monthly, 3 months
001Jul 2026Sep 2026Oct 2026
Latest, 16 Oct 2026: 0 ratingsMove the mouse over the chart for any month

The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.

About TagSentry — GA4 & Consent Mode Debugger

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 is a tag debugger that 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 debugs • GA4 & Google Tag Manager — every event, measurement ID, and parameter, as it fires • Google Ads — conversion pings on the Google tag, with their own consent signals • Meta Pixel & TikTok Pixel — pixel IDs and events, including POST/JSON beacons • GA4 ecommerce items — pr1, pr2… unpacked into a readable table • 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, and a legacy v1 tag hiding behind a correct v2 one • A missing or late consent default — the classic silent failure • Tags that fire before the visitor answers the banner • Missing DMA parameter for EEA traffic • gcs / gcd disagreement (partial or double-wired consent) • Hits the browser never actually delivered (ad blocker or network) — so "it fired" never means "it arrived" Built for people who do this for a living — all free • DevTools panel with a live feed, full parameter inspector and copy buttons • Click a finding to step through the exact hits that evidence it • How-to-fix snippets you can paste into gtag / GTM • Session summary — what fired, how often, how much never left • Pin a baseline, change your tagging, reload, and compare before/after • Full keyboard navigation of the hit feed • At-a-glance popup verdict + toolbar health badge • One-click audit report — Print / Save as PDF, ready to send a client It tells you when it cannot be sure A finding that stops being reported because the tag stopped firing looks identical, on the wire, to one that was fixed. TagSentry refuses to call that a fix, and says why. Unknown Consent Mode encodings are reported as unknown, never guessed. That is the whole point of a QA tool. Optional upgrade: white-label reports ($29, one-time) Put your agency's name, logo, contact line, and accent colour on the exported report so it goes out under your brand. Everything above stays free forever — the upgrade only changes how the report is dressed, never what it finds. Paid once via ExtensionPay (Stripe); no subscription, no account needed for the free tool. Private by design TagSentry observes only the analytics endpoints (Google Analytics, Google Tag Manager, Google Ads conversion measurement, Meta, TikTok). It has no backend and no analytics of its own — nothing you capture ever leaves your browser. The single exception is the optional upgrade: if you buy or restore white-label branding, the extension checks that entitlement with extensionpay.com. Details in the privacy policy. 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. Google Ads coverage is the conversion traffic sent by the Google tag; classic googleadservices.com / doubleclick.net pixels are out of scope. Universal Analytics and Measurement Protocol traffic are decoded but excluded from Consent Mode verdicts. Free to install and free to use, with one optional $29 one-time upgrade for white-label report branding.

Growth

WindowUsersChangeRatingsRating
7 days+1+14.3%00.00
30 days+1+14.3%00.00

Version history

9 versions recorded
0.3.125 Sep 2026
0.3.014 Aug 2026
0.2.91 Aug 2026
0.2.828 Jul 2026
0.2.727 Jul 2026
0.2.324 Jul 2026
0.2.221 Jul 2026
0.2.118 Jul 2026

Details

Category
Developer Tools
First seen
15 Jul 2026
Size
282 KB
Languages
de, en, id, nl, vi, tr, ca, da
Pricing
in_app
Extension ID
okhpllfgdakpjmdmgeejdeljdhfgdknp

Permissions and risk

Elevated riskimpact 4, likelihood 3
Permissions
webRequeststorageactiveTab
Site access
*://*.google-analytics.com/**://analytics.google.com/**://*.googletagmanager.com/**://www.google.com/ccm/**://google.com/ccm/**://*.facebook.com/tr**://facebook.com/tr**://connect.facebook.net/**://analytics.tiktok.com/*

Alternatives to TagSentry — GA4 & Consent Mode Debugger

Extensions that rank for the same store searches or share the Developer Tools category, ordered by users