Evaluating a consent management platform (CMP) comes down to ten criteria, and most of them are about what happens after the banner. Does consent reach every system that uses the data? Does the platform honor browser signals like Global Privacy Control? Can it prove, months later, exactly what a customer agreed to?
Almost every CMP on a shortlist can show you a compliant cookie banner. Where they differ is everything behind it: identity, propagation, evidence and the signals regulators now check for. That’s where this checklist spends its time.
Each criterion below includes the questions to put to vendors. If you’re turning them into a formal process, our guide to writing an RFP for a consent management platform covers the rest.
The checklist at a glance
| What to evaluate | The question to ask | A good answer includes |
|---|---|---|
| Law coverage | Which laws do you support, and how do you apply different rules by jurisdiction? | Opt-in and opt-out models run side by side from one configuration |
| GPC and opt-out signals | How do you detect and apply Global Privacy Control? | The signal applied before tags fire, logged, and shown to the visitor |
| Granular capture and preferences | Can we define our own purposes, data categories and preferences? | Custom purposes, contextual prompts, and preferences in the same record as consent |
| Identity, cross-domain and cross-device consent | What happens to consent when two customer profiles merge? | A clear rule for merges, and consent tied to a person, not only a cookie |
| Real-time propagation | How fast does a withdrawal reach our CRM, CDP and ad platforms? | Seconds, by API or connector, with retries if a system is down |
| Integrations and APIs | Which of our systems do you connect to out of the box? | Prebuilt connectors, a documented REST API and bulk import of existing records |
| Audit records | Can you show what one person saw and chose on a given date? | Append-only event history linked to policy versions, exportable on request |
| Google Consent Mode v2 and IAB TCF v2.3 | Are you Google-certified, and do you support TCF v2.3 and Consent Mode v2? | On Google’s certified CMP list, with Consent Mode signals you can inspect |
| Tracker discovery | How do you find cookies and tags we don’t know about? | Scheduled scanning, including logged-in pages and different regions, with alerts |
| Data storage and security | Where is consent data stored, and what independent audits do you hold? | Named hosting regions and subprocessors, current audit reports, role-based access |
Coverage of the laws you operate under
Start with your footprint. A retailer selling across US states runs a different consent model from a bank operating under GDPR in Europe and PIPEDA in Canada, and plenty of enterprises have to run both at once. These regulations have varying requirements for consent, data deletion, user rights, and cross-border transfers.
Complying with diverse regulations across multiple jurisdictions can be resource-intensive, requiring significant legal and operational effort.
The practical test is whether one configuration can apply different rules by jurisdiction: opt-in where GDPR applies, opt-out with signal handling in the US states that require it, and stricter defaults for sensitive data. If every region needs its own setup, every law change becomes a project.
Ask vendors: Which regulations do you support out of the box? How do you work out which rules apply to a visitor? How quickly do you ship changes when a law is amended?
Global Privacy Control and universal opt-out signals
Global Privacy Control (GPC) is a browser setting that tells every site a visitor lands on that they don’t want their personal information sold or shared. Twelve US states now require businesses to recognize opt-out preference signals like it: California, Colorado, Connecticut, Delaware, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon and Texas.
Regulators are checking. California’s Attorney General settled with Sephora for $1.2 million in 2022, partly for failing to process opt-outs sent through GPC. On September 9, 2025, the California Privacy Protection Agency and the attorneys general of California, Colorado and Connecticut announced a joint sweep of businesses that don’t honor these signals. And since January 1, 2026, California’s regulations require a business to display whether it has processed the signal.
A CMP should read the signal when the visitor arrives, apply it before advertising and analytics tags fire, record that it did, and show the visitor the result. Then check where the opt-out goes next. If the signal only changes a cookie, your CRM may still treat a known customer as opted in.
Ask vendors: Do you detect GPC by default? Is the opt-out logged as a consent event? Does it reach the customer’s profile when we know who they are?
Granular, contextual consent and preference capture
Data collection requirements for businesses vary widely. For e-commerce businesses, it could be personalizing product recommendations or analyzing purchasing behavior; for healthcare, it could be diagnosing and treating patients, tracking health outcomes, or conducting research.
Three capabilities matter most here: granular consent options, custom data categories, and consent requests that adjust to context.
Granular options let people agree to some uses of their data and not others. When they can see exactly what they’re agreeing to, the consent you collect is clearer and easier to defend.
For example, for financial services, tailoring consent choices could be allowing users to choose whether they would like to share sensitive data like income or investment preferences for personalized financial advice; for healthcare, it could be segmenting consent options for sharing medical history, wearable devices, or participating in research studies for personalized care plans.
Custom data categories let you define purposes and data types that match how your business works, rather than a generic template. Collecting data you have no stated purpose for adds risk without adding value.
Laws like GDPR, the CCPA and HIPAA set different rules for how certain categories of data can be used and shared, so the platform should let you set purposes and defaults by category, including for sensitive data.
Contextual, or just-in-time, consent reduces consent fatigue. Instead of asking for everything at once, the platform asks at the moment a specific type of data is needed.
For example, asking users to provide consent for location-based recommendations when a user searches local stores makes a good case for contextually adjusting consent based on user behavior.
Look past yes and no, too. Customers increasingly want to choose channels, topics and frequency, so check whether the CMP manages preferences in the same record as consent, and whether people can change them from a preference center or a link in an email.
Ask vendors: Can we define our own purposes and data categories? Can consent requests trigger in context? Are preferences and consent stored together?
Consent that follows the person across domains and devices
A banner records a choice for one browser on one domain. Your customers use several of each. If someone opts out on your main site and then visits a sister brand or opens your app, the platform should already know.
There are three capabilities to check. Cross-domain consent applies one choice across your domains and brands. Cross-device consent links it to a profile so it follows the person between devices. And identity consent ties it to a verified customer rather than a cookie, including people with more than one persona, like a home and a work account.
Then ask the question vendors answer least consistently: what happens to consent when two customer profiles merge? If the answer is vague, that’s where records get lost.
Real-time propagation to downstream systems
Consent only protects you if the systems that use the data act on it. When a customer withdraws consent, your email platform, CRM, CDP and ad audiences need to know within seconds, not at the next nightly export.
Ask vendors: How does a change reach each downstream system, by API, webhook, connector or file? How long does it take? What happens if a system is offline when the change is made, and how would we know?
Integrations, APIs and bulk import
Judge integrations by the ones you need, not the total count. Check for prebuilt connectors to your CRM, CDP, marketing and analytics tools, a documented REST API for anything custom, and a way to bulk-load the consent records you already hold, so you don’t start from zero on go-live.
If a connector only works in one direction, ask how a preference changed in that system, such as an unsubscribe in your email tool, finds its way back.
Immutable audit records and exportable evidence
When a regulator or a customer asks what someone agreed to, you need the answer for a specific moment: what the person saw, which policy version was live, what they chose, and when it changed. That history should be immutable, meaning new events are added and nothing is edited or deleted, and you should be able to export it in a form you can hand to an auditor.
Ask vendors: Is every capture, update and withdrawal stored as its own event? Is each record linked to the banner and policy version the person saw? How quickly can we export the evidence for one person, or for everyone?
Google Consent Mode v2, IAB TCF v2.3 and Google certification
If you serve ads through Google AdSense, Ad Manager or AdMob, Google requires a Google-certified CMP integrated with the IAB’s Transparency and Consent Framework (TCF) when serving personalized ads to users in the EEA and the UK, a rule in place since January 16, 2024, and in Switzerland since July 31, 2024. The framework has moved on as well: Google required publishers and CMPs to move to TCF v2.3 by February 28, 2026.
Advertisers have a separate requirement. To keep using Google’s measurement, ad personalization and remarketing features for users in the EEA, you have to collect consent and send it to Google, which on a website means implementing Google Consent Mode v2. If your US sites or apps get European traffic, both apply to you.
Ask vendors: Are you on Google’s list of certified CMPs? Do you support TCF v2.3? Is Consent Mode v2 preconfigured, and can we see the signals your platform sends?
Tracker discovery and monitoring
You can’t ask for consent for trackers you don’t know about. Check how the platform finds cookies, SDKs and tags across your websites and apps, whether it can scan pages behind a login and from different regions, and whether it alerts you when a new tracker appears after a release.
Data storage, security and access control
Understanding where data is stored proves helpful in assessing the potential security risks associated with that location. GDPR doesn’t require data to stay in the EU, but it restricts transfers outside the EEA unless the destination has an adequacy decision or the transfer is covered by safeguards such as standard contractual clauses. If you’re a US business with European customers, ask where consent data is hosted, which subprocessors handle it, and how transfers are covered.
CMP vendors should undergo regular independent security audits of their data centers and conduct regular penetration testing to identify and address potential vulnerabilities in their systems. Ask for their current audit reports and a summary of their most recent penetration test.
Access controls and data encryption serve as the foundational pillars safeguarding the sensitive personal data of users. Ideally, companies should give priority to platforms that offer granular access controls for administrators to define roles, permissions, and access levels that match their organizational structure.
Check that consent data is encrypted both at rest and in transit, using a current standard such as AES-256 for stored data.
Turn the checklist into an RFP
Not every criterion carries the same weight for every business. A publisher with European traffic will put Google certification near the top; a retailer with several brands will care most about cross-domain consent and propagation. Weight the ten criteria for your situation, then put the questions above to every vendor in the same form so the answers can be compared.
Our guides to writing an RFP for a consent management platform and choosing a CMP through an RFP walk through the process, and CMP vs CDP covers where consent management ends and customer data platforms begin.
How Syrenis measures up
Syrenis is a specialist consent management platform for enterprises where consent has to reach every system, not just the website that collected it. Against this checklist, it supports IAB TCF and Global Privacy Control, matches consent to identities and personas, carries it across domains and devices, propagates changes to downstream systems in real time, and keeps immutable records of every capture, update and withdrawal. It connects to 350+ integrations, it’s on Google’s list of certified CMPs (TCF CMP ID 200), and it comes preconfigured for Google Consent Mode v2.
Book a demo and we’ll walk through the checklist against your own stack.