How to Check if Google Tag Manager Is Working
Updated
Verify four separate things: the correct container loads, the reviewed version is published, the intended action fires the right tag, and the destination receives the event. Seeing a GTM ID in page source proves installation, but it does not prove that a conversion is being measured.
A complete GTM check follows one action from the production page to the receiving analytics or advertising account.
A developer says GTM is installed. A marketer sees a tag marked as fired. GA4 still has no useful conversion data. Those statements can all describe the same implementation because they refer to different parts of the measurement chain. Use this verification sequence before launch or after a website release. Start with one production URL, one expected container and one test action, then record evidence at each stage. If the container is completely missing, the linked detection guide gives you a narrower troubleshooting path.
What to check
1. Define what a successful test should produce
Write down the production URL, the expected GTM container ID, the destination measurement ID and one action to verify. For a lead form, success might mean one accepted test submission produces one generate_lead event in the intended GA4 property. A button click and a successful submission are different actions. Agree on the business definition before inspecting tags.
2. Check the container on the actual destination
Follow the campaign URL through its redirects. In the browser Network panel, look for the container request, commonly gtm.js?id=GTM-XXXX, and compare its ID with your installation record. A snippet in the HTML can exist even when the script is blocked. Record whether the request loads and any browser error; a successful response is evidence of loading, not proof of downstream measurement.
3. Verify the published version and environment
In GTM, review Versions and identify the configuration published to the environment used by production. A saved version and an unpublished workspace are not the same as a live release. Compare the version with the changes you intend to test. Sites that use environment snippets need the matching environment checked as well. Keep the version number with the test evidence.
4. Use Tag Assistant to follow the action
Connect Tag Assistant to the exact URL. Perform the test action once and inspect the event timeline, variables and tags associated with that action. For a form, confirm that the application reports success before the conversion tag runs. If a tag fires on both a click and a success callback, investigate the two triggers before treating the implementation as verified.
5. Confirm delivery to the intended destination
Check the tag destination and inspect the outgoing event. For GA4, use an authorised DebugView session to look for the expected event name and relevant parameters in the correct property. For another platform, use its own test-event diagnostics. A GTM fired label describes the tag execution; destination evidence answers whether the receiving system observed your test.
6. Repeat under the expected consent conditions
Record the initial consent state and repeat a permitted test after the relevant choice. Consent configuration can change tag execution and what diagnostics reveal. Do not remove consent requirements to make a test pass. Also distinguish a browser extension blocking a request from a site deployment fault, and document which browser conditions you used.
7. Retest the published site outside the workspace preview
After publishing a reviewed change, close the workspace preview and repeat the action on the ordinary production URL. Check loading and delivery again. Include the important funnel variants, such as the mobile landing page, another language and a return visit. Save the action, event name, destination, consent state, timestamp and published version together.
8. Use AdVault to establish the URL and tag baseline
Run the campaign URL through the GTM Checker to inspect the destination and supported visible signals. Use that evidence to select the page to debug. AdVault cannot replace access to your receiving account or establish that every interaction works from an initial page scan. Mark any untested conversion action as unverified rather than assuming it passed.
What you see and what it usually means
The container loads, but no action tag fires
Inspect the event and trigger conditions. Installation has been observed; the action still needs verification.
Preview works, but the published site behaves differently
Compare the live version, environment and test conditions using the dedicated Preview versus Live guide.
The tag fires, but the destination has no test event
Check the destination ID, outgoing delivery and diagnostic conditions before changing the business trigger.
A typical case
Illustrative example: a newsletter form emits form_success only after the server accepts a test subscription. Tag Assistant shows one matching GA4 tag, and the intended property receives one generate_lead event. The same tag does not fire when the form returns a validation error. That verifies the tested success path under the recorded consent state. It does not establish that every form, device or integration on the site works.
Before you call it fixed
- Expected container and destination IDs recorded
- Production container request checked
- Published version and environment confirmed
- One business action tested
- Trigger tied to the intended event
- Receiving destination checked
- Consent and browser conditions documented
- Ordinary production URL retested
Check the production URL
A correct configuration on paper can still fail after redirects, deployment or consent logic. Use the exact URL your campaign will send traffic to.
Check a campaign URLVerify the signal directly
Related troubleshooting guides
Common questions
Is seeing GTM in the page source enough?
It establishes that the snippet is present. Verify that the container loads, the intended trigger runs and the receiving destination observes the expected event.
Does GTM Preview prove the live site works?
Preview helps inspect the workspace. Production uses its published configuration, so complete a separate check after the reviewed version is released.
Can I check GTM without access to the account?
You can inspect public loading signals and use a URL checker. Verifying container configuration and destination receipt requires the appropriate account access.
Technical references
Scan the full campaign route.
See where the click lands, what survives the redirect chain and which supported tracking signals are visible on the final page.