Why you test GTM, not just install it
Google Tag Manager is a container: a small script that loads on your pages and then runs the tags you configure inside it — GA4, Google Ads, the Meta Pixel, and so on. Installing the container and configuring a working tag are two different things.
Plenty of sites have a container that loads perfectly and still send no data, because the tags inside were never published, are blocked by a trigger condition, or wait on a consent signal that never arrives. Others have the snippet on the homepage but not on the checkout or landing page that actually matters.
So 'I installed GTM' is not the same as 'my tracking works'. Testing is how you close that gap.
Method 1 — GTM Preview mode
Preview mode is the official way to see what your container does, tag by tag. In the GTM interface, click Preview, enter your site URL, and Tag Assistant opens a connected session of your site.
As you click around, it shows each event in order and, for every event, which tags fired and which did not — with the reason. It is the most complete view because it reads your actual container configuration, not just what loaded in the browser.
Method 2 — Check it in your browser devtools
You do not always need a tool. A browser can confirm the basics in under a minute:
- Open devtools → Network tab, reload the page, and filter for 'gtm.js'. A request to googletagmanager.com/gtm.js?id=GTM-XXXXXX means the container loaded — and shows which container ID.
- Open the Console and type dataLayer — you should see an array of events. If it is empty or undefined, GTM has nothing to work with.
- Type google_tag_manager in the Console; the object exists when a container is present.
- Confirm the container ID that loads matches the one you expect — a common mistake is an old or wrong GTM-ID left on the page.
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 checkMethod 3 — Google Tag Assistant
Tag Assistant, Google's free debugging extension, gives you the same tag-by-tag view outside the GTM editor. Connect your site, interact with it, and watch which tags fire, what data they send, and how Consent Mode affected them.
It is the right tool when you want to debug a specific page interactively, or when you do not have edit access to the container itself.
What 'working' actually means
A real pass is not just 'the container loaded'. Three things all have to be true, and each of the methods above checks a different layer:
- The container loads on the page (gtm.js request succeeds).
- The right tags fire — GA4, Ads, Pixel — for the right events.
- It happens on the pages that matter, not only the homepage you happened to test.
The catch: these are all one-time checks
Preview mode, devtools, and Tag Assistant all share the same limit: they tell you GTM works in the session you are watching, right now. They say nothing about next week.
Most GTM failures arrive after launch, silently — a redesign drops the snippet, a consent tool starts blocking it, a developer removes a script they did not recognise. Nobody is running Preview mode at the moment it breaks, so the data just quietly stops.
That is why a one-time 'it works' is worth confirming on a schedule, not just once.
The fastest check: a free GTM checker on a live URL
When you just want a quick answer for a specific page, you do not need to open the GTM editor at all. TrackCanary's free Google Tag Manager checker inspects a live URL and tells you whether a GTM container loads on it, in seconds.
Use it as your fast first pass — confirm the container is there on the exact page that matters — then use Preview mode or Tag Assistant when you need to debug the tags inside. And when tracking has to stay healthy over time, monitoring re-runs that check for you so a future change can't break it unnoticed.
Next step
Check if GTM is live on any URL — free
Run a free Google Tag Manager check on any live page to confirm the container loads, then keep it monitored so a future change can't break tracking silently.