Check if Google Tag Manager (GTM) is visible on your website

Google Tag Manager has a deceptively simple health signal: the container snippet is on the page, so a scan sees GTM, and it feels like tracking is handled. But GTM loading and the tags inside GTM actually firing are two different things. The container is just a delivery system — an empty one loads exactly like a full one. A page can carry GTM perfectly while the pixel, the GA4 event, and the conversion tag inside it never trigger on the actions that matter.

Tags fail to fire for reasons that leave no visible trace. A workspace change was previewed but never published, so the live container is stale. A trigger still points at a button, form, or URL that a redesign renamed. A consent banner blocks the container until the visitor accepts. Or the dataLayer event a trigger listens for was renamed by a developer and nothing matches anymore. The container keeps loading, the page looks normal, and the tags quietly stay dormant — while campaigns run on the assumption that everything inside GTM is working.

The free check works at the visible layer: it looks for whether a GTM signal appears present on the public page and flags the lead paths that usually depend on it for review. It does not open the container or prove any tag fires — it tells you GTM appears to be there and where the triggers worth reviewing live.

GTM sits between your site and every tool it feeds. The container loads once, then tags fire based on triggers — a form submit, a click, a page view — reading values from the dataLayer to decide what to send and where. That indirection is what makes GTM powerful and also what makes it fragile: every tag depends on a trigger matching and a dataLayer value being present, and any link in that chain can break without the container itself looking any different.

The common failure is silent and structural. The container is published and loads fine, but a specific tag has a broken or unpublished trigger, so it never fires on the real action. From the outside — and from a simple presence check — GTM looks healthy the whole time. A loaded container is not the same as a firing tag, and that gap is exactly what lets a tracking setup look intact while the events campaigns rely on quietly go missing.

The free check works at the visible layer: it looks for whether GTM appears present and which lead actions are visible on the public page, then flags them for review. It does not access the container, read triggers or variables, or prove a tag fires — those need GTM Preview or Tag Assistant with account access. Naming that limit honestly is the point: the scan tells you where to look inside GTM, not that the container is fine.

The usual way to verify GTM is from inside the account: open the container, enter Preview mode, and click through the site watching each tag fire in the debug pane — or run Tag Assistant on one page at a time. That is the right tool for confirming exactly what a container does, but it needs login access to the client's GTM and checks a single page per session from the machine you are on.

TrackCanary takes the opposite approach for the first look. Paste a public URL — no login, no install, no account access — and the check reviews whether GTM appears present alongside the forms, calls, WhatsApp, and other lead paths that usually run through it, all in one pass. It is the fast preflight you can run on any page, including a client's, before more budget goes through it — a way to see whether the container even appears to be on the page before anyone opens Preview mode.

It does not replace GTM Preview or Tag Assistant — those still confirm which tags fire and what they send. TrackCanary is the step before that: a quick, honest read of what appears visible from the public page, and a way to keep watching it so a container that stops loading after a change does not go unnoticed.