Cookiebot

What Stevin gets out of Cookiebot

Cookiebot does one thing well: it scans your site, finds the cookies and puts a banner over the top that looks tidy to the regulator. We use it for clients who need to be demonstrably compliant fast without standing up a whole privacy project. Where it pinches is the connection to your measurement. A banner that sits too strict or does not talk to Consent Mode quietly costs you conversion data, and you only notice that weeks later in a report that does not add up. Cookiebot handles the consent, but it does not watch whether your tracking still works afterward. That is where Stevin sits on top. Through the consent status and your tag data, Stevin flags when measurement drops out because of consent, so a broken setup surfaces before a whole month of data is unusable, with a person confirming the fix.

What you pair it with

Cookiebot covers the consent part, but it does not handle your measurement. Count on a tag manager alongside it and a correct Consent Mode v2 connection, otherwise your banner sits right but your data still leaks away. It does scan your cookies, but it says nothing about the quality of what still comes in after consent. In practice: configure Cookiebot and your tags as one whole, not as two separate projects, and test whether your core conversions survive the banner. The question that remains is not whether you are compliant, but whether you have enough reliable data left after consent to steer on.

Common mistakes

• →Setting the banner too strict without Consent Mode: you lose measurable conversions without noticing.
• →Installing Cookiebot separately from your tag manager, after which tags ignore consent.
• →Assuming a placed banner equals correct measurement.
• →Accepting a faulty scan, so cookies are missing from the banner.