Yandex
Features
Bidder Code | yandex | Prebid.org Member | no |
---|---|---|---|
Media Types | display, native | GDPR TCF Support | no |
User IDs | none | USP/CCPA Support | no |
Supply Chain Support | no | COPPA Support | no |
Demand Chain Support | no | GPP Support | no |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | check with bidder | 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_yandex |
hb_bidder_yandex |
hb_adid_yandex |
hb_size_yandex |
hb_source_yandex |
hb_format_yandex |
hb_cache_host_yandex |
hb_cache_id_yandex |
hb_uuid_yandex |
hb_cache_path_yandex |
hb_deal_yandex |
Bid params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
pageId |
required | Page ID | 123 |
Integer |
impId |
required | Block ID | 1 |
Integer |
Test Parameters
var adUnits = [{
code: 'banner-1',
mediaTypes: {
banner: {
sizes: [[240, 400]],
}
},
bids: [{
{
bidder: 'yandex',
params: {
pageId: 346580,
impId: 143,
},
}
}]
}];