Adnuntius
Features
Bidder Code | adnuntius | Prebid.org Member | no |
---|---|---|---|
Media Types | display, video | GDPR TCF Support | yes |
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 | 855 | Prebid Server Adapter | yes |
Floors Module Support | no | First Party Data Support | yes |
Multi Format Support | will-bid-on-any | ORTB Blocking Support | no |
Safeframes OK | no |
"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_adnuntius |
hb_bidder_adnuntius |
hb_adid_adnuntius |
hb_size_adnuntius |
hb_source_adnuntius |
hb_format_adnuntius |
hb_cache_host_adnunt |
hb_cache_id_adnuntiu |
hb_uuid_adnuntius |
hb_cache_path_adnunt |
hb_deal_adnuntius |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
auId |
required | The ad unit ID '0000000000072345' leading zeros can be omitted. |
'0000000000072345' |
string |
network |
optional | Used if you want to make requests to multiple networks in adnuntius. | 'adnuntius' |
string |
targeting |
optional | Targeting to be sent through to adnuntius with the request. | { c: ['prebids'] } |
string |
Targeting
The Adnuntius Documentation provides detailed information on sending targeting data to the Adnuntius adserver.
Example
Here’s an example of sending targeting information about categories to adnuntius via the bid request:
{
code: "0000000000072345",
mediaTypes: {
banner: {
sizes: [[980, 360], [980, 300], [980, 240], [980, 120]]
}
},
bids: [
{
bidder: "adnuntius",
params: {
auId: "8b6bc",
network: "adnuntius",
targeting: {
c: ['prebids']
}
}
}
]
}
Sending segments to the ad server
There’s an option to send segment id in the bidder config that will be picked up and sent to the ad server. Below is an example on how to do this:
pbjs.setBidderConfig({
bidders: ['adnuntius', 'bidderB'],
config: {
ortb2: {
user: {
data: [{
name: "adnuntius",
segment: [
{ id: "1" },
{ id: "2" }
]
}]
}
}
}
});
Disable cookies for adnuntius
You have the option to tell adnuntius not to set cookies in your browser. This does not mean that third party ads being served through the ad server will not set cookies. Just that Adnuintius will not set it for internal ads.
pbjs.setBidderConfig({
bidders: ['adnuntius'],
config: {
useCookie: false
}
});
Use cookie will always be set to true by default. Changing it to false will disable cookies.
Prebid Server Test Request
The following test parameters can be used to verify that Prebid Server is working properly with the server-side Adnuntius adapter. the auId
below will not return a creative. Please substitute it with your own.
"imp": [{
"id": "impression-id",
"banner": {
"format": [{
"w": 980,
"h": 240
}, {
"w": 980,
"h": 360
}]
},
"ext": {
"adnuntius": {
"auId": "abc123"
}
}
}]
Passing no Cookie in Prebid Server request
As a publisher you have the option to set no cookie in the device request to let Adnuntius adserver know not to set cookies in the client’s browser. In order to do that you just need to pass this in the request:
"device": {
"ext": {
"noCookies": true
}
},
First Party Data
publishers can use the ortb2
configuration parameter to provide First Party Data. We accept all standard OpenRTB fields for both:
ortb2.site
ortb2.user
These fields are optional and only needed for user identification and contextual targeting. How to use it can be read here: Prebid ortb2. Currently we only support this for our prebid server bidder, but will add it to the client bidder in the future.
Video requests
Currently we only support client requests and instream context. An example request would look like this:
{
code: 'video1',
mediaTypes: {
video: {
playerSize: [640, 480],
context: 'instream'
}
},
bids: [{
bidder: 'adnuntius',
params: {
auId: '00000000001cd429', //put your placement id here
video: {
skippable: true,
playback_method: ['auto_play_sound_off']
}
}
}]
};