Why Consent Mode isn't working after you set it up
You added Consent Mode, ticked the box in your banner, and assumed it was done. But Consent Mode fails quietly: nothing errors, the data just stays wrong. Here is where it usually breaks.
The common failures
- Default state set after the tags load, so the first hit ignores consent entirely. Timing is everything.
- Banner not actually updating consent: it looks right but never calls the consent update, so tags stay stuck.
- Advanced vs basic mode confusion, changing whether tags fire cookieless or not at all.
- Tags not consent-aware, firing regardless of the signal. Related to consent breaking tracking.
How to verify it
Use GTM Preview or the Tag Assistant consent view to watch the consent state change when you accept and reject, and confirm tags respond correctly in each case. If the state never updates on reject, your banner is not wired to Consent Mode. Getting this exactly right is fiddly and high-stakes, both for data and compliance, which is why it is a core part of an audit.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Google Consent Mode v2