Your CMP gives you a consent rate. It's wrong.
Your CMP counts bots and ignores the visitors who never click. ConsentLift measures your real opt-in rate — bots filtered, banners seen without a decision counted — broken down by page, browser, device, country and source. On top of your CMP, no migration.
Works with Didomi, OneTrust, Cookiebot, Axeptio, Tarteaucitron, Complianz
Two real leaks caught at customers: at one, a Firefox-specific bug had dropped opt-in by about 10 points on that browser; at the other, an exit-intent popup was covering the CMP and blocking every click on "Accept" — weeks of lost consents, invisible in the CMP. Surfaced via the banners-shown / interactions gap and the per-browser breakdown.
The two leaks described are past incidents, observed at customers.
Step 1 · Measure
Your real opt-in rate, with no blind spot
One line of code on top of your CMP. From the first hour, your real opt-in rate broken down by browser, device, page and source — the data neither your CMP nor GA4 shows you.
Overview
SDK live · 7,123 events / 24hOpt-in rate
63.7%
+21 pp
Consent rate
89.4%
+2.3 pp
Banners shown
124,800
30d
Interactions
88,900
+62%
Accept All
79,500
+58%
Reject All
9,400
+71%
Consent rate over time (30d)
Consent by category
OneTrustConsent by device
Product preview with sample data. Your real numbers are available within the first hour.
Step 2 · Optimize
Find the pages that cost you consents
ConsentLift shows, page by page, where the banner is displayed and no decision follows.
Banner funnel by page
Where do you lose the most sessions between banner shown and decision?
Sessions with a banner
98,400
distinct sessions
Decided sessions
69,900
decided-session rate: 71%
Lost sessions
28,500
banner seen, no decision
Top 3 pages
51%
of concentrated loss
| PAGE | VIEWS | DECIDED | % DECIDED | % ACCEPT | LOSS |
|---|---|---|---|---|---|
| /accueil | 24,300 | 15,800 | 65% | 91% | 8,500 |
| /produits | 12,100 | 8,700 | 72% | 90% | 3,400 |
| /panier | 8,900 | 7,100 | 80% | 89% | 1,800 |
| /blog/guide-consentement | 6,400 | 3,800 | 59% | 92% | 2,600 |
| /tarifs | 5,200 | 3,900 | 75% | 90% | 1,300 |
| /contact | 3,800 | 2,900 | 76% | 88% | 900 |
| /a-propos | 2,900 | 2,100 | 72% | 91% | 800 |
Product preview with sample data. Your real numbers are available within the first hour.
Step 3 · Estimate
Estimate what it costs you
Every point of opt-in you lose has a cost. We do not claim to measure it to the euro — nobody honestly can. Our calculator applies a documented model to your own figures and gives you a range, with every assumption shown and editable.
Measure your consent, optimize it, estimate what it costs
Measure your real opt-in rate
A single line of JavaScript (under 5KB gzipped, async) placed on top of your existing CMP — Didomi, OneTrust, Cookiebot, Axeptio, Tarteaucitron, Complianz. Within the first hour, you see your real opt-in rate, broken down by browser, device, page, country and traffic source. No banner change, no ad-account connection required.
Set up alerts on your rates
You can set up alerts: a drop in your opt-in or consent rate, or a bot rate above the threshold you choose.
Estimate the impact in euros
Every point of opt-in you lose has a cost. We do not claim to measure it to the euro — nobody honestly can. Our calculator applies a documented model to your own figures and gives you a range, with every assumption shown and editable.
The measurement layer missing between your CMP and your analytics
vs your CMP
A complement, not a replacement.
Your Didomi or OneTrust collects consent. ConsentLift measures what your banner actually gets — and catches its failures. No migration: we plug on top.
vs GA4 / Adobe
GA4 measures what it sees. ConsentLift measures what it doesn't.
GA4 only sees the visitors who accepted. ConsentLift counts banners shown, decisions and refusals — including the sessions that never decide — and breaks them down browser by browser.
vs naive counting
We detect the banner bugs that cost you consents.
Surfaced by comparing banners shown to actual interactions, then breaking it down browser by browser: an abnormal gap reveals a technical problem, invisible in the CMP itself.
What your marketing, IT and DPO teams will ask
How do you detect banner or CMP issues?
By continuously comparing banners shown to actual interactions, then breaking it down by browser and page. An abnormal gap reveals a technical problem. This is how we caught, at customers, an exit-intent popup covering the CMP and blocking every click on "Accept", and a Firefox-specific bug blocking the click on the banner — two consent leaks completely invisible in the CMP itself.
Do you offer industry benchmarks?
No, and we are not announcing a date. An industry benchmark only means something beyond several dozen sites per category; below that it is an average drawn from a handful of accounts with a label on it. What your demo does contain: your own opt-in rate, measured on the banners actually shown on your site, broken down by page, browser, device and source.
Where is my data stored?
Consent events are stored with Tinybird, in London (United Kingdom). They are first received by Cloudflare, on the node closest to the visitor, in memory and without being stored there. The application and configuration database run on a Hetzner server in Nuremberg (Germany); account authentication goes through Auth0, United States region. The full list, with what each provider processes, is in our privacy policy.
What data do you collect?
Consent events: banner display, decision and categories, with the page path, the referring domain, the country and the device type, plus two random identifiers (session and page view) linked to no name, email address or IP address. No persistent visitor identity: the session identifier does not outlive the tab. The SDK does not read third-party cookies or browser storage outside its own namespace. The details, including retention periods and our server logs, are in the privacy policy.
Performance impact on my site?
SDK under 5KB gzipped, async loading, never blocking: it delays neither rendering nor interaction.
Which CMPs do you support?
Auto-detection of Didomi, OneTrust, Cookiebot, Axeptio, Tarteaucitron, Usercentrics, Complianz and any CMP exposing IAB TCF v2.2. Custom configuration (CSS selectors) for in-house banners.
How fast do we see the first numbers?
First consent events flow in within an hour. The per-page, per-browser, per-device, per-country and per-source breakdowns settle as soon as volume allows.
How do you estimate lost revenue?
Three sources: ghost conversions (attributable sales not reported by platforms), lost retargeting (spend on incomplete audiences), algorithm degradation (ad optimization weakened by missing signal). Each assumption is documented and editable in the public calculator, with low / mid / high estimates.
Contract, DPA, certifications?
MSA and DPA: contact us. We hold no SOC 2 or ISO 27001 certification today, and we are not announcing a date.
See your real opt-in rate, banner by banner
30 minutes with our team. Personalized demo on your industry.
Book a demo