Is your cookie banner blocking Google Analytics?
Your cookie banner is meant to control Google Analytics, allowing it when a visitor consents and holding it back when they do not. But a lot of banners get this wrong in one of two directions, and both cost you. Here is how to tell which is happening and how to fix it.
The two ways it goes wrong
- Over-blocking: GA4 is blocked for everyone who has not clicked Accept, with no Consent Mode to recover the gap, so a big slice of visitors are never counted.
- Under-blocking: GA4 fires for everyone regardless of choice, so the banner is decorative and you are not actually compliant.
The right behaviour sits between the two: honour the choice, but keep measuring what you legitimately can through Consent Mode.
How to tell what yours is doing
A few quick signs. If your GA4 traffic dropped sharply the day the banner appeared, you are probably over-blocking. If declining the banner makes no difference to whether tags fire (you can check in your browser’s developer tools or a tag assistant), you are under-blocking. If you are not sure, that uncertainty is itself the problem worth resolving.
Find out what your banner does to GA4
We’ll scan your live site and show whether GA4 is blocked, firing regardless, or correctly controlled. Free, 10 seconds.
Check my tracking freeWhy it is easy to get wrong
The consent platform (the banner tool) and Google Tag Manager have to be deliberately connected so the consent state actually reaches the GA4 tag. Many setups install the banner and the tags separately and never link them, so the banner looks right but controls nothing, or blocks everything. It is a wiring job, not a visual one.
The fix
Connect your consent platform to GTM, set Google’s Consent Mode (Advanced is usually best), and test both paths: accept and decline. Done right, GA4 measures consenting visitors fully and still models the rest, so you are compliant and your numbers are trustworthy again.
Get your banner and GA4 working together
We wire your consent platform to GTM and set Consent Mode so GA4 behaves correctly on both accept and decline. The audit comes off any build.
See how it works & pricingRelated guides
Why analytics dropped after a banner How consent breaks tracking Consent Mode v2 explained All guidesDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Ads, Meta and server-side tracking. See pricing · All guides · Back to datahound.agency
Banner and Google Analytics: common questions
How do I know if my cookie banner is blocking Google Analytics?
Check whether GA4 traffic dropped when the banner launched (a sign of over-blocking), and whether declining the banner actually stops the tag firing using browser dev tools or a tag assistant (if not, it is under-blocking). Either is a fault to fix.
Should my cookie banner block Google Analytics?
It should hold GA4 back until a visitor consents, then allow it, while using Consent Mode to recover modelled data from those who decline. Blocking everyone with no Consent Mode loses data; firing for everyone is not compliant.
Why does my banner not stop the tags?
Usually the consent platform and Google Tag Manager were never connected, so the consent choice never reaches the tags. The banner shows but does not control anything until they are wired together.