You declined your own Cookiebot banner in a private window, and the Network tab still shows a marketing script loading. That result almost always traces back to how the page is set up, not to Cookiebot itself, and the cause is easier to find if you check things in the right order.
Start with the blocking mode
Cookiebot's support documentation is plain about the mechanism: the platform doesn't block cookies, it stops the HTML elements that set them (mostly scripts, iframes and images) from loading. It does that in one of two ways. Automatic blocking is switched on with data-blockingmode="auto" on the Cookiebot script, and Cookiebot's developer reference says leaving the attribute off behaves the same as "none". Without it, you are in manual mode, where every tag needs markup like this:
<script type="text/plain" data-cookieconsent="marketing" src="..."></script>View source on the page that misbehaves and find the Cookiebot tag. Which mode you're in decides which list below applies.
If you use automatic blocking
- Has a scan finished? Cookiebot says auto-blocking only has instructions once at least one scan of the domain has completed.
- Is Cookiebot the very first script? Its documentation asks for exactly that placement, because anything that loads earlier has already run.
- Search for
data-cookieconsent="ignore". The attribute exempts an element from auto-blocking, and Cookiebot warns that any element carrying it can set tracking without the visitor's consent. Someone may have added it months ago to rescue a broken widget. - Look for unclassified cookies. An element that sets only cookies Cookiebot hasn't classified yet isn't blocked, so a tag added after the last scan can load until you categorize it.
- Check where Cookiebot loads from. For auto-blocking, Cookiebot's guidance is that Google Tag Manager must not be the thing executing the Cookiebot script.
If you mark up scripts by hand
Here the usual culprit is a tag nobody marked up: a script still typed text/javascript, or an iframe that kept src when Cookiebot's guide calls for data-cookieblock-src. Scripts your own code injects at runtime need the JavaScript SDK instead of markup. And inside Tag Manager, Cookiebot tells you to replace the All Pages trigger with its cookie_consent_update event on every tag that tracks behavior; a tag left on All Pages fires on load.
What website owners should do
Decline the banner in a private window, then watch the Network tab on the homepage and one deeper page such as checkout. Fix whatever third-party advertising request shows up, publish, and run the same test again after the next tag release, since one new pixel can undo a clean result. Under the CCPA a consumer's opt-out of sale or sharing is something the business has to act on, so what the page sends counts for more than what the dashboard reports.
Where Privisy fits
Privisy loads your live pages the way a visitor would, sends a real Global Privacy Control signal, and records what fires. It gives you an outside opinion on your Cookiebot setup without touching it; it complements the platform and doesn't replace it. The Cookiebot comparison page shows how the two fit together, and our earlier post covers the gaps any client-side CMP leaves.
Get an outside check on your setup
Privisy audits the live site's trackers, opt-out link and GPC response from the outside, whichever consent platform you run.
Get a full audit