Skip to main content

Which consent managers support which features?

Pick the features that you cannot do without. The list keeps only the consent managers whose documentation covers all of them.

8 of 10 have no framework SDK. They install through a script tag, which works in any framework.

Must have

First-party SDK for

Skip feature matrix
Features of all 10 cookie consent managers. The groups are standards, compliance, developer tools, pricing and frameworks. CMPs are in alphabetical order. Statuses come from vendor documentation.
Featurec15tCookie ControlCookieYesDidomiEnzuzoiubendaKetchOneTrustOsanoUsercentrics
Standards
IAB TCF
IAB GPPUnknownUnknownUnknown
Google Consent Mode v2
Google-certified CMP
Global Privacy Control
Compliance
Geo-targeted banners
Script blocking
Consent records
Cookie scanning
Developer
Open source
Self-hostableUnknown
Headless UIUnknownUnknown
TypeScript typesUnknownUnknownUnknownUnknownUnknown
Pricing
Free tier
Frameworks
Script tag
React
Next.js
Vue
Nuxt
Svelte
SvelteKit
Astro
TanStack Start

Standards

IAB GPP7 of 10
c15t, Didomi, iubenda, Ketch, OneTrust, Osano and Usercentrics
Unknown: Cookie Control, CookieYes and Enzuzo
Sources and notes

Compliance

Developer

Open source1 of 10
c15t
Partial: Ketch and Osano
Not supported: Cookie Control, CookieYes, Didomi, Enzuzo, iubenda, OneTrust and Usercentrics
Sources and notes
Self-hostable1 of 10
c15t
Partial: Didomi and OneTrust
Not supported: Cookie Control, Enzuzo, iubenda, Ketch, Osano and Usercentrics
Unknown: CookieYes
Sources and notes
Headless UI5 of 10
c15t, Didomi, Enzuzo, Ketch and Usercentrics
Partial: Cookie Control, iubenda and OneTrust
Unknown: CookieYes and Osano
Sources and notes
TypeScript types3 of 10
c15t, Ketch and Usercentrics
Partial: Didomi and Osano
Unknown: Cookie Control, CookieYes, Enzuzo, iubenda and OneTrust
Sources and notes

Pricing

Free tier8 of 10
c15t, Cookie Control, CookieYes, Enzuzo, iubenda, Ketch, Osano and Usercentrics
Not supported: Didomi and OneTrust
Sources and notes

Frameworks

Where does this feature data come from?

Each status comes from the vendor’s public documentation, with the page that we read. In the matrix, hover or tap a mark, or press Enter on it, to open that page. On a phone, open “Sources and notes” under a feature. “Per vendor docs” means that the vendor says it works. We did not test it.

We use “Verified by test” only for features that a CookieBench run tested. It covers the setup that we tested, not every configuration. It is not a legal certification. How we check features

Vendors change their products often. If a status is wrong or out of date, report a correction with a link to the source. We will fix it.

What the marks mean

  • Verified by test
  • Per vendor docs
  • Partial
  • Not supported
  • Unknown

Partial also covers a feature that only some of a CMP’s SDKs have. Filter to those frameworks and it shows as full. In the frameworks rows, a full mark means a first-party SDK and a partial mark means the script tag only. Each mark links to the CMP’s CookieBench page. We compare each framework with its own app without a consent manager. How we handle frameworks