Your clients don't all run the same CMP. Their numbers still need to line up.

OneTrust at the enterprise account, Cookiebot at the retailer, Didomi at the publisher, Complianz on the WordPress sites. Each tool has its own dashboard, its own idea of a "consent rate", its own way of handling bots. The day a client asks why their GA4 conversions dropped after the banner redesign, you end up comparing numbers that were never meant to be compared.

ConsentLift sits on top of each client's CMP, without replacing it and without touching the banner, and measures everyone the same way.

What you get

One measurement, whatever the CMP. Opt-in rate, consent rate and decision rate, calculated with the same definitions on every domain, bots filtered. A client on OneTrust and a client on Cookiebot finally read in the same units. The definitions are public, in our glossary.

The detail you need to find the cause. Every rate breaks down by page, browser, device, country, source and campaign. The banner funnel shows, page by page, how many sessions see a banner, how many make a decision and how many accept.

The before and after of a change. You log the date of a CMP migration or a banner redesign in the CMP Change Timeline. ConsentLift compares the two periods and tells you, with a statistical test, whether the gap is real or down to chance.

Alerts you set per domain. A drop in opt-in or consent rate, or a bot rate above a threshold you choose. Nothing is switched on by default: you decide which clients to watch and from when.

Client access, limited to their own domains. Invite your contact at the client with the client role, and choose which domains they can access.

Install monitoring. For each domain, you see whether the script is sending data and when the last event arrived, without opening the browser console.

Four jobs it changes

Auditing a banner before touching it

Most banner recommendations are made by eye: look at the banner, compare it with best practice, propose a new version. Measuring for two weeks before proposing anything changes the conversation. You see whether the problem is a message that doesn't convince (low consent rate) or a banner people don't see or can't use (low decision rate), and on which browsers or pages.

That is how clients found a Firefox-only bug that had cut the opt-in rate by around 10 points on that browser, and a popup sitting on top of the banner that stopped anyone clicking "Accept". Neither showed up in the CMP's own dashboard.

Switching CMP without arguing about the numbers

When a client moves from one CMP to another, the old and the new one don't count the same way, so comparing their dashboards proves nothing. With an independent measurement, in place before the switch and left running after it, before and after use the same definition. You show the client a gap, its margin of error and the exact date of the switch. The detail: switching CMP without losing consent.

Explaining a data drop

"We've lost part of our conversions since September." The answer is often in the banner: a new version, a "Reject all" button moved to the first layer, a script that no longer loads on mobile. The opt-in rate broken down by source and device tells you in minutes whether the lost signal comes from consent, and where.

Reporting every month

Consent reporting comes down to three numbers read together: opt-in rate, decision rate and consent rate, with their trend and the changes logged in the timeline. ConsentLift's screens give you those numbers for each client; you put the report together, in your own branding. To explain the three rates to a client: opt-in rate vs consent rate; to put them in context: what a good cookie consent rate is.

What doesn't exist yet

We'd rather tell you now than in the demo:

• a single screen showing all your clients together;
• a monthly PDF report generated in your branding;
• automatic detection of a CMP or banner change (the timeline is filled in by hand);
• alerts switched on by default when you add a domain.

If any of these decides it for you, tell us: agency demand sets the order of what comes next.

Pricing

One plan, every feature: €149 a month for 5 domains, €19 a month per extra domain, on request beyond 30. Usage is counted in sessions shown a banner, bots filtered, up to one million per domain per month. See the details

Installation

One line of JavaScript, loaded asynchronously, under 5 KB compressed, placed next to the existing CMP. OneTrust, Cookiebot, Didomi, Axeptio, Tarteaucitron and Complianz are detected automatically (see integrations); a custom banner connects through CSS selectors. No migration, no connection to ad accounts, nothing to change in the client's banner.

A 30-minute demo

We look at your portfolio together: which CMPs, what volumes, which clients would ask the question first. And we prepare the install on a first domain.