DecidePrivacy logo DecidePrivacy

Let users see what "Accept" and "Decline" actually do.

Replace your cookie banner with a revenue engine that respects user privacy and earns trust.

DecidePrivacy outcome-shown consent banner works as a first-layer overlay on top of your existing CMP. Nothing renders before a choice. After Accept, the banner renders a personalized creative; after Decline, it renders a non-personalized creative.

Pilot setup

Scope
1 template / 1 domain
Design
A/B: 50/50 vs current first layer
Sample
Target: 25k eligible encounters per arm
Duration
4–8 weeks or until sample hit
Reporting
Daily export + Safari split

How it works

  1. First-layer replacement — Our overlay replaces your CMP's first layer; consent is stored via your CMP.
  2. Pre-choice and post-choice flows — Pre-choice: no ads are shown. Decline triggers NP path; Accept triggers P path (with purge).
  3. Resurfacing — Your CMP controls re-prompt policy. We report the observed encounter rate.

What we measure

Key metrics collected during the pilot to evaluate performance.

  • Consent lift — Accept-rate delta vs. control (overall + Safari).
  • Proceed rate — Proceed-to-content delta vs. control.
  • Encounter rate — Percentage of sessions showing the first layer (overall + Safari).
  • Banner economics — Impressions, fill, and RPM for P, NP, and blended creatives.

Frequently asked questions

Does this replace our CMP?
No. DecidePrivacy overlays the first layer only and writes consent via your existing CMP. Your CMP remains the system of record for consent storage and vendor management.
Do you show ads before consent?
No. Nothing is shown before a user makes their choice. Pre-choice: no ads are displayed. Only after the user accepts or declines do we trigger the appropriate ad path.
Which CMPs do you support?
We integrate with TCF 2.2-compliant CMPs. Detailed integration specifications are shared during the pilot onboarding process.
What do you need from us?
Page URL, CMP provider, traffic estimate, and ad stack context. We'll work with your team to configure the integration during onboarding.
How is impact measured?
Via A/B testing on eligible consent encounters. We report overall metrics plus a Safari split to account for browser-specific behaviors.
Is this 'consent or pay'?
No. This is an ad-supported consent UI overlay. Users choose between personalized ads, non-personalized ads, or Decline — all free options.
What happens after the pilot?
If KPIs are met, we discuss commercial terms. If not, there's no obligation. Pilot revenue is retained by the publisher regardless of outcome.
How long does integration take?
Typically 1–2 weeks for technical integration, followed by a 4–8 week pilot period to reach statistical significance.