What “no tags found” in Tag Assistant actually means
Google Tag Assistant reports on what it can see in the page it connected to, at the moment it checked. “No tags found,” or a missing GTM, GA4, or Google Ads tag, means it did not detect that visible tag signal on that page, in that session.
That is a useful signal, but it is a snapshot of one page in one moment — not proof that your tags are gone everywhere.
It can mean any of the following:
- the tag or GTM container was removed from this page or template
- a cookie-consent banner is delaying the tags until the visitor accepts
- the tag fires only on a specific event, click, or thank-you page, not on page load
- Tag Assistant connected to a page, stage, or preview environment the tag was never added to
- a single-page-app route change did not re-load the tag
- an ad blocker or privacy extension in the browser blocked the script
Common reasons Tag Assistant does not detect your tags
For most sites, the cause is ordinary site work rather than someone intentionally touching tracking. A theme update, a plugin change, a redesign, or a new landing page built outside the usual template can all drop the GTM snippet or a tag from a page while the site keeps looking completely normal.
This is exactly why the problem is easy to miss: nothing on the page looks broken. The site loads, checkout works, and only the tracking quietly stops — usually noticed weeks later when campaign results drift.
Consent is the other frequent culprit. If your cookie banner blocks marketing and analytics tags until the visitor accepts, Tag Assistant will not see them on that first view. Accept the banner and check again before concluding a tag is missing.
Free tracking check
See what’s visible on a real site.
Run a free browser-based scan — no login, no install, ~10 seconds.
Run a free checkHow to check without Tag Assistant
You do not need Tag Assistant to know whether your tags are visible on your public pages. You can check the same browser-side signals from outside.
Open the page in an incognito window and view the page source, then search for the tag you expect: “googletagmanager.com/gtm.js” or a “GTM-” container ID for Google Tag Manager, “gtag(” or a “G-” ID for GA4, and “googleadservices.com” or an “AW-” ID for Google Ads. If the one you expect is missing, that tag does not seem to load on that page. Repeat on a few templates (home, product, cart, thank-you) — a tag that shows on one page and not another is only partially installed.
If you would rather not read source code, TrackCanary’s free checkers run this visible check for you across your public pages and show where each tag appears and where it drops.
A visible tag is not proof conversions are recorded
Even when Tag Assistant (or an external check) finds a tag, that only confirms the tag is visible on the page. It does not prove that a specific event or conversion — a GA4 event, a Google Ads conversion — actually fires on the real action, or that it was recorded in the account.
A GTM container can load perfectly while an important tag inside it is unpublished, paused, or tied to the wrong trigger; a conversion tag can be present while the conversion action was never wired to the real event. To confirm the events themselves, use GTM Preview mode, GA4 DebugView, or Google Ads reporting with Tag Assistant in connected mode. A single failed request is not proof of a permanent break; it may be temporary.
Next step
Start with the free Google Tag Manager Checker
Paste your storefront URL and see whether GTM, GA4, and your Google Ads tag appear to load across your public pages — free, no login, no extension. Use the result to decide whether you need a developer handoff or ongoing monitoring.