Prompt
Consent banner not blocking analytics
Latest observation
Oct 9, 2026
OpenAI APIWeb search: off
If your consent banner isn’t blocking analytics, the usual issue is that the analytics tag is loading before consent is granted, or the consent state isn’t being passed correctly to the tag manager / analytics script.
Quick checklist
-
Ensure analytics scripts are not hardcoded in
<head>- Remove direct GA/GTM/Meta/etc. tags from the page if you’re using a consent tool.
-
Verify the banner sets consent before tags fire
- Your CMP should update consent state first, then allow analytics to load.
-
Use tag manager consent controls
- If you use GTM, make sure:
- Consent Mode is enabled
- Analytics tags require
analytics_storage - Tags are set to wait for consent if needed
- If you use GTM, make sure:
-
Check for default-denied behavior
- Before user acceptance, analytics storage should be denied by default.
-
Test in a clean browser session
- Use an incognito window, clear cookies, and inspect network requests for analytics calls before consent.
Common causes
- Analytics script embedded directly in the site template
- CMP loaded after analytics
- Consent accepted visually, but not written to cookie/localStorage
- GTM tags not configured to honor consent
- Multiple consent tools conflicting
What to inspect
- Browser devtools → Network: look for requests to GA/gtag/GTM before consent
- Console: check for consent-related errors
- Source code: confirm analytics is loaded conditionally
If you want, I can help you debug it step by step if you share:
- your CMP name
- whether you use GTM or direct analytics
- a snippet of your banner/analytics setup