Vidoomy
Features
Bidder Code | vidoomy | Prebid.org Member | no |
---|---|---|---|
Media Types | display, video | GDPR TCF Support | yes |
User IDs | all | USP/CCPA Support | yes |
Supply Chain Support | yes | COPPA Support | yes |
Demand Chain Support | no | GPP Support | no |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | 380 | Prebid Server Adapter | yes |
Floors Module Support | yes | First Party Data Support | check with bidder |
Multi Format Support | check with bidder | ORTB Blocking Support | yes |
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_vidoomy |
hb_bidder_vidoomy |
hb_adid_vidoomy |
hb_size_vidoomy |
hb_source_vidoomy |
hb_format_vidoomy |
hb_cache_host_vidoom |
hb_cache_id_vidoomy |
hb_uuid_vidoomy |
hb_cache_path_vidoom |
hb_deal_vidoomy |
Note:
Vidoomy, for more info please contact support@vidoomy.com
Client Side Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
id |
required | id | '123123' |
string |
pid |
required | pid | '123123' |
string |
bidfloor |
optional | CPM bidfloor in USD | 0.08 |
float |
Server Side Bid Params (Prebid Server)
Name | Scope | Description | Example | Type |
---|---|---|---|---|
zoneId |
required | Zone Id | '123123' |
string |
bcat |
optional | List of blocked advertiser categories (IAB) | ['IAB1-1'] |
string array |
badv |
optional | Blocked Advertiser Domains | ['example.com'] |
string array |
bapp |
optional | blocked advertiser mobile app bundles | ['app.com'] |
string array |
btype |
optional | blocked creative types (e.g. XHTML) | [1, 2, 3] |
int array |
battr |
optional | blocked creative attributes (e.g. audio) | [1, 2, 3] |
int array |
Notes:
- Preferred to provide the
bcat
,badv
,bapp
,btype
andbattr
within the first party data (above). When both methods are provided, first party data values will be prioritized.
First Party Data
Publishers can use the ortb2
configuration parameter to provide First Party Data.
OpenRTB Parameters
The following table contains currently supported parameters we parse.
Name | Scope | Description | Example | Type |
---|---|---|---|---|
bcat |
optional | List of blocked advertiser categories (IAB) | ['IAB1-1'] |
Array |
badv |
optional | Blocked Advertiser Domains | ['example.com'] |
Array |
bapp |
optional | blocked advertiser mobile app bundles | ['app.com'] |
Array |
btype |
optional | blocked creative types (e.g. XHTML) | [1, 2, 3] |
Array |
battr |
optional | blocked creative attributes (e.g. audio) | [1, 2, 3] |
Array |
Notes:
- will extract the bcat,badv,bapp,btype,battr if passed within
ortb2
Example configuration:
pbjs.setConfig({
ortb2: {
bcat: ['IAB1-1'],
badv: ['example.com'],
bapp: ['app.com'],
btype: [1, 2, 3],
battr: [1, 2, 3]
}
});