OneTrust
Enterprise privacy, consent, and governance suite with Cookie Consent and PreferenceChoice.
A CMP configures what should happen when visitors accept, reject, or send Global Privacy Control. It does not, by itself, prove that analytics, ads, and session replay actually stop at the network layer. This guide compares leading CMPs for enterprises and publishers, then scores each on the enforcement realities privacy teams see after deployment: GPC handling, TCF depth, regional hosting, and how much work still falls to tag order and server-side controls.
Quick summary
What it does
CMPs collect consent choices, show notices and preference centers, maintain vendor lists, and signal allowed purposes to tags and ad partners.
What to look for
Require IAB TCF alignment where you use ad tech, explicit GPC handling, strong audit logs, EU infrastructure options, and a plan to validate tags with network-layer testing after every change.
Where Lokker fits
Lokker works with any CMP you choose: Privacy Edge inventories what still fires on your pages, Consent Validator proves behavior in each consent state including GPC, and Guardian blocks disallowed requests when the CMP and tag manager drift out of sync.
The tools
Eight leading tools covering free, mid-market, and enterprise tiers, cloud and self-hosted deployment, and a range of privacy and compliance postures.
OneTrust
Enterprise privacy, consent, and governance suite with Cookie Consent and PreferenceChoice.
TrustArc
Consent Manager with NIST-aligned privacy program tooling and enterprise assessments.
Cookiebot by Usercentrics
Scanner-led CMP with automatic cookie classification and multilingual banners.
Usercentrics CMP
App and web CMP with App Consent, server-side options, and Google Consent Mode v2 kits.
Osano
Consent Platform with no-hassle pricing, monitoring, and vendor risk scoring.
Ketch
Orchestration-first consent and preference APIs with programmatic policy enforcement.
Sourcepoint
Publisher-focused CMP and messaging with paid and ad-supported experience patterns.
Didomi
EU-founded consent and preference stack with strong TCF and mobile SDK coverage.
All product names and trademarks are property of their respective owners. Lokker is not affiliated with or endorsed by any of the companies listed. Pricing and feature information is based on publicly available data and may change; verify with each vendor before purchasing.
Feature comparison
How each tool compares across the dimensions that matter most for product, engineering, and privacy teams.
Focus the matrix
Showing 5 of 8 tools. Add vendors as needed, or show the full table when you want every column.
3 tools are hidden from the focused table. The full text matrix below keeps every capability visible in the page source.
| Capability | |||||
|---|---|---|---|---|---|
| IAB TCF v2 support | TCF 2.2 certified CMP strings and vendor list support | TCF-certified options for publisher and advertiser stacks | TCF integration for publishers; consent mode helpers for Google stacks | TCF 2.2 certified CMP with in-app extensions | TCF support on eligible plans with publisher-focused configuration |
| Global Privacy Control handling | GPC recognition with regional rule templates | GPC tied to jurisdiction templates and opt-out propagation | GPC support with Google Consent Mode bridging | GPC handling in web and app CMP configurations | GPC support with documentation for CCPA-style opt-outs |
| Site scanning and cookie inventory | CookieConsent scanner with scheduled rescans and categorization | Automated scanning with governance dashboards | Monthly scans with auto-blocking until consent on many plans | Scanning plus Custom Implementation Service for complex stacks | Discovery scans with vendor risk cards |
| Google Consent Mode v2 alignment | Templates and docs for Consent Mode default and update signals | Integration guidance for GA4 and Ads with regional rules | Native Consent Mode integration and tag recipes | Certified Google CMP partner patterns for v2 | Consent Mode support with configuration guides |
| Preference center and granular purposes | PreferenceChoice with granular toggles and policy linkage | Preference centers with jurisdiction-based purpose sets | Per-category toggles with auto-generated policy sections | Granular purposes with app and web parity | Simplified preference UX with category bundles |
| DSAR and privacy rights workflow coupling | Native OneTrust Privacy Rights Automation integration | TrustArc privacy rights module integration paths | Focused on consent; DSAR via Usercentrics suite partners | Usercentrics Preference Manager and Automation paths | Osano Subject Rights Management add-on |
| Regional hosting and DPA posture | Multi-region hosting with EU and US deployment options | Regional options with enterprise DPA packages | EU operator with strong EU hosting story | EU parent with regional hosting choices | US operator; SCC-based transfers for EU customers |
| Tag manager and GTM integration depth | Templates for GTM, Adobe, and Tealium with consent mode variables | Professional services patterns for complex tag stacks | GTM community templates and auto-blocking helpers | GTM template gallery and server-side consent bridges | GTM guidance with script blocking patterns |
| CMP analytics and A/B testing of banners | Analytics on banner performance and geo splits | Reporting dashboards for consent rates | Banner analytics and consent rate reporting | A/B testing for banner variants on higher tiers | Consent analytics dashboards |
| Typical entry motion | Enterprise contracts with modular SKUs | Enterprise sales-led | SMB-friendly tiers with domain-based pricing | Tiered by consents and apps | Transparent SaaS tiers |
Does your tool actually stop in reject and GPC states?
Lokker Consent Validator runs automated browser sessions across every consent state and confirms at the network layer whether tools in this category still send requests when they should not.
Privacy and compliance
The dimensions Lokker Privacy Edge evaluates when it detects consent management platforms on your properties. Use this scorecard alongside the capability matrix when making your vendor decision.
| Privacy dimension | ||||||||
|---|---|---|---|---|---|---|---|---|
| Vendor proves tags stop without separate testing product | ||||||||
| IAB Europe CMP certification path for TCF | ||||||||
| Documented default GPC treatment for US states | ||||||||
| EU legal entity or strong EU hosting story | ||||||||
| Auto-blocking of uncategorized scripts option | ||||||||
| Administrative audit logs for CMP changes | ||||||||
| Native mobile app CMP SDK | ||||||||
| Published sub-processor list | ||||||||
| Support for in-app WebView consent continuity |
Scores reflect publicly available product documentation as of 2026. Vendor capabilities change; verify current behavior with each vendor and through independent testing. "Partial" indicates the capability exists but requires non-default configuration, an additional plan tier, or has meaningful limitations.
Buyer guidance
Choosing among these consent management platforms depends on your industry, infrastructure, privacy posture, and budget. Use these decision guides to narrow your evaluation.
Sourcepoint, Didomi, and enterprise OneTrust setups often pair with complex header bidding. TCF string accuracy and vendor list updates become weekly work.
Lokker note: After CMP go-live, schedule Consent Validator runs whenever you change Prebid or ad refresh logic.
OneTrust and TrustArc bundle assessments, RoPA, and DSAR with consent. Budget for cross-module ownership so the CMP configuration does not drift from the RoPA.
Lokker note: Use Privacy Edge to catch uncatalogued tags that never entered the CMP vendor list.
Usercentrics, Ketch, and Didomi emphasize APIs and app SDKs. Divergent taxonomies between web GTM and native SDKs create silent over-collection.
Lokker note: Validate both surfaces with the same consent-state test matrix.
Cookiebot, Osano, and mid tiers of Usercentrics keep operational load lower. You still need tag order discipline and periodic rescans.
Lokker note: Automate quarterly Consent Validator evidence exports for your risk committee.
Privacy context
CMPs are essential, but they are not autonomous enforcement engines. They emit signals that tags are supposed to respect. Any gap between the CMP UI, the tag manager container, and the actual network call creates liability. Plaintiffs and regulators increasingly ask what crossed the wire, not what the privacy dashboard claimed.
When GTM or Tealium loads before the CMP resolves, tags can execute in pre-consent states even though the CMP record shows correct categories.
New third-party scripts appear after every sprint. If rescans lag, vendors stay uncategorized and default allow rules may apply.
Publishing a GPC response in the CMP is not the same as proving that every ad pixel stopped firing for that session.
Where Lokker fits
Lokker does not replace your CMP. OneTrust, TrustArc, Cookiebot, Usercentrics, Osano, Ketch, Sourcepoint, and Didomi remain the system of record for consent choices. Lokker proves that your tags honor those choices.
Privacy Edge scans pages and surfaces third-party requests that never made it into the CMP vendor list, including tag-manager aliases.
See Privacy EdgeConsent Validator runs scripted sessions for each CMP state and stores network-level proof for legal and insurance workflows.
See Consent ValidatorGuardian blocks disallowed hosts at the browser edge so a stale container cannot override the CMP decision.
See GuardianCommon questions
The most common questions from privacy teams, legal counsel, and buyers evaluating consent management platforms.
More comparison guides
Next step
Lokker confirms that the tool you choose stops collecting data in reject and GPC states, surfaces any gaps in your CMP configuration, and enforces blocking at the network layer so a misconfigured consent banner cannot result in an unauthorized data collection event.