Consent and Privacy Signals Suite for Revive Adserver

Consent and Privacy Signals Suite reads the TCF v2 consent string and the GPP string on the page and applies them to ad delivery in Revive Adserver. Publishers decide per zone and region what is shown when consent is missing, and pass the same signals to their RTB and header bidding plugins.

What it does

• Reads the TCF v2 consent string and the GPP string on the page, so delivery decisions follow the signals the visitor actually gave.
• Zone and region rules choose what happens without consent: a contextual banner, a house ad or no ad, so you control the revenue and risk trade-off for each market.
• Passes gdpr, consent and privacy fields to RTB and header bidding plugins, so demand partners receive the same signals the page holds.
• Passes DSA transparency fields, so the data that goes with a bid request travels with the consent data.
• Counts consent outcomes in reports (counts only), so ad ops can see how often consent is present or absent by zone and region.

How it fits your ad stack

The suite works inside Revive Adserver delivery and is configured per zone and region in the admin. It does not act as a CMP itself, so you keep your existing consent management platform and this plugin reads what that platform places on the page. Teams serving EU traffic usually work with the IAB Europe Transparency and Consent Framework, and the IAB Tech Lab Global Privacy Platform (GPP) carries consent and preference signals, including US state privacy signals, through the advertising supply chain. GDPR and CCPA/CPRA are the privacy laws most often referenced by consent tools.

Full feature details

• Reads the TCF v2 consent string present on the page.
• Reads the GPP string present on the page, including US state signals.
• Applies the signals to ad delivery.
• Zone and region rules for the no-consent outcome: contextual banner, house ad or no ad.
• Passes gdpr, consent and privacy fields to RTB and header bidding plugins.
• Passes DSA transparency fields.
• Counts consent outcomes in reports (counts only).
• Admin settings per zone and region.
• Does not act as a CMP itself.

Requirements

• A running Revive Adserver 6.x install.
• A consent management platform of your own that places the TCF v2 and/or GPP strings on the page.
• RTB or header bidding plugins, if you want the fields passed on to them.
• Any other details are confirmed at order.

Frequently asked questions

Is this a consent management platform?

No. It does not act as a CMP itself. It reads the consent string and GPP string that your own consent platform places on the page and applies them to ad delivery.

What can I show when a visitor has not given consent?

Zone and region rules choose the outcome: a contextual banner, a house ad or no ad. You set this in the admin per zone and region.

What do the reports show?

They count consent outcomes only. No further consent detail is described beyond those counts.