GTM Preview “No Tags Found / No Debuggable Google Tags”: How to Fix It.

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.

The "No Tags Found" Error

"No Tags Found. There Are Currently No Debuggable Google Tags at the Address You Provided"

Cause: This specific message means Tag Assistant reached the URL you entered but found no gtm.js (or gtag.js) request on that page at all — it isn't a trigger problem or an extension problem, GTM simply isn't running at that exact address. Four common reasons: the URL redirects before the page finishes loading (a www/non-www redirect, an http→https redirect, or a locale redirect can strip the debug parameter mid-flight, so the page that finally loads was never the one you were previewing); you're testing a staging or password-protected URL where the GTM snippet was never deployed; the container snippet is gated behind a consent-management or cookie-banner script that only injects GTM after a visitor interacts with the banner, so a fresh page load has nothing to detect yet; or the URL has a typo, a trailing space, or the wrong protocol.

Fix: Open the URL you're testing in a plain browser tab first — no preview — and confirm it loads with no redirect showing in the address bar. Then check the page source or the Network tab for a request to gtm.js containing your container ID. If it isn't there on a plain load, preview mode was never going to find it either. If your snippet is gated behind a consent banner, accept the banner before starting preview, or temporarily let the container itself load unconditionally while you test (keep tag-level consent gating in place — just don't gate the container load).

Connection Problems

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 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 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 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.

Tags Not Firing Correctly

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 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 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.

GTM Preview Mode and Shopify

Shopify stores hit "No tags found" for two platform-specific reasons that don't apply to a typical site.

Checkout and Order Status Pages

Shopify's hosted checkout runs in a separate, sandboxed environment where you can't add a raw GTM container script the way you can on your storefront theme. If you're pointing preview mode at a checkout or order-status URL and getting "No tags found," that's often not a bug — GTM was never permitted to run there in the first place. Shopify's supported path for checkout-page tracking is its Web Pixels API (Settings → Customer events → Add a custom pixel) or the official Google & YouTube sales channel app, not a hand-rolled GTM container.

Storefront Pages: Check Your App Embeds

If GTM is installed via a theme app embed — common on Online Store 2.0 themes — the embed block can be silently switched off, especially after a theme change or update. Go to Online Store → Themes → Customize → App embeds and confirm the GTM (or GA4) embed is on. If it's off, gtm.js never loads on any storefront page, and every preview session will show "No tags found" — not just on the one page you happened to test.

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 problems above — usually caused by some combination of stale cookies, session storage, and browser extension state that no single fix 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.

Frequently Asked Questions

Why is GTM Preview Mode not working?

GTM Preview Mode most commonly fails for one of three reasons: a browser extension (ad blocker, VPN, or privacy tool) is blocking the connection to tagassistant.google.com; a browser pop-up blocker is preventing the Tag Assistant debug window from opening; or a Content Security Policy on the site is blocking the debug script. The fastest diagnostic is to open Chrome in Incognito mode and retry — Incognito disables extensions by default, which rules out the most common cause in under a minute.

Why does GTM Preview show no tags fired?

When GTM Preview shows a successful connection but zero tags firing, the most common cause is a URL or hostname mismatch. Check that the URL you entered in the preview prompt exactly matches where your GTM snippet is installed, including protocol (https), the correct www vs non-www variant, and any subdomain. Then check your tag trigger conditions — if a trigger is scoped to a specific Page Hostname and you're testing on a different hostname, none of the tags using that trigger will appear in the Tags tab.

How do I fix GTM Preview Mode not connecting?

To fix a GTM Preview Mode connection failure: first try Incognito mode to rule out browser extension interference. If that connects, identify the offending extension (uBlock Origin, Privacy Badger, and DuckDuckGo Privacy Essentials are the most frequent culprits) and whitelist tagassistant.google.com. If Incognito also fails, check for a pop-up blocker icon in the Chrome address bar and allow pop-ups from tagmanager.google.com. If you're on a corporate network, contact IT to whitelist both tagmanager.google.com and tagassistant.google.com. If none of these work, run the complete preview reset procedure.

Does GTM Preview Mode work on password-protected sites?

GTM Preview Mode can work on password-protected sites, but you need to handle authentication before starting the preview session. Log in to the protected site first in a regular Chrome tab, then start the GTM preview and enter the URL. If the site uses HTTP Basic Authentication, include the credentials in the URL or authenticate in the browser before initiating preview. The main issue is that Tag Assistant opens the site in a new window without carrying your session cookies — log in first, or the preview may land on the login page rather than the page you're trying to debug.

Why do some tags not appear in GTM Preview?

Tags that don't appear in GTM Preview are either: (a) not yet published — preview shows workspace drafts but if you're looking at a published container version in preview, unpublished tags won't appear; (b) blocked from firing by exception triggers — a tag may be set to fire on All Pages but also have an exception trigger that matches your test page; or (c) controlled by a Trigger Group where not all component triggers have fired yet. Check the "Not Fired" tab in the debug panel — it shows tags that were evaluated but whose trigger conditions weren't met, along with the specific condition that failed.

Can I use GTM Preview Mode on mobile devices?

GTM Preview Mode cannot run directly on a mobile device — it requires Chrome on desktop with the Tag Assistant session initiated from GTM. To debug mobile-specific behavior, use Chrome's built-in device emulation (DevTools → Toggle Device Toolbar) which simulates mobile viewport and user agent within the desktop browser. For testing actual mobile hardware, you can use Chrome Remote Debugging: connect your Android device via USB, enable USB debugging, then open Chrome DevTools on desktop and inspect the mobile browser's open tabs. iOS testing still requires desktop Chrome emulation or a dedicated analytics tool.

What is the difference between GTM Preview Mode and Tag Assistant?

GTM Preview Mode and Tag Assistant are the same tool under different names at different points in history. The original Tag Assistant was a Chrome extension that had separate functionality. Since 2020, Google folded GTM's debug functionality into Tag Assistant (now at tagassistant.google.com), and "Preview Mode" in GTM is what launches that tool. When you click Preview in your GTM workspace, it initiates a Tag Assistant session connected to your specific container. There is no meaningful functional difference between "GTM Preview Mode" and "Tag Assistant" for GTM debugging today.

Why does GTM Preview show different tags than the live site?

GTM Preview Mode shows the tags in your current workspace (draft), not the published container version running on the live site. If you've added or modified tags since the last publish, preview shows those changes — but the live site is still running the last published version. This is the intended behavior: preview exists so you can verify changes before publishing. If preview shows tags firing that don't appear in production, the most likely explanation is that those changes have not been published yet. Click Submit → Publish to push workspace changes to the live container.

Why does GTM Preview say "No tags found"?

"No tags found. There are currently no debuggable Google tags at the address you provided" means Tag Assistant loaded the URL you entered but never saw a gtm.js request fire on that page — GTM simply isn't running there, at that exact address, on that exact load. The most common causes are a redirect that strips the debug parameter before the final page loads (http→https, www/non-www, or a locale redirect), a staging or password-protected URL that never got the GTM snippet deployed, or a snippet that's gated behind a consent banner so a fresh page load has nothing to detect. Load the URL in a plain tab first and check the Network tab for a gtm.js request before troubleshooting further — if it's not there on a plain load, preview was never going to find it.

Does GTM Preview Mode work on Shopify?

On storefront pages, yes, the same way it works on any site — as long as the GTM snippet is actually loading, which is worth confirming directly if you installed it via a theme app embed (Online Store → Themes → Customize → App embeds), since that toggle can get switched off without anyone noticing. On Shopify's hosted checkout, generally no: checkout runs in a separate, sandboxed environment that doesn't accept a raw GTM container script, so "No tags found" on a checkout URL is frequently expected rather than a bug. Track checkout events through Shopify's Web Pixels API or the official Google & YouTube channel app instead of trying to debug GTM there.