Trackers and cookies before consent: how to make the banner actually block them
Best practices1 min readFixes 2 checks cookies-before-consent, trackers-before-consent
A consent banner only counts if analytics and ad tags wait for the click. Check in a fresh browser, then wire the tags to the consent platform or Consent Mode.
Step by step, with screenshots: A cookie banner that passes: reject button, lifetime, consent mode →
Check your own site
Runs these 2 checks and the other 185, free, in about 45 seconds.
What a passing site looks like
- Only necessary cookies are set before consentwarning · −2.5 ptseffort M
- No trackers load before consentwarning · −2.5 ptseffort M
2. Trackers before consent
Why it matters. Analytics, ad pixels and session-recording scripts that run before the visitor answers the cookie banner set identifiers without permission. Under GDPR and ePrivacy that needs prior consent; regulators fine for it, and the banner is worthless if the tags do not wait for it.
How to fix it.
- Load tracking tags through your consent platform (Cookiebot, OneTrust, Complianz, CookieYes, Google Tag Manager with consent triggers) so they run only after "Accept". Test in a fresh incognito window: no tracker request until you click.
- If you use Google tags, add Consent Mode v2 with the defaults set to denied; the tags then send cookieless pings until consent.