Tag Master decodes GA4, GTM, Google Ads, Meta, TikTok, Adform, Adobe and 45 more platforms in real time — then tells you what each one got wrong, and switches on that platform’s own test mode when you need it.
Decoded in real time
Everything you normally check across GTM Preview, DebugView, the console and three vendor helpers
Every dataLayer push lists the requests it produced, matched by event name across platform spellings. Then it puts what the push carried next to what the tag actually sent.
A funnel checklist across the pages actually walked, a client ID that changes mid-journey, domain hops with no linker, and the chain from ad click to conversion.
Every hit decoded into readable parameters — account ID, event name, value, currency — not raw query strings.
Hits proxied through your own first-party endpoint are still recognised, labelled and decoded. Paste your preview token and they appear in your sGTM session.
Live state for all four signals, plus a red flag listing every vendor that kept firing while ad consent was denied.
Google has Tag Assistant and DebugView. TikTok, Snap, Microsoft UET, Tealium, Criteo, Yandex, Hotjar and Adobe Launch each have their own — switch one on and its test tool starts receiving your events.
Drop any container onto any site, persisting across reloads, then open Tag Assistant ready to connect. Snippets are saved per container — paste once, reuse forever.
Click any element and get a ready-to-paste GTM recipe: stable selector, condition options with copy buttons, and a variable that extracts prices automatically.
Every tool here is free. The difference is coverage.
Swipe the table to see the other tools
| Capability | Tag Master | Tag Assistant | Omnibug | Meta Pixel Helper | Analytics Debugger |
|---|---|---|---|---|---|
| Platforms decoded | 62 | Google only | ~69 | Meta only | GA4, GTM, Adobe + |
| Server-side GTM hits recognised | ✓ | – | – | – | – |
| Explains why a GTM trigger fired | – | ✓ | – | – | – |
| Flags vendors firing without consent | ✓ | – | – | – | – |
| Element picker to GTM trigger | ✓ | – | – | – | – |
Three steps, no configuration
Add Tag Master from the Chrome Web Store. No account to create.
Click the icon on any site you want to inspect. Reload to catch hits from the first request.
Decoded hits, dataLayer events, consent state and a one-click audit of what's missing.
Practical walkthroughs for the problems this tool was built for
Preview needs container access, changes the page, and only speaks for one container. Here is how to verify GTM from the requests it actually produces.
Read the guide →Adding to cart rarely fires one event. What a real storefront pushes, which of them a trigger should use, and the four kinds of push that are never the answer.
Read the guide →You open the inspector on a working shop and nothing arrives. The events are real, they fired, and they are not in window.dataLayer. Four platforms route them somewhere no extension can read, and each has a different place to read them instead.
Read the guide →Why the debug stream stays empty, what a /g/collect request actually contains, and how to check GA4 on production without switching debug mode on.
Read the guide →Read consent parameters straight from the hits, tell a default apart from an update, and find the vendors that fire regardless of what the banner says.
Read the guide →How deduplication actually works, what eid looks like in the browser request, and the five mistakes that turn a single order into two conversions.
Read the guide →Yes — every feature, with no account, no login and no paid tier. The extension collects no data; captured sessions stay in your browser.
Tag Assistant covers Google tags only and runs its debug session from an external site. Tag Master decodes 62 platforms in the side panel next to the page — including Meta, TikTok, LinkedIn, Adform, Criteo and Adobe Analytics — and adds server-side GTM detection plus Consent Mode V2 auditing. The two work well together: Tag Master can open Tag Assistant for you with the container prefilled.
Yes. Hits are matched by request path rather than hostname, so GA4 requests proxied through your own first-party endpoint are still recognised and marked. You can also paste your X-Gtm-Server-Preview token so requests from your browser appear inside your server container preview session.
No. There is no account, no telemetry and no external server. Everything is processed and stored locally.
Blocking only affects tracking requests for the vendors you tick, and only while the toggle is on. The site own functionality is untouched, and blocked hits are still listed so you can see what would have been sent.
Install once, debug every platform
Add to Chrome — FreeChrome 116+ · MIT licensed