Back to Bidders
Relay
Features
| Bidder Code |
relay |
Prebid.org Member |
no |
| Media Types |
display, video, native |
TCF-EU Support |
no |
| User IDs |
none |
USP/CCPA Support |
no |
| Supply Chain Support |
yes |
COPPA Support |
yes |
| Demand Chain Support |
no |
GPP Support |
check with bidder |
| Supports Deals |
yes |
Prebid.js Adapter |
yes |
| IAB GVL ID |
check with bidder |
Prebid Server Adapter |
no |
| Floors Module Support |
yes |
First Party Data Support |
yes |
| Multi Format Support |
will-bid-any |
ORTB Blocking Support |
partial |
| Safeframes OK |
yes |
|
|
Bid Params
| Name |
Scope |
Description |
Example |
Type |
accountId |
required |
Relay Account Id |
9778 |
'number' |
Note
The Relay Bid Adapter makes requests to the Relay Exchange API which supports OpenRTB.
Therefore the only bid param required is the the accountId, all Prebid Ad Unit fields will be automatically inferred via Prebid’s ORTB Converter. If any field on the request requires customization it is configurable using First Party Data - Prebid.js via ortb2 interface. We support all FPD fields: site.content.data, site.ext.data., user.data, user.ext.data.
"Send All Bids" Ad Server Keys
These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_relay |
hb_bidder_relay |
hb_adid_relay |
hb_size_relay |
hb_source_relay |
hb_format_relay |
hb_cache_host_relay |
hb_cache_id_relay |
hb_uuid_relay |
hb_cache_path_relay |
hb_deal_relay |
|
Back to Bidders