GTM Preview Mode Not Working? Fix Connection and Firing Issues

Google Tag Manager's Preview mode is the main way to test tags before they go live. When it works, you can see every event, every tag and every variable value. When it does not, you are left guessing, which is exactly what Preview is supposed to prevent.

Preview problems fall into two groups. Either Tag Assistant cannot connect to your site at all, or it connects but your tags do not behave the way you expect. This guide covers both, starting with the most common causes.

How Preview mode works

When you click Preview at the top right of your workspace, Tag Assistant opens and asks for your site URL. When you click Connect, your site opens and loads the current draft of that workspace instead of the published container. Google's preview and debug documentation describes this as browsing the site as if the current container draft were deployed.

Two details explain many problems later:

• Preview only affects the browser you started it in. Regular visitors still get the published version.
• Preview shows the workspace or version you previewed. A change saved in a different workspace is not included.

Google recommends installing the Tag Assistant Chrome extension. With it, the debug window opens in a new tab, tags inside iframes can be detected, and pop-ups or new tabs opened from your site stay in the same debug session.

Part 1: Tag Assistant will not connect

1. The container is not on the page, or it is a different container

Tag Assistant can only connect if the page loads the container you are previewing. View the page source and search for GTM-. Compare the ID with the one at the top of your GTM workspace.

Mismatches are common when a site has a staging container and a production container, when an agency set up its own container, or when you test a page template that never got the snippet, such as a landing page builder or checkout. Google's Tag Assistant troubleshooting page lists "the URL you entered might not have the Google tag on the page" as the first cause to check.

2. An ad blocker or browser extension blocks GTM

Many ad blockers and privacy extensions block googletagmanager.com. If GTM never loads, Tag Assistant has nothing to connect to. Disable blockers for the site, or test in a clean Chrome profile with only the Tag Assistant extension installed. Also check that the extension has permission to read and change site data on the domain you are testing.

Privacy-focused browsers and strict tracking protection settings can block the same requests or limit the storage the debug session relies on. If Preview works in a standard Chrome profile but not in your usual browser, the browser's protections are the cause.

3. Your consent banner blocks GTM

Some consent tools hold back Google tags, or the whole container, until the visitor accepts. Google lists consent management tools as a possible cause of connection failures. Accept the banner in the preview window and click Retry in Tag Assistant if needed.

4. The script loads after Tag Assistant tries to connect

If the container loads late, for example after a delay script, a lazy loader, or a consent check, Tag Assistant may give up before GTM is ready. Clicking Retry usually solves this.

5. The debug parameter or redirects break the page

By default Tag Assistant adds a debug parameter to the URL. Some sites strip unknown parameters, redirect on them, or break. Google notes that multiple browser redirects can also prevent the debug window from loading. When you connect, untick Include debug signal in the URL and try again. Also enter the final URL your site lands on, including https and www if your site uses them, to avoid unnecessary redirects.

6. A Content Security Policy blocks the Google tag

If your site sends a strict Content Security Policy header, the browser may refuse to load GTM or the scripts it injects. Open the browser console and look for CSP violation messages mentioning googletagmanager.com. Our guide to Content Security Policy blocking pixels explains how to read and fix these errors.

7. The page type is not supported

Tag Assistant does not support AMP pages. Tags loaded inside an iframe can only be debugged with the Tag Assistant Chrome extension installed. The debug interface is also not available for mobile app containers.

Part 2: Preview connects, but tags do not fire

1. You are looking at the wrong container

If the page loads more than one GTM container, or GTM plus a standalone Google tag, Tag Assistant shows each one. Make sure you have selected the container you are working on at the top of the Tag Assistant window. Otherwise you will be inspecting someone else's tags.

2. You previewed the wrong workspace

Each workspace has its own draft. If a colleague made the change in another workspace, or you edited in one tab and clicked Preview in another, the tag you expect may not exist in this preview. Click Preview again from the workspace that contains your change.

3. It works in Preview but not on the live site

This almost always means the change was never published. Preview uses your draft; visitors get the published version. Click Submit, publish the version, and test again outside Preview. If you use GTM environments, make sure you published to the environment whose snippet is on the live site.

4. A trigger condition does not match

This is the most common reason a tag stays silent. To find the exact condition:

1. In the left panel of Tag Assistant, click the event where the tag should have fired, such as a click, a form submission, or a custom event.
2. In the Tags view, find your tag under Tags Not Fired and click it.
3. Look at the firing triggers. Each filter condition shows whether it passed or failed.
4. Open the Variables view for the same event and compare the actual value of the variable with the value your trigger expects.

Typical mismatches:

• Wrong event. The trigger listens on Page View, but the data you need is only pushed to the data layer later, in a custom event.
• Exact match on a changing value. A URL condition uses "equals" while real URLs include query strings or trailing slashes.
• Case differences. A custom event trigger set to Purchase will not match a data layer event named purchase.
• Built-in variables are off. Click and form variables such as Click ID, Click Classes and Form ID must be enabled under Variables > Configure before triggers can use them.
• A blocking trigger or exception on the tag overrides its firing trigger.

5. The tag is paused, limited, or blocked by consent

Check the tag itself. A paused tag never fires. A firing option of "Once per page" stops it on repeat events. In the tag's advanced settings, consent checks can block a tag when the required consent has not been granted. Accept your banner and see whether the tag moves to Tags Fired. Our Consent Mode v2 guide shows how to read the Consent tab.

6. The tag fired, but nothing arrived in the platform

Tags Fired only means GTM ran the tag. It does not prove the platform accepted the data. Click the tag to check the values it sent, such as the measurement ID or conversion label, and confirm the matching request in your browser's Network tab. For GA4, continue with our guide to GA4 events not showing.

How to verify the fix

1. Start Preview from the correct workspace and connect to the final URL of the page you are testing.
2. Perform the action once, such as a click or form submission.
3. In Tag Assistant, confirm the tag appears under Tags Fired on the right event, and only once.
4. Publish the container.
5. Close Preview by clicking the X in the debug interface or Stop debugging, open the live site in a normal window, and repeat the action while watching the Network tab.

The Pixel Helper extension is also useful for a final live check, since it shows which tags and events fire on the published page without any debug session.

FAQ

Why does Tag Assistant say "Could not connect"?

Usually the container is missing from the page, blocked by an ad blocker or consent tool, or loaded too late. Check the page source for your GTM- ID, disable blockers, accept the banner, and click Retry.

Do visitors see my Preview changes?

No. Preview applies only to the browser you started it in, or to people you share a preview link with. Everyone else gets the published container until you publish.

Why do I see two containers in Tag Assistant?

Your site loads two GTM containers, or a container and a separate Google tag. That can be intentional, but it is also a common cause of duplicate tracking. Our guide to duplicate gtag.js and GTM tags explains how to check.

Can I preview an older version of my container?

Yes. In GTM, go to Versions, open the version's More Actions menu, and choose Preview. This is useful for checking whether a problem started with a specific publish.