Prompt
Why do my tags still load even after I set consent mode?
Latest observation
Because Consent Mode does not block tags by itself.
It mainly tells Google tags how to behave based on consent signals. If your tags are still loading, usually one of these is happening:
-
The tag is loaded before consent is checked
- For example, via hardcoded script tags, a CMS plugin, or a tag manager setup that fires immediately.
-
Consent Mode is only adjusting behavior, not preventing execution
- Google tags may still load, but they can operate in a restricted way until consent is granted.
-
You’re using the wrong consent defaults or update timing
- If you set consent after the tag has already fired, it won’t stop that initial load.
-
Other tags aren’t governed by Consent Mode
- Consent Mode is mainly for Google tags. Third-party tags need their own consent gating.
-
Tag Manager trigger rules are not set to require consent
- In Google Tag Manager, a tag can still fire unless you explicitly configure consent checks or blocking triggers.
What to check
- Make sure default consent states are set before any Google tags load.
- Verify that your CMP or consent banner sends consent updates early enough.
- In GTM, check:
- Consent Initialization trigger
- Tag-level consent settings
- Whether tags are set to require
ad_storage,analytics_storage, etc.
- Confirm you don’t have duplicate installations of the same tag outside GTM.
Key idea
Consent Mode changes how tags behave; it does not automatically stop them from appearing on the page.
If you want tags to not load at all, you need tag blocking / consent gating, not just Consent Mode.
If you want, I can help you troubleshoot your exact setup in Google Tag Manager, gtag.js, or a CMP.