Identity Pack for Header Bidding (UID2, EUID, ID5, SharedID)

Identity Pack for Header Bidding lets you configure Prebid user ID modules for UID2 or EUID, ID5 and SharedID from the Revive Adserver admin panel and adds the resulting extended user IDs to the bid requests your header bidding plugins send. Publishers get a controlled way to pass identity signals to bidders, and IDs go out only when the consent signal allows.

What it does

• One admin panel configures the UID2 or EUID, ID5 and SharedID modules, so identity settings live in one place instead of in scattered page code.
• Extended user IDs (eids) are added to the bid requests sent by your header bidding plugins, so bidders receive the identity signals you choose to share.
• Token refresh is handled for you, which keeps IDs current without manual re-issuing.
• IDs are passed only when the consent signal allows, so identity sharing follows the choice the visitor made.
• A report shows the ID availability rate per zone, so you can see which zones actually yield IDs and where to look when the rate is low.

How it fits your ad stack

The pack works with the header bidding plugins that send bid requests from Revive Adserver zones, and it sits in the admin panel and the reporting area. Prebid.js is the open-source header bidding wrapper maintained by Prebid.org, and its user ID modules are the mechanism this pack configures. Teams that pass identity signals usually read the IAB Tech Lab ID Solutions Guidance v1.0 alongside their consent setup, and consent strings are commonly carried by the IAB Europe Transparency and Consent Framework and the IAB Tech Lab Global Privacy Platform.

Full feature details

• Admin panel to configure Prebid user ID modules for UID2 or EUID, ID5 and SharedID.
• Adds extended user IDs (eids) to bid requests sent by header bidding plugins.
• Token refresh handling.
• Consent-gated delivery: IDs are only passed when the consent signal allows.
• Reporting of ID availability rate per zone.
• Credentials for each identity provider are entered by the publisher.

Requirements

• A running Revive Adserver 6.x installation with a header bidding plugin that sends bid requests.
• Credentials from each identity provider you want to use (UID2 or EUID, ID5; SharedID details confirmed at order).
• A consent signal on your pages. Other technical details are confirmed at order.

Frequently asked questions

Do I need an account with each identity provider?

You supply the credentials from each identity provider yourself. The pack takes those credentials in its admin panel and does not issue them.

What happens when a visitor has not given consent?

IDs are only passed when the consent signal allows. Without a permitting signal, the IDs are not added to the bid request.

How do I know whether the IDs are reaching bidders?

The ID availability rate per zone report shows how often an ID was available for each zone, so you can compare zones and spot gaps.