FutureAds
Features
Bidder Code | futureads | Prebid.org Member | yes |
---|---|---|---|
Media Types | display, video, native | GDPR TCF Support | yes |
User IDs | AdmixerID | USP/CCPA Support | yes |
Supply Chain Support | yes | COPPA Support | no |
Demand Chain Support | no | GPP Support | no |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | 511 | Prebid Server Adapter | yes |
Floors Module Support | no | First Party Data Support | check with bidder |
Multi Format Support | check with bidder | ORTB Blocking Support | check with bidder |
Safeframes OK | check with bidder |
"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_futureads |
hb_bidder_futureads |
hb_adid_futureads |
hb_size_futureads |
hb_source_futureads |
hb_format_futureads |
hb_cache_host_future |
hb_cache_id_futuread |
hb_uuid_futureads |
hb_cache_path_future |
hb_deal_futureads |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
zone |
required | The unique identifier of the ad placement. Could be obtained from the FutureAds UI or from your account manager. | “e5ff8e48-4bd0-4a2c-9236-55530ab8981d” | string |
kvTargeting |
optional | Key/Value - a pair of the unique values that will be used for the custom targeting option. | {key1: value2, key2: value2} | object |