GTM Preview Mode Not Working? Every Fix in One Place.

GTM's preview mode is your lifeline for debugging tags. When it doesn't work, you're flying blind. The debug panel spins forever, shows "Connecting...", or opens a blank tab. Sometimes it loads but shows zero tags firing. Let's fix all of these.

Problem 1: "Connecting..." Spinner That Never Resolves

Cause: Browser extensions are blocking the debug connection between your site and Tag Assistant. Ad blockers, privacy tools, and VPN extensions treat the GTM debug script (loaded from tagassistant.google.com) the same way they treat ad network scripts, and silently drop the requests. You'll never see an error — just an infinite spinner.

Fix: The fastest approach is to open Chrome in Incognito mode, which disables extensions by default, then retry preview. If that works, the culprit is an extension. Common offenders: uBlock Origin, AdBlock Plus, Privacy Badger, Ghostery, DuckDuckGo Privacy Essentials, and most VPN browser extensions. Either disable them site-wide or whitelist tagassistant.google.com and tagmanager.google.com specifically.

Problem 2: Preview Opens But Shows Zero Tags Firing

Cause: The URL you typed into the preview prompt doesn't match the site where the GTM snippet is actually installed, OR your tag triggers are scoped to a different hostname than the one you're testing on. This is the most common "it's connected but nothing is happening" scenario. You'll see the debug bar and the green "Connected!" message, but the Tags tab is empty.

Fix: When you click Preview, make sure the URL field is the exact URL — including protocol (https://), trailing slash, and the correct www/non-www variant. Then check tag trigger conditions: if a trigger requires Page Hostname equals www.example.com and you're testing example.com, nothing will fire. Either adjust the trigger or test on the matching domain.

Problem 3: Blank Page After Clicking Preview

Cause: Your browser's pop-up blocker is stopping the Tag Assistant debug window from opening. Chrome blocks pop-ups by default, and since GTM preview opens a new window to tagassistant.google.com, that window is categorized as a pop-up. Corporate DNS filtering, zero-trust network policies, and some employee-monitoring tools also silently block the Tag Assistant domain.

Fix: Look for the blocked pop-up icon on the right side of the Chrome address bar — it usually appears immediately after clicking Preview. Click it and choose "Always allow pop-ups from tagmanager.google.com." If you're on a corporate network, ask IT to whitelist both tagmanager.google.com and tagassistant.google.com. The debug panel moved to the Tag Assistant domain in 2020, so older allow-lists that only cover tagmanager.google.com won't work anymore.

Problem 4: "Connected!" But Tag Assistant Shows the Wrong Container

Cause: The page has multiple GTM containers installed, or a cached debug session from an earlier attempt is hijacking your current preview. We see this mostly on sites that integrate third-party marketing tools (HubSpot, Intercom, consent managers) — those tools often inject their own GTM container alongside yours, and Tag Assistant grabs the first one it finds.

Fix: Check the container ID shown in the top-left of the debug panel. If it isn't your container (starts with GTM-XXXXXXX), end the current preview via the button in GTM, clear cookies for tagassistant.google.com, close all Chrome windows, then restart preview. If the third-party container is the problem, ask the vendor whether their script loads GTM and either coordinate with them or move your tags to a server-side container to eliminate the conflict.

Problem 5: Preview Works in Chrome But Not Safari/Firefox/Edge

Cause: GTM preview is officially supported only in Google Chrome. While it often works in other Chromium browsers (Edge, Brave, Arc), Google does not guarantee compatibility and the debug features lag behind. Safari and Firefox reliably fail because Tag Assistant relies on Chrome-specific extension APIs and cookie behavior that aren't available in non-Chromium engines.

Fix: Use the latest stable Chrome for debugging, then test cross-browser behavior separately once you've confirmed tags fire correctly. If you need to debug a browser-specific tag issue (e.g., a tag that only fires in Safari), install the Tag Assistant Companion extension and use it with manual inspection rather than relying on preview mode.

Problem 6: Tags Fire in Preview But Not on the Live Site

Cause: The container version you're debugging has never been published. Preview mode reads from your workspace (the draft), not the live container. This catches everyone at least once — you test, confirm tags fire correctly, walk away, and then realize a week later that nothing has been tracked in production because you never hit Submit.

Fix: Compare the "Workspace" version number (top bar of GTM) to the "Published" version shown on the Versions tab. If the workspace is higher, you have unpublished changes. Click Submit, give the version a name describing what changed, then click Publish. Verify within 5-10 minutes by checking the live site in a fresh browser — the debug bar should be absent, and tag requests should show up in the Network tab.

Problem 7: Content Security Policy (CSP) Blocking Debug Script

Cause: Your site's CSP headers block the Tag Assistant debug script from loading. This happens on sites with strict security policies — especially banking, healthcare, and enterprise SaaS — where the CSP allows the main GTM domain but not the separate Tag Assistant domain. The browser console will show a CSP violation error mentioning tagassistant.google.com.

Fix: Open DevTools → Console and look for errors containing "Refused to load" or "violates the following Content Security Policy directive." Add *.google.com and *.googletagmanager.com to your site's script-src, connect-src, and frame-src CSP directives. Only do this in a staging environment or temporarily in production — you don't want to ship a permanently loosened CSP for the sake of debugging. Revert the change once the tag issue is resolved.

The Nuclear Option: Complete Preview Reset

When none of the specific fixes work, a full reset clears out every piece of cached state that could be interfering. This resolves the 5-10% of preview issues that fall outside the seven problems above — usually caused by some combination of stale cookies, session storage, and browser extension state that no single fix above addresses. It takes about two minutes and has no side effects beyond logging you out of GTM.

1. Click End Preview in your GTM workspace.
2. Clear all cookies and cache in Chrome (Settings → Privacy and security → Clear browsing data, last hour is usually enough).
3. Close every Chrome window completely.
4. Open a fresh Incognito window (extensions are off by default).
5. Log back into GTM and click Preview.
6. Enter your site URL manually with the correct protocol and subdomain.