Billowlink
Features
| Bidder Code | billow_rtb25 | Prebid.org Member | no |
|---|---|---|---|
| Prebid.js Adapter | yes | Prebid Server Adapter | no |
| Media Types | display, video, native | Multi Format Support | will-bid-on-any |
| 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 | yes | Demand Chain Support | no |
| Safeframes OK | yes | Supports Deals | no |
| Floors Module Support | no | First Party Data Support | yes |
| Endpoint Compression | check with bidder | ORTB Blocking Support | no |
| User IDs | none | Privacy Sandbox | check with bidder |
Note
The Billowlink bidder adapter requires setup and approval before beginning. Please reach out to support@billowlink.com for more details.
This adapter sends requests to Billowlink using OpenRTB 2.5. Billowlink bids are returned in USD.
Bid Params
| Name | Scope | Description | Example | Type |
|---|---|---|---|---|
placementId |
required | Placement ID configured on the Billowlink side. This value is sent as OpenRTB imp.tagid. |
'12345' |
string |
endpoint |
optional | Overrides the default Billowlink bid endpoint. This is normally only needed for testing or staging. | 'https://adx-sg.billowlink.com/api/rtb/adsWeb' |
string |
First Party Data
Publishers should use the ortb2 method of setting First Party Data.
The adapter uses Prebid’s OpenRTB converter, so standard request-level and impression-level ORTB data can be included in the outgoing request.
Ad Unit Setup for Banner
var adUnits = [{
code: 'div-gpt-ad-123456-1',
mediaTypes: {
banner: {
sizes: [[300, 250], [728, 90]]
}
},
bids: [{
bidder: 'billow_rtb25',
params: {
placementId: '12345'
}
}]
}];
Ad Unit Setup for Video
var adUnits = [{
code: 'video-ad-unit',
mediaTypes: {
video: {
context: 'instream',
playerSize: [640, 480],
mimes: ['video/mp4'],
minduration: 1,
maxduration: 120,
protocols: [2, 3, 5, 6]
}
},
bids: [{
bidder: 'billow_rtb25',
params: {
placementId: 'video-placement-123'
}
}]
}];
For outstream video, publishers must provide a renderer through the ad unit or use their standard video integration.
Ad Unit Setup for Native
var adUnits = [{
code: 'native-ad-unit',
mediaTypes: {
native: {
ortb: {
ver: '1.2',
assets: [
{ id: 1, required: 1, title: { len: 80 } },
{ id: 2, required: 1, img: { type: 3, wmin: 100, hmin: 100 } }
]
}
}
},
bids: [{
bidder: 'billow_rtb25',
params: {
placementId: 'native-placement-123'
}
}]
}];
Endpoint Override
var adUnits = [{
code: 'div-gpt-ad-123456-2',
mediaTypes: {
banner: {
sizes: [[300, 250]]
}
},
bids: [{
bidder: 'billow_rtb25',
params: {
placementId: '12345',
endpoint: 'https://adx-sg.billowlink.com/api/rtb/adsWeb'
}
}]
}];
"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_billow_rtb25 |
hb_bidder_billow_rtb |
hb_adid_billow_rtb25 |
hb_size_billow_rtb25 |
hb_source_billow_rtb |
hb_format_billow_rtb |
hb_cache_host_billow |
hb_cache_id_billow_r |
hb_uuid_billow_rtb25 |
hb_cache_path_billow |
hb_deal_billow_rtb25 |