Evaluation Rubric
Feature checklists are somewhat useless when it comes to evaluating a CMP because there is a lot of parity between them. To really evaluate which one is the best fit for your organization, you have to look under the hood to understand how leveraging those features will translate into your processes and structure.
Need help evaluating?
A free tag compliance audit will give you a perspective on your current state. One of our privacy experts will walk you through your results.
Consent signal control and tag integration
Weight 25%What we look at
How the platform exposes consent state, how early that state is available on page load, and how reliably your tag management system can gate tags against it. Some CMPs refresh the page after a consent selection. This often causes significant issues in data collection and attribution, giving marketing teams headaches.
Strong looks like
Multiple signal methods (data layer, JavaScript object, callback, Consent Mode parameters, cookie storage); signal resolution before tags evaluate their firing conditions, and documented patterns for server-side tagging.
Limited looks like
A single signal mechanism, sole reliance on automatic blocking in place of tag configuration, or signal timing that leaves a race condition on some share of page loads.
Ask the vendor: Show me how consent states are exposed, and tell me when it resolves relative to tag evaluation on a cold page load.
Ease of implementation
Weight 20%What we look at
Total effort to reach a working, correctly configured deployment, including the tag layer work the platform does not do for you.
Strong looks like
Live and correctly gated within days, with clear documentation and no engineering dependency for routine changes.
Limited looks like
Multi-month deployments, engineering sponsorship required for the initial build, or a configuration surface complex enough that no internal resources fully understand it.
Ask the vendor: Walk me through a deployment for a company our size.
Support model and expertise
Weight 15%What we look at
Whether the vendor helps you define and enforce a policy, or just hands you documentation.
Strong looks like
Named support, help defining tag and cookie policy, and remediation guidance when monitoring surfaces a problem.
Limited looks like
Documentation plus email support only.
Ask the vendor: When a tag fires before consent six months from now, who catches it and who fixes it?
Regulatory coverage
Weight 15%What we look at
Breadth across GDPR, US state regimes, universal opt-out signals, IAB TCF where relevant, and speed of adapting to new requirements. Support for Google Consent Mode is becoming table-stakes to operate in Europe — ensuring the Consent Mode object updates correctly is a requirement under the Digital Markets Act.
Strong looks like
Granular geographic rule targeting, reliable GPC handling, current TCF certification, and a track record of shipping ahead of regulatory deadlines.
Limited looks like
One global rule set applied everywhere, or GPC support that stops at reading the signal without propagating it.
Ask the vendor: How did you handle the January 2026 state laws, and how far ahead of the effective date did it ship?
Privacy program breadth
Weight 15%What we look at
Coverage beyond consent, including data mapping, assessments, subject request automation, vendor lists, and incident response.
Strong looks like
An integrated suite where consent records flow into the rest of the program without custom work.
Limited looks like
Consent only, or a high-lift solution to implement.
Ask the vendor: If we add subject request automation in eighteen months, is that a module we can easily add on?
Evidence and auditability
Weight 10%What we look at
Whether you can prove, on demand, what a specific visitor consented to and what your site then did.
Strong looks like
Time-stamped records, retention matching your longest limitation period, exportable audit trails, and some means of validating tag behavior against recorded consent.
Limited looks like
Reporting that documents what the banner captured but no information on whether it was enforced.
Ask the vendor: Produce the record you would hand a regulator asking what visitor X consented to on a given date, and what our site did in response.