Why your visitors' consent choice isn't being remembered
The banner pops up on every visit, sometimes every page, no matter how many times someone clicks accept. That is not just irritating: it means consent is not being stored, which breaks both the experience and your compliance.
Why it is not sticking
- The consent cookie is blocked or cleared, often by Safari's short cookie lifetimes or privacy settings.
- The banner writes consent to the wrong scope, so it does not persist across pages or subdomains.
- A caching or CDN layer serves the pre-consent version of the page.
- Two consent tools fighting each other.
Why it matters beyond annoyance
If consent is not stored, you cannot prove it was given (a compliance problem), and your tags may keep re-prompting or mis-firing. Fix the cookie scope and lifetime so a choice persists for a sensible period, and make sure only one consent tool is running. A banner that cannot remember a yes is doing neither its legal nor its practical job.
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 · How to prove you collected consent