Most Consent Mode implementations are either non-compliant or throw away usable data. Done properly - Basic or Advanced, with correct timing - you get both GDPR compliance and behavioural modelling that keeps GA4 useful.
Why It Matters
We find at least one of these on almost every EU-facing site we audit.
The Consent Signal
Correct timing at every hop is what prevents both a GDPR violation and _gl URL pollution in GA4.
Default consent state applied.
Banner shown before any tag fires.
Granted, denied, or default.
Correct timing - no race condition.
Compliant, and still measurable.
The Difference
What We Do
Basic blocks all tags until consent; Advanced sends anonymised, cookieless pings before consent for behavioural modelling. We help you choose the right mode for your market.
Our Process
Full review of current CMP configuration, tag firing behavior, and consent state handling across your container.
Consent Mode v2 built at the tag level with correct timing, avoiding race conditions and the checkbox trap.
Every consent state combination tested and confirmed compliant before sign-off.
Run a free, live check and see whether Consent Mode is really in place on your site - not just installed, but working.
Check My Site →FAQ
