GTM Preview won't connect: why Tag Assistant says not connected or shows no tags.
- “GTM Preview not connecting”
- “Tag Assistant not connected”
- “Tag Assistant could not connect to the site”
- “Google Tag Manager preview mode not working”
- “GTM preview connected but no tags”
- “Tag Assistant timeout when connecting”
- “GTM debug mode not showing”
- “server-side GTM preview empty”
Baris Asa, tracking consultant, London · Last checked: 9 November 2026
When GTM Preview won’t connect, Tag Assistant opened your page but couldn’t find your container on it. Usually the snippet isn’t on that page, something blocks it (an ad blocker, a cookie banner, a content security policy), or a redirect drops the debug parameter. First check: the browser’s Network tab, filter forgtm.js, and look for your container ID.
That one check splits the problem (it needs a desktop: in Chrome, right-click the page, Inspect, Network tab, type gtm.js in the filter box, reload). No gtm.js request usually means the snippet isn’t on the page, though a cookie banner or a script-delay setting can hold it back, so click Accept and scroll once before you conclude. Blocked or failed means something stopped it. A 404 means the container file doesn’t exist yet. A 200 means the container loaded: go to the redirect section if it still won’t connect, or to Tags Not Fired if it connects but nothing fires.
Two terms, once. Preview is GTM’s test mode: it runs your unpublished changes in your browser only. Tag Assistant is the Google tool that opens your site in Preview and shows which tags fired on each event.
Not connected, or connected with no tags?
These are two different faults, and they get different fixes. Name yours before changing anything.
| WHAT YOU SEE | WHAT IT USUALLY MEANS | FIRST CHECK |
|---|---|---|
| Not connected, or a timeout | Container not found on the page | gtm.js in the Network tab |
| Connects, then drops on a later page | Left the domain, or a page has no container | Which page it dropped on |
| Connected, tags under Not Fired | Container loaded, trigger didn’t match | The event the tag should fire on |
| Server container Preview empty | Requests don’t reach the tagging server | The server-side checks below |
The first two rows are connection problems and this note covers them. The third is a trigger problem: the container is fine, and the tag waited for something that never happened. The last has its own note.
Is the container on the page you opened?
Tag Assistant can only connect to a container the page actually loads. Google’s Tag Assistant help puts this first: confirm the tag is on the page, try another page on the site, and check the tag loads in the browser’s developer tools.
What to look for in the Network tab:
- No
gtm.jsrequest at all. The snippet isn’t on this template. Common on landing page builders, a separate blog platform, a checkout or booking step run by another system, or a staging site. - A
gtm.jsrequest with a differentid=GTM-.... The site runs another container: an old one, an agency’s, or a plugin’s. Tag Assistant looks for the container you clicked Preview in, so it won’t connect to yours. - A 404 on your container ID. In my experience this is a container that has never been published. Publish a version (an empty one will do) and the file exists.
- Only
gtag/js?id=G-..., nogtm.js. The site has a Google tag installed directly, not GTM. Preview has no container to show.
If the snippet was edited (a custom loader, a renamed dataLayer, a script moved into a plugin), compare it with the one in Admin, Install Google Tag Manager. Put the original back before you debug anything else.
Is something blocking it?
Google’s help page lists five blockers. Here ad blockers and other extensions share one item. Check them in this order, cheapest first.
- Ad blockers and extensions. Google says ad blockers can stop the Google tag running and other extensions may block it. Test in a Chrome profile with only the Tag Assistant extension, and give that extension permission to read and change site data on your site (Google names this setting).
- The cookie banner. Google says consent management tools may block Google tags. If the banner holds back GTM itself until someone clicks Accept, Preview has nothing to connect to until you do. Click Accept, then Retry. That gets you testing. The lasting fix is to configure the banner to work with Google’s consent API (Consent Mode) instead of blocking the container script. If tags then load but behave oddly, the consent wiring is its own question: see Cookiebot and GTM Consent Mode v2.
- A firewall or proxy. A company network that filters Google domains will stop the container loading. Try once from another connection.
- The content security policy. A CSP is the site header that lists which domains may load scripts, styles and images. Google’s CSP guide lists the domains Preview needs:
script-src-elemforgoogletagmanager.comandtagmanager.google.com, plus entries instyle-src,img-srcandfont-src. It also says Tag Assistant shows the resources your policy blocked. The browser console says the same, in red. This is a developer change.
Does the debug parameter survive the redirect?
When it connects, Tag Assistant adds a debug parameter to the URL. Google’s help page names it _dbg, and says the parameter can interfere with page behaviour and that multiple browser redirects can stop the debug window loading. So:
- If the page redirects (to
www, to a country path, to a login), enter the final URL in Tag Assistant, not the one you typed. - If the page breaks or the parameter disappears, edit the domain in Tag Assistant and untick Include debug signal in the URL. Google’s Tag Manager help gives the same advice for Preview.
- If the container loads late, Google says to click Retry. In my work, late usually means a script that holds GTM back: a “delay JavaScript” option in a speed plugin, a script optimiser such as Cloudflare Rocket Loader, or code that waits for the first click or scroll. Scroll or click, then Retry. If it connects that way, exclude GTM from the delay.
Is the tag somewhere Tag Assistant can’t follow?
Some places are out of reach by design. Google documents each of these.
- Iframes. Google says iframe-loaded tag configurations can only be debugged with the Tag Assistant Chrome extension installed. Booking widgets and embedded forms often sit in one.
- Another domain. Google says the session stays active while you browse the same domain and the Google tag remains on the page. A checkout, booking or payment step on a different domain drops out. Connect to that domain separately.
- Shopify custom pixels. Shopify says Tag Assistant’s Troubleshoot tag feature isn’t compatible with custom pixels and doesn’t detect Google tags in them. Test with the Shopify Pixel Helper and the Network panel. The Shopify custom pixel note covers what the sandbox can and can’t see.
- AMP pages. Google says Tag Assistant doesn’t support them.
Server container Preview shows nothing?
A server container has its own Preview, and it lists the requests that reach your tagging server. Google’s server-side testing guide gives two checks when it stays empty: the web tag sends to the right server URL, and you browse the site in the same browser where the server Preview is open. Google says you only see requests from that browser. The full order of checks, from the server’s /healthy response to the preview server setting, is in server-side GTM errors: what Preview shows.
Connected, but the tag sits under Tags Not Fired?
Then the connection is fine. Click the event in the left panel where you expected the tag, open the tag and read which trigger condition failed. The usual reasons: the tag is on Page View or DOM Ready and the data arrives later, the push has no event key so no Custom Event trigger can match it, or the tag waits for a consent state the banner never set. The timing case is filed as F-103 , and the trigger fix is in GTM tag fires before the dataLayer is ready.
If instead the GA4 tag shows under Tags Fired but DebugView stays empty, the connection and the trigger are both fine. The cause is after the tag fires: GA4 DebugView is empty covers the debug flag, the measurement ID, the device selector, consent and ad blockers.
How do I fix it, in order?
- Open the Network tab on the page, filter for
gtm.js, reload. Note: no request, wrong ID, blocked, 404 or 200. - No request or wrong ID: add or correct the snippet on that template. 404: publish a version.
- Blocked: pause extensions, click Accept on the banner, try another network, then read the console for CSP errors.
- 200 but not connected: enter the final URL, untick the debug signal if the page breaks, interact with the page and click Retry.
- Connects, then drops: check whether the page moved to another domain or an iframe. Install the extension, or connect that domain on its own.
- Connected, tags not fired: that’s a trigger, not a connection. See the section above.
What to send the developer
If the cause is in the page code, one message is enough:
GTM Preview can’t connect on [URL]. In the Network tab, gtm.js for GTM-XXXX is [missing / blocked / 404 / loading late]. Can you [add the snippet to this template / allow the GTM Preview domains in the CSP / exclude GTM from the script delay]?
If nobody on your side reads Preview or the Network tab, send me the URL and the container ID. I’ll check what loads from outside and tell you what’s left to test on your side. That diagnosis is part of the work I do as a Google Tag Manager consultant.
Common questions
Why won’t GTM Preview connect to my site?
Tag Assistant opened the page but couldn’t find your container on it. Either the container snippet isn’t on that page (or a different GTM ID is), something blocked gtm.js (an ad blocker, a consent tool, a firewall or the site’s content security policy), or a redirect dropped the debug parameter. Open the Network tab, filter for gtm.js and check your container ID loads with status 200.
Preview says connected but no tags fire. Is that the same problem?
No. Connected means the container loaded. Tags listed under Tags Not Fired is a trigger question: the tag waited for a page-load trigger, a push without an event key, or a consent state that never came. Click the event in the left panel where you expected the tag and read its trigger conditions.
Does Tag Assistant work with ad blockers?
Not reliably. Google’s Tag Assistant help says ad blockers can stop the Google tag running and that other extensions may block it too. Pause them for the site you’re testing, or use a clean Chrome profile with only the Tag Assistant extension installed.
Can I preview tags inside an iframe?
Only with the Tag Assistant Chrome extension. Google’s help page says iframe-loaded tag configurations can only be debugged when the extension is also installed. Without it, the parent page connects and the iframe’s tags never appear.
Why does Preview disconnect when I go to checkout?
Google says the debug session stays active while you browse the same domain and the Google tag remains on the page. A checkout or booking step on another domain, or a page without the container, ends what Tag Assistant can see. Connect again on that domain, or test the step in the Network tab.
Who fixes GTM Preview when it won’t connect?
Usually a developer, because most causes sit in the page code: a missing snippet, a content security policy, a redirect, a script that delays GTM. Someone who reads Preview should name the cause first, so the developer gets one specific change rather than a hunt.
Sources
Read on 9 November 2026:
- Tag Assistant Help, troubleshoot with Tag Assistant (the
_dbgdebug parameter; confirm the tag is on the page and loads in developer tools; Retry if the tag loads after Tag Assistant tries to connect; multiple browser redirects can prevent the debug window loading; ad blockers, extensions, consent management tools, firewalls, proxies and CSP can block tags; extension permission to read and change site data; iframe-loaded tags need the Chrome extension; AMP not supported; session stays active on the same domain while the Google tag remains on the page) - Tag Manager Help, preview and debug containers (Preview opens Tag Assistant; untick Include debug signal in the URL if the site breaks; server containers have their own debug interface)
- Google for Developers, content security policy (directives Preview mode needs; Tag Assistant lists resources the policy blocks)
- Google for Developers, server-side tagging: testing your setup (empty server Preview: check the web tag’s server URL and use the same browser; only requests from that browser show) and preview and debug server containers
- Shopify Help Center, GTM in a custom pixel (Tag Assistant’s Troubleshoot tag feature isn’t compatible with custom pixels and doesn’t detect Google tags in them; test with Shopify Pixel Helper)