Answers
1 answer
That usually means Preview connected to your browser session, but it can’t see a runnable GTM container or Google tag on the exact page that opened. First, check the final URL after redirects and inspect the rendered page/source for the correct `GTM-XXXX` snippet and a `gtm.js` request. It’s easy to have the container in a template that isn’t live on that route, use the wrong container ID, or load it only inside an iframe.
If the snippet is there, retry with ad/privacy extensions and any VPN filtering disabled, then test after accepting your consent banner. Google also calls out CSP, firewall/proxy rules, late script loading, redirects, and iframe setups as things that can stop Tag Assistant from detecting the tag. Once the container appears in Preview, then look at individual tags and triggers; “no tags found” is usually an installation/loading problem, not a trigger problem.
Your answer
Sign in to answer.
Keep exploring