ConsentCheck

Check if Your GTM Tags Are Working

GTM “installed” doesn't mean your tags fire — and that's how conversion tracking breaks silently.

This tool checks for GTM container signals (loader, container IDs, dataLayer hints, and overlapping setups) so you can quickly see if your base instrumentation looks healthy.

What this checks:

  • GTM loader script present
  • GTM container IDs (including multiple containers)
  • dataLayer hint
  • gtag() hint (possible overlap/conflict)

Get the exact issue (not just “GTM installed”).

If GTM is present but conversions still don't show in Ads, something else is blocking attribution (consent timing, click IDs, firing conditions).

Also confirm firing: test conversion tracking.

Why GTM tags are not firing

GTM tags usually fail because triggers don't match the real page events, consent blocks execution, preview mode isn't configured, or multiple containers / overlapping setups create conflicting rules.

Google Tag Manager not working — common causes

  • GTM container isn't actually loaded (script blocked, wrong environment, missing snippet)
  • Consent defaults run after tags (tags fire “denied” or never fire)
  • Triggers rely on events that never happen on the real conversion path
  • Multiple containers installed (conflicts, duplicated tags)
  • CSP/ad blockers block `googletagmanager.com`

If you're debugging firing, this guide helps: GTM tags not firing (debug steps).

How to verify GTM tags are firing correctly

  1. Use GTM Preview mode and confirm the conversion tag fires on the conversion event
  2. Verify Consent Mode defaults and updates happen before/after user actions
  3. Confirm network requests (Google Ads / GA4 hits) actually fire
  4. If Ads still shows 0 conversions, run a full scan to find missing signals

FAQ

Why are my GTM tags not firing?

Usually: wrong trigger conditions, consent blocking, a blocked GTM script, or the conversion event never occurs.

GTM is detected — does that mean my conversion tag works?

No. GTM presence only confirms the container is present/likely loaded. You still need to verify tag firing on the conversion path.

What should I do next if conversions still show 0?

Use the tracking issue scanner and then get exact fix steps in the full Consent Mode v2 check.