What Google Tag Assistant is
Google Tag Assistant is Google's official debugging tool for tags. It inspects a page while it loads and running, then reports which Google tags fired, in what order, and what data each one sent.
It covers the Google tagging stack: Google Analytics (GA4), Google Ads, and Google Tag Manager (GTM). Instead of guessing whether a tag is on a page, you connect the page to Tag Assistant and watch the tags fire as you click around.
Think of it as a live x-ray of your tagging. It does not change anything on your site; it only observes and reports.
Wasn't Tag Assistant deprecated?
For a while, yes — and then no. Google had signalled it would retire the older Tag Assistant Legacy extension, which worried a lot of analysts who relied on it daily.
In late December 2024 Google reversed that decision. Instead of killing the tool, it merged Tag Assistant Legacy and Tag Assistant Companion into a single, unified Chrome extension. That merged extension is now the supported way to debug Google Analytics, Google Ads, and Tag Manager, and it has quickly passed two million users.
The update also added a few things worth knowing about: Consent Mode debugging so you can see ad_storage and other consent states, support for debugging pop-ups and new tabs, and tag-coverage summaries across a site. So if a colleague tells you Tag Assistant is dead, they are working from old news.
How to use Google Tag Assistant
There are two entry points, and they lead to the same debugging experience. You can install the Tag Assistant Companion extension from the Chrome Web Store, or start from the web at tagassistant.google.com and connect your site by entering its URL.
Once connected, Tag Assistant opens a debug session for your site. From there the workflow is simple:
- Connect the page you want to test (by URL, or with the extension active on the tab).
- Interact with the page the way a real visitor would — load it, click, submit a form, complete a purchase step.
- Watch the events appear in firing order as you go.
- Open an event to see the tags it triggered and the exact data they sent.
- Check the Output and Data Layer views to confirm hits went where you expected.
Free tracking check
See what’s visible on a real site.
Run a free browser-based scan — no login, no install, ~10 seconds.
Run a free checkWhat Tag Assistant shows you
The value of Tag Assistant is in the detail it exposes. For each event on the page it can show you:
- A Summary view listing events and the tags that fired, numbered in the order they ran.
- The Data Layer tab, showing the current dataLayer state and every push, event by event.
- The Output section, showing where each hit was sent and surfacing errors.
- The underlying API calls — the gtag() or dataLayer.push() that configured each event.
- Consent Mode states such as ad_storage, so you can see how consent affected which tags ran.
What Tag Assistant can't tell you
Everything above describes one debugging session, run by you, on your machine, right now. That is exactly the boundary of the tool.
Tag Assistant only sees what happens while you are actively watching. It does not sit in the background and check your live site for real visitors. It will not notice when a deploy next Tuesday removes a container snippet, when a consent banner update starts blocking the pixel, or when a theme change quietly breaks the checkout tag.
It also debugs the page you test — usually a homepage or a single funnel path. A pixel can be perfect there and missing on the one landing page your paid campaign actually points to.
None of this is a flaw. Tag Assistant is a debugger, not a monitor. The mistake is treating a clean debugging session as proof that tracking will stay healthy in production.
Tag Assistant checks once — production changes every day
Most tracking failures are not present the day you build the tag. They arrive later, silently, through a change nobody connected to analytics: a redesign, a plugin update, a new consent tool, a developer removing a script they didn't recognise.
A manual debugger cannot catch those, because by definition nobody is debugging at the moment they happen. The gap between 'it worked when I checked' and 'it broke three weeks later' is where most wasted ad spend and missing conversions live.
That gap is what continuous checking is for. A monitor re-runs the check for you on a schedule, on the pages that matter, and tells you when a tag that used to fire stops firing — without you remembering to open Tag Assistant again.
A practical workflow: debug once, then keep watching
The two approaches are complements, not rivals. A healthy setup uses each for what it is good at.
Use Tag Assistant when you are hands-on: building a new tag, handing off to a developer, or diagnosing a specific problem. It is the right tool for deep, interactive debugging.
Then, once tags are live, put a continuous check on the pages that drive revenue — your key landing pages, checkout, and lead forms — so a future change can't break tracking without anyone noticing. Debug once with Tag Assistant; keep watching automatically after that.
TrackCanary's free checkers let you confirm GTM and GA4 tags on a live URL in seconds, and its monitoring re-runs those checks for you over time.
Next step
Confirm your tags are live — then keep them that way
Tag Assistant is great for hands-on debugging. When you want a fast second check on a live URL, or ongoing monitoring so tracking can't break silently, start with a free TrackCanary checker.