Hashed First-Party List Activation for Revive Adserver

Hashed First-Party List Activation lets a publisher or network target Revive Adserver campaigns to its own audience lists without keeping the raw emails or phone numbers. Lists are uploaded as SHA-256 hashes, matched to a hashed identifier supplied by your page, and used as a targeting rule in banners and campaigns.

What it does

• Uploads audience lists as SHA-256 hashes of emails or phone numbers, so the raw values are not needed in Revive.
• Documented normalisation rules for emails and phone numbers mean a hash made on your side matches the hash made in the plugin.
• Matches list members to a hashed identifier your page supplies at login, so you can target people who have signed in to your own site.
• Banner and campaign targeting against a list lets you serve a message to your own customers or members in chosen zones.
• Matching only runs when the consent signal allows it, and counts the consent state used, so the decision is visible in reports.
• List expiry and deletion settings keep audiences from living longer than you intend.

How it fits your ad stack

The plugin adds a list-based targeting rule to Revive Adserver banners and campaigns, and your page passes the hashed identifier at delivery. Match rates are reported as counts only. It does not send lists to third parties and does not act as a clean room. Teams that use first-party audience data commonly work to GDPR and CCPA/CPRA, and TCF and GPP are the standards that carry the consent signals through the supply chain.

Full feature details

• Upload of audience lists as SHA-256 hashes of emails or phone numbers.
• Documented normalisation rules for emails and phone numbers.
• Matching to a hashed identifier supplied by your page.
• Banner and campaign targeting to list members by zone.
• Matching only when the consent signal allows it.
• Counts of the consent state used for each match decision.
• List expiry and deletion settings.
• Match-rate report (counts only).
• No transfer of lists to third parties; not a clean room.

Requirements

• A running Revive Adserver installation of a version listed in the Product Versions drop-down on this page.
• A page or login system that can supply a hashed identifier to the ad tag.
• A consent signal on the page if you want matching tied to consent. Other details are confirmed at order.

Frequently asked questions

Are the raw emails stored?

The plugin works from hashes you upload. How lists are prepared on your side is up to you, and the plugin documents the normalisation rules to use.

Is this a clean room?

No. Lists stay in your Revive install and are not shared with third parties or matched across companies.

What does the report show?

Match rates and consent states used, as counts only.