Prebid Server Connector for Revive Adserver

Prebid Server Connector sends Revive Adserver ad requests to a Prebid Server endpoint and brings the winning bids back as candidates against your direct campaigns. Publishers add server-side demand to Revive Adserver and keep one place to decide what wins.

What it does

• Ad requests go to a Prebid Server endpoint of your choice, your own or a hosted one, so you decide where the auction runs.
• Requests use stored requests, which keeps the bidder setup on the server side and the request from Revive Adserver short.
• Server-side bidders, timeouts and account ids are set in the Revive Adserver admin, so ad ops can adjust demand partners without code changes.
• Winning bids return to Revive Adserver as candidates that compete with direct campaigns, so programmatic demand is weighed against your guaranteed and house deals in one decision.
• A cookie sync proxy endpoint is included, which supports user id matching between bidders and your domain.
• Bid responses and timeouts are logged, so you can see which bidders answered, which timed out and why a slot stayed empty.

How it fits your ad stack

Prebid.js is the open-source header bidding wrapper maintained by Prebid.org, and Prebid Server runs auctions server-side. Teams that run server-side auctions usually check their bid requests and responses against the OpenRTB 2.6 protocol from IAB Tech Lab. The connector works between Revive Adserver and the Prebid Server endpoint you point it at.

Full feature details

• Sends Revive Adserver ad requests to a Prebid Server endpoint, your own or a hosted one.
• Uses stored requests for the request configuration.
• Admin settings for server-side bidders, timeouts and account ids.
• Cookie sync proxy endpoint.
• Returns winning bids to Revive Adserver as candidates that compete with direct campaigns.
• Logs bid responses and timeouts for debugging.

Requirements

• A running Revive Adserver 6.x installation.
• A Prebid Server endpoint, either self-hosted or from a hosting provider, and your account id on it.
• Stored requests set up on that endpoint.
• Further technical details confirmed at order.

Frequently asked questions

Do I need my own Prebid Server?

No. The connector works with your own Prebid Server or a hosted one. You supply the endpoint address and account id.

How do programmatic bids compete with direct campaigns?

Winning bids come back to Revive Adserver as candidates that compete with direct campaigns, so the ad server makes the final choice between them.

How do I find out why a bidder did not deliver?

The connector logs bid responses and timeouts. Check the log to see whether a bidder answered, returned nothing or timed out.