Building a Consent Analytics Dashboard: Metrics Publishers Should Track
Why Consent Is a Measurable Funnel
Most publishers treat consent as a binary compliance checkbox. In reality it is a revenue funnel: a banner is shown, the user interacts, a choice is recorded, and that choice determines how much of your inventory can be monetized at full value. Every step has a drop-off you can measure and improve.
The Core Metrics
A useful consent dashboard tracks at least these:
- Consent rate — the percentage of users who grant consent. The single most important number; a few points here move real revenue.
- Interaction rate — how many users engage with the banner at all versus ignore it.
- Reject rate & partial consent — how many decline, and how many grant some purposes but not others.
- Time-to-decision — long delays signal a confusing banner.
- Withdrawal rate — how often users later revoke consent.
Slice Everything by Dimension
An aggregate consent rate hides the story. Break every metric down by:
- Geography — EEA vs. UK vs. rest-of-world behave very differently.
- Platform — iOS (with ATT in the mix), Android, web, and PWA.
- Language / locale — a poorly translated banner tanks consent in that market.
- Banner variant — so A/B tests are measurable.
This is where a dashboard earns its keep: it turns “our consent rate is 62%” into “our German Android consent rate dropped 9 points after the last banner change.”
Connect Consent to Revenue
The metric that convinces stakeholders is revenue per mille split by consent state. Show the eCPM of consented vs. non-consented traffic side by side and the cost of every declined banner becomes concrete. Pair that with consent rate trends and you can forecast the revenue impact of any banner change before you ship it.
Watch for Compliance Signals Too
The same dashboard should surface compliance health: stale or missing TC strings, Consent Mode v2 signals that never fired, and anomalies that suggest a broken banner. A sudden 100% consent rate is not a win — it usually means the banner stopped recording rejections.
How FlexyConsent Helps
FlexyConsent ships these analytics out of the box: consent, interaction, reject, and withdrawal rates sliced by geography, platform, language, and banner variant, with TC-string and Consent Mode v2 health checks alongside. You see exactly where consent — and revenue — is being won or lost, across every property.
Key Takeaways
- Treat consent as a measurable funnel, not a checkbox.
- Track consent, interaction, reject, withdrawal rates and time-to-decision.
- Slice by geography, platform, language, and banner variant to find real problems.
- Tie consent state to eCPM so banner changes can be judged on revenue.