8pod
Features
| Bidder Code | eightPod | Prebid.org Member | no |
|---|---|---|---|
| Prebid.js Adapter | yes | Prebid Server Adapter | no |
| Media Types | display, video | Multi Format Support | will-not-bid |
| TCF-EU Support | no | IAB GVL ID | none |
| GPP Support | none | DSA Support | check with bidder |
| USP/CCPA Support | no | COPPA Support | no |
| Supply Chain Support | no | Demand Chain Support | no |
| Safeframes OK | no | Supports Deals | no |
| Floors Module Support | no | First Party Data Support | yes |
| User IDs | check with bidder | ORTB Blocking Support | no |
| Privacy Sandbox | check with bidder |
Registration
The EightPod adapter requires setup before beginning. Please contact us at ewald@8pod.com
Bid Params
| Name | Scope | Description | Example | Type |
|---|---|---|---|---|
placementId |
required | The unique identifier of the ad placement. Could be obtained from the 8pod UI or from your account manager. | “placementId-438753744289” | string |
publisherId |
optional | The unique identifier of the publisher. | “publisherId-438753744289” | string |
First Party Data
We accept all standard OpenRTB 2.6 fields for following object:
ortb2.site
ortb2.user
ortb2.device
ortb2.user.data.*
ortb2.site.content.data
Note that all fields are optional. For contextual data (e.g. categories), standard IAB taxonomies are supported. Also, note that any 1st party data circulation should be agreed in advance.
"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_eightPod |
hb_bidder_eightPod |
hb_adid_eightPod |
hb_size_eightPod |
hb_source_eightPod |
hb_format_eightPod |
hb_cache_host_eightP |
hb_cache_id_eightPod |
hb_uuid_eightPod |
hb_cache_path_eightP |
hb_deal_eightPod |