Google Tag Manager Preview Mode Not Connecting: Causes and Fixes
Quick fix
Google tag manager preview mode not connecting usually means Tag Assistant can't see the tag on the page or something is blocking it. Check the URL you entered has your Google tag, uncheck Include debug signal in the URL if the page breaks, and click Retry if the tag loads late. Disable ad blockers and browser extensions.
- Check the URL you entered carries the Google tag.
- Uncheck the debug signal option if the page breaks.
- Disable ad blockers and browser extensions.
- Allow Google tags through consent tools, then retry.
Can't fix it yourself? Send me the details
What this error means
Preview mode connects your container draft to your live site through Tag Assistant so you can see which tags fire. If Tag Assistant can't find the tag, the page blocks it, or the setup is unsupported, it won't connect.
Why it happens
1The page has no tag or it loads late
Tag Assistant needs the tag on the page when it connects.
How to tell if this is you: The page you entered has no tag, or Retry later works.
2The debug signal breaks the page
The extra URL parameter can break some pages.
How to tell if this is you: The page errors when connecting.
3Blockers, extensions or consent tools
These can stop the tag or the connection.
How to tell if this is you: It works in a clean browser.
4AMP, iframes or redirects
These setups can prevent debugging.
How to tell if this is you: The page is AMP, loads the tag in an iframe, or redirects repeatedly.
How to fix it
Connect to the right page
For: The page has no tag or it loads late, The debug signal breaks the page
- Launch Preview from the Workspace tab and enter a URL that carries the tag.
- Uncheck the debug signal option if the page breaks.
- Click Retry if the tag loads after the connection attempt.
Remove blockers
For: Blockers, extensions or consent tools
- Disable ad blockers on the test pages.
- Disable browser extensions and retry.
- Allow Google tags through your consent tool.
Handle special setups
For: AMP, iframes or redirects
- Install the Tag Assistant extension for iframe-loaded tags.
- AMP pages are not supported by Tag Assistant.
How long it takes
Google doesn't publish a timeline for this.
How to stop it happening again
- Test on a page that is known to carry the tag first.
- Keep a clean browser profile for debugging.
- Remember the debug view only shows in the same browser, or for shared users.
From my desk
My first suspect is a blocker. An ad blocker, a browser extension, or a consent tool can stop the tag from loading, so I try a clean browser profile. After that I confirm the URL I entered really has the tag, and I untick the debug signal if the page breaks with the extra parameter.
Muhammed Abdul Kalam
When to get help
- You've worked through the checks and the status still isn't changing.
- The account has many campaigns and ad groups and you cannot tell which change caused the problem.
- Results are suffering during a launch or sale and every day costs real money.
Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.
Send me the detailsFAQs
How do I start preview mode?
Click Preview in the Workspace tab to launch Tag Assistant.
How do I know it connected?
The site opens and shows Connected in the bottom right.
What if the debug parameter breaks my page?
Uncheck Include debug signal in the URL.
Does it work on AMP pages?
No. Tag Assistant does not support AMP pages yet.
Can ad blockers stop it?
Yes. Ad blockers may prevent the Google tag from running.