Cookiebot: visitors click Deny, but tracking continues
Your Cookiebot banner records a rejection, yet GA4, Meta Pixel or other trackers keep running. How to test it, why it happens and how to fix it.
Lukas Kontur · · 7 min read
Cookiebot was the most common consent platform in our scan of 97,304 EU websites: we identified it on 6,481 sites, 14.8% of all detected banners (full study). It is a capable tool, but it can only hold back scripts it controls. When a visitor clicks Deny (or "Reject all", "Use necessary cookies only" or your banner's equivalent) and your analytics or ad pixels keep running, the cause is usually a script that bypasses Cookiebot. This guide shows how to find it and bring it under control.
The symptoms
- A scan report lists trackers still active after reject or cookies still present after reject, on a site with a Cookiebot banner.
- Cookiebot's own scan report looks clean, but your browser shows
_gaor_fbpafter clicking Deny. - After Deny, cookies disappear, but come back as soon as you open the next page.
This pattern is widespread. When we clicked Reject on EU websites, 48.3% of the 22,445 sites with a conclusive test still had non-essential cookies after the reject flow, and on 1,743 sites cookies came back after a reload (reject button study).
Corrected on 2026-10-21: this figure was re-measured from the stored scan results with stricter definitions (see the methodology). These numbers cover all consent tools, not Cookiebot in particular.
How to check it yourself
- Open a new private window in Chrome, press F12 and click Network.
- Load your site and click Deny (or your banner's equivalent).
- Clear the Network list with the "clear" icon, then reload the page.
- Filter for
collect(GA4),facebook,tiktok,hotjar,linkedinanddoubleclick, one at a time. Every request listed now happened after a rejection. - In Application, Cookies, check for
_ga,_fbp,_ttpand similar. Cookiebot's own cookie (CookieConsent) is expected; it stores the choice. - For each leaking request, open the Initiator tab. You will usually see one of three sources: a
<script>in your page HTML,googletagmanager.com/gtm.js, or a plugin file. - Check the page's own Response Headers for
Set-Cookieheaders that set tracking cookies. Those come from your server.
Why it happens
- The Cookiebot script is not first, or it loads async. For automatic blocking, Cookiebot must be the very first script on the page and must not be loaded with
async(Cookiebot: automatic cookie blocking); its scan report help also warns againstdefer(Cookiebot: understanding the scan report). The exception is a GTM setup, see step 3. Anything that loads earlier runs unchecked. - You use manual blocking and some scripts are not marked. Without automatic blocking, only scripts marked with
type="text/plain"anddata-cookieconsentwait for consent (Cookiebot: manual cookie blocking). - GTM fires tags without consent rules. Cookiebot's template sets Google Consent Mode, but a custom HTML tag (Meta, TikTok, Hotjar) ignores Consent Mode unless you give it a consent requirement.
- Cookies are set by the web server. Cookiebot's scan report shows these with the initiator "Webserver". They cannot be blocked in the browser (Cookiebot: understanding the scan report).
- A plugin or app adds its own tracking. On WordPress and WooCommerce, plugins such as pixel or analytics plugins often insert their scripts in ways your Cookiebot setup does not cover, especially with manual blocking. The Initiator tab shows the plugin folder name, which tells you where to look.
- Unclassified cookies. Cookiebot blocks by category. A cookie or script that is still "Unclassified" in your Cookiebot account is not blocked (Cookiebot: understanding the scan report).
The fix
Step 1: load Cookiebot correctly
If you paste the script yourself (without GTM), it must be the first script in <head>, without async, and with automatic blocking switched on if you want Cookiebot to catch unmarked scripts. Cookiebot's developer documentation shows the data-blockingmode="auto" attribute; your snippet from the Cookiebot account already contains your own ID:
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js"
data-cbid="YOUR-COOKIEBOT-ID" data-blockingmode="auto" type="text/javascript"></script>
Exclude this script from every caching, minify and "delay JavaScript" feature.
Step 2: mark scripts that must wait
For scripts in your HTML, the documented markup is:
<script type="text/plain" data-cookieconsent="statistics">
// analytics code
</script>
<script type="text/plain" data-cookieconsent="marketing">
// advertising pixel code
</script>
The valid categories are preferences, statistics and marketing. Strictly necessary scripts need no markup. For a YouTube or other embedded frame, the manual blocking article shows replacing src with data-cookieblock-src and adding data-cookieconsent="marketing" (same article as above; Cookiebot's older YouTube example uses data-src, so follow the variant that matches your Cookiebot setup).
Step 3: give every GTM tag a consent rule
If you use Google Tag Manager:
- Add the Cookiebot CMP template from the Community Template Gallery and fire it on the Consent Initialization - All Pages trigger. According to Cookiebot, the template sets the Consent Mode defaults to "denied" until consent (Cookiebot: GTM deployment). Keep the template up to date so that it also sets the v2 signals
ad_user_dataandad_personalization. Cookiebot's GTM guide also has you fire consent-dependent tags on a Custom Event trigger for the eventcookie_consent_updateinstead of All Pages, so they can fire as soon as the visitor accepts. - GA4 and Google Ads tags have Built-In Consent Checks. For every other tag (Meta, TikTok, Hotjar, LinkedIn), open the tag, Advanced Settings, Consent Settings, choose "Require additional consent for tag to fire" and add
ad_storage(ads) oranalytics_storage(analytics) (Google: consent in Tag Manager). - If you use automatic blocking together with GTM, Cookiebot recommends the order Consent Mode, then GTM, then Cookiebot, with
data-cookieconsent="ignore"on the consent and GTM snippets, and it advises against also running the Cookiebot CMP tag inside GTM in that setup. Choose one: the template in GTM, or automatic blocking with the script in the page (Cookiebot: GTM and automatic blocking).
The GTM Consent Mode v2 guide walks through these settings in detail.
Step 4: classify everything
Log in to your Cookiebot account, open the latest scan and give every "Unclassified" cookie a category. Cookiebot notes that a first scan can take up to 24 hours to analyse.
Step 5: deal with server-side cookies
If the scan report shows a cookie with the initiator "Webserver", or you found it in Response Headers, the fix is in your website code or plugin, not in Cookiebot. Find the plugin or server feature that sets it and make it read the visitor's choice. On WordPress, many plugins can read consent through the WP Consent API, which the Cookiebot plugin supports (WP Consent API).
Step 6: check your banner behaviour settings
Cookiebot's help centre describes how a "close on scroll" style setting can make a scanner's scrolling register as consent; it presents this as a scanner artefact (Cookiebot: scanner false positives). Our recommendation: make sure only a click on a button counts as a choice, so that real visitors who scroll are not treated as having agreed.
How to verify the fix
- Deny test: new private window, click Deny, clear the Network list, reload. No requests for
collect,facebook,tiktokorhotjar; no_ga,_fbpor_ttpcookies. Repeat on two more pages. - Respawn test: close the tab and open the site again in the same private window. The rejection should hold and cookies must not return.
- Accept test: new private window, click Allow all. Trackers and cookies appear.
- Consent Mode: in Tag Assistant, the Consent tab should show On-page Default "Denied" and, after Deny, no update to "Granted" (Google: troubleshoot consent mode).
- GTM preview: in Preview mode, open the Tags tab after a Deny. Meta, TikTok and similar tags should be shown as not fired (at the time of writing, the preview lists them under "Tags Not Fired").
Related: Pre-consent tracking explained.
Check your site in 1 minute
Our free scan clicks Deny on your Cookiebot banner, reloads the page and lists every tracker and cookie that survived the rejection. No signup needed. Run a free scan.
Get alerted when it breaks
A new tag in GTM or a plugin update can quietly bypass Cookiebot again. With monitoring, we repeat the reject test on a schedule and email you when tracking survives a rejection. Create an account and add your site.
Last updated: