hello@datascale.de+49 89 921 35 623tracked cookie-free · /openDEEN

Search services, integrations and blog posts.

DatascaleResourcesChecksCookie banner / CMP

Check · C01 · Consent Mode V2

Cookie banner / CMP

A cookie banner is the visible half of the consent flow, no CMP means no documented opt-in.

What we check

Detects 11 common cookie banners: OneTrust, Usercentrics, Cookiebot, Didomi, and more.

Why it matters

A cookie banner is the visible half of the consent flow, no CMP means no documented opt-in.

Common causes

  • There simply is no CMP, and the tracking has run without a consent layer for years.
  • The CMP only loads on the homepage; campaign landing pages or a separate shop run without a banner.
  • A self-built banner without a CMP backend: visible yes, but with no audit trail and no tag-blocking behind it.
  • After a relaunch the CMP script no longer loads from an old template, and nobody notices because the banner cookie still sits in their own browser.
  • The CMP is loaded through the tag manager and thereby loses exactly the window in which it should block tags.

The fix

Integrate a CMP (Usercentrics, Cookiebot, consentmanager) and enable tag-blocking. The CMP script belongs directly in the HTML before all tracking snippets, not in the tag manager. For Usercentrics setups: how the chain continues into the server container is covered in Usercentrics + Server-Side GTM; we run the platform as a certified partner.

Matching template

Consent Mode Audit Checklist

Seven layers, each with a check, a failure signal and an owner. Covers this finding and the six around it.

Get the checklist →

Check it yourself first

The Tracking Check tests this point along with all the others, in seconds.

Start the Tracking Check →
What does a failing "Cookie banner / CMP" check mean?

A cookie banner is the visible half of the consent flow, no CMP means no documented opt-in. Integrate a CMP (Usercentrics, Cookiebot, consentmanager) and enable tag-blocking.

How do you fix a failing "Cookie banner / CMP" check?

Integrate a CMP (Usercentrics, Cookiebot, consentmanager) and enable tag-blocking.

The fix, delivered

Wired up in days, not sprints.

Findings from the Tracking Check go into a ranked sequence with effort estimates in the Audit Sprint, every module with an acceptance criterion.