Data & Tracking
Google Tag Assistant: how to debug your tags step by step
Copy for AI
Google Tag Assistant is Google’s free tool for checking your website’s tags.
Per page and per click, you see which tags fire, which don’t, what data they send and which consent status applies.
The verdict: Tag Assistant is the fastest way to find out why a conversion is missing, counted twice or carries the wrong value. But a tag that fires isn’t yet a conversion that’s measured.
Below: how to open it, how to read a debug session and the checks to run before you publish anything.
What is Google Tag Assistant?
It’s a debugging tool for every Google tag on your site.
In its help centre, Google describes Tag Assistant as a tool to “check the implementation and operation of tags on your website”.
You review tags, events and data. You can also export and import debug sessions to share them with colleagues.
The web version and the Companion extension
Tag Assistant works via the website tagassistant.google.com. An optional Chrome extension, Tag Assistant Companion, adds two things that are otherwise hard to test:
- Tags in an iframe: think of an embedded form or scheduling tool.
- Pop-ups and new tabs: windows that open from your page.
Still looking for the old standalone extension “Tag Assistant Legacy”? Work with the web version and the Companion extension today.
Price: free. You only need a Google account.
Three ways to open Tag Assistant
Pick the route by what you want to test:
| Route | When to use it | What you see |
|---|---|---|
| Preview in Google Tag Manager | You test changes in a GTM container before you publish | Tags fired and not fired, triggers, variables, data layer, consent |
| tagassistant.google.com, “Add domain” | You want to check a live site, even without GTM access | The Google tag, events and an overview of tagged and untagged pages |
| GA4 DebugView | You want to see what GA4 actually receives | Events and parameters in real time, per test device |
Via Preview in Google Tag Manager
This is the route you’ll use most often. In your Google Tag Manager workspace, click Preview at the top right.
According to the GTM documentation, Tag Assistant then opens in a new tab. You enter your site’s URL and click Connect.
Your site opens in a new window with “Connected” at the bottom right. Everything you do on the site after that appears in the debug view.
Via tagassistant.google.com
On tagassistant.google.com, choose Add domain and enter your URL.
Tag Assistant adds a debug parameter (_dbg) to the URL and follows your session.
This also works on sites where you have no GTM access. For example, to quickly look at a new client’s Google tag.
Via GA4 DebugView
A tag that fires isn’t yet an event that GA4 processes correctly. So you also check in GA4 under Admin > DebugView.
According to Google’s explanation of DebugView, sessions from Tag Assistant or preview mode appear there automatically.
Watch out: events aren’t visible in DebugView if consent mode is active and the test user didn’t give consent. Accept the cookies in your test window, or deliberately test the declined route as well.
Here are the 4 layers you check, in order:
How do you read a Tag Assistant debug session, step by step?
Work through 6 steps, from the timeline to the platform that receives the data.
Step 1: start with the timeline on the left
On the left you see a timeline with every moment GTM records:
- the container loading and “Consent Initialization”
- “Initialization” and “Container Loaded”
- “DOM Ready” and “Window Loaded”
- every click, form submission or custom data layer event after that
Click a moment to see what happened at that point.
Now perform the action you want to test, for example submitting a form. Then look for the matching moment.
Step 2: check Tags Fired and Tags Not Fired
For each moment, Tag Assistant shows which tags fired and which didn’t.
Is your conversion tag listed under “Not Fired”? Click it. You’ll see which trigger condition wasn’t met.
Watch out: if it fires on every page instead of only after the submission, your trigger is too broad.
Narrow the trigger. Then retest.
Step 3: look at the data in Variables and Data Layer
On the Variables tab you see the value of every variable at that moment: the conversion value, the form ID, the page.
On the Data Layer tab you see exactly what your website passed on.
2 checks decide where the error sits:
- Right in the data layer, wrong in the variable: the error is in GTM.
- Already missing in the data layer: the error is on the website.
Read more about that structure in the data layer explained.
Step 4: check the consent status
On the Consent tab you see the default and updated status per consent type, such as ad_storage and analytics_storage.
Test at least 2 scenarios: everything accepted and everything declined.
In the second case, advertising tags mustn’t set cookies. How consent mode fits together is explained in consent mode v2 for Google Ads.
Step 5: check receipt in the platform
Then go to the platform itself:
- GA4: DebugView
- Google Ads: the conversion diagnostics and the conversion action
- Meta: the test events in Events Manager
In Google Ads, also open the conversion action you’re testing. Check that it’s the one set as primary:
The contact form conversion action in our own Google Ads account, October 2026. It’s set as primary, so campaigns optimise on real enquiries.
Only when the event arrives there with the right parameters has your test succeeded.
Step 6: share the session
Does a developer or colleague need to take a look? In Tag Assistant, choose More Actions and then Share to share a preview link.
You can also export a session. That’s handy for showing a problem later.
Checklist: what do you test per platform?
Use this table as your minimum test before you publish:
| Platform | What must be right | Where you check |
|---|---|---|
| GA4 | Event name, parameters, key event, no duplicate page views | Tag Assistant and GA4 DebugView |
| Google Ads | Conversion tag fires once per conversion, with value and currency, conversion linker active | Tag Assistant and conversion diagnostics in Google Ads |
| Meta | Pixel event and possibly a server event with the same event ID | Tag Assistant and test events in Events Manager |
| Consent | Default status “denied” before a choice, update after the choice | Consent tab in Tag Assistant |
| Forms | Event only after a successful submission, also without a thank-you page | Timeline and Data Layer tab |
For the Meta row, the matching event ID matters most when you also run the Meta Conversions API.
For the forms row, see form conversions without a thank-you page.
Common mistakes we find with Google Tag Assistant
These 5 come up again and again in our audits.
A conversion that fires on every page view
Often it’s a trigger on “All Pages”. Or a thank-you page that reloads via the back button.
Two GA4 configurations at once
A hard-coded Google tag in the theme plus a tag in GTM. Every page view counts twice.
Forms in an iframe
Without the Companion extension you don’t see them. And without separate measurement, they don’t count.
Test traffic in your numbers
At Tryve, the audit revealed that test hits counted as real conversions. They ended up in the Google Ads bidding strategy.
Fix: filter internal and test traffic in GA4, and preferably test conversions in a separate environment.
No retest after a form update
At Suivo, a form update silently stopped lead measurement, without any error message.
We found the cause through a root cause analysis in GTM Preview.
Read more patterns in common mistakes in Google Analytics tracking.
Debugging server-side containers
If you work with server-side tagging, your server container has its own preview mode.
Per incoming request, you see:
- which client picked it up
- which tags fired
- which outgoing requests left for GA4, Google Ads or Meta
- their status code
Test the web container and the server container together. An event that leaves the browser correctly can still fail in the server.
When is Tag Assistant not enough?
Tag Assistant shows 1 session in 1 browser.
It doesn’t tell you whether your numbers are right over a month. Or whether GA4 and Google Ads count the same number of leads, or your CRM and ad platforms line up.
For that you need a broader check. A tracking audit puts your tags, consent, conversions and platform differences side by side.
You get a prioritised list of what to fix first. Also read why conversions in Google Ads and GA4 differ.
Frequently asked questions
Is Google Tag Assistant free?
Yes. Tag Assistant on tagassistant.google.com and the Companion extension are free. You need a Google account and, for GTM preview mode, access to the container.
Why doesn’t Tag Assistant show my site as “Connected”?
Usually something is blocking the connection: an ad blocker, a cookie banner that prevents the container from loading, a redirect to a different URL or a pop-up blocker. Try a private window without extensions, and check whether the GTM snippet is on the page.
Why don’t I see my events in GA4 DebugView?
Often because consent was declined in your test session: in that case events are not visible in DebugView. Also check whether you are looking at the right GA4 property and whether the debug session is still active.
Does Tag Assistant also work for the Meta pixel or LinkedIn?
Tag Assistant shows whether the tag fires in GTM, including for Meta or LinkedIn. Whether the platform receives the event correctly, you check in that platform’s own tools, such as the test events in Meta Events Manager.
Can I use Tag Assistant without Google Tag Manager?
Yes. Via “Add domain” on tagassistant.google.com you can also debug a site that uses the Google tag directly. You then see the Google tag and the events, but not the GTM-specific tabs such as triggers.
Have your tags checked
Seeing things in Tag Assistant you can’t explain? Or want every conversion right before you invest more budget?
With a tracking audit we check your entire setup, and our tracking specialist fixes what’s wrong.
For the basics of your container, also read our article on Google Tag Manager. Get in touch if you want to discuss it straight away.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.