NextMillennium
Features
Bidder Code | nextMillennium | Prebid.org Member | yes |
---|---|---|---|
Prebid.js Adapter | yes | Prebid Server Adapter | yes |
Media Types | display, video | Multi Format Support | check with bidder |
TCF-EU Support | yes | IAB GVL ID | dev-docs/bidders/nextMillennium.md |
GPP Support | check with bidder | DSA Support | check with bidder |
USP/CCPA Support | yes | COPPA Support | yes |
Supply Chain Support | yes | Demand Chain Support | no |
Safeframes OK | no | Supports Deals | no |
Floors Module Support | no | First Party Data Support | no |
User IDs | none | ORTB Blocking Support | check with bidder |
Privacy Sandbox | check with bidder | Prebid Server App Support | no |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
placement_id |
required | Placement ID, provided by nextMillennium | '12345' |
String |
group_id |
optional | Group ID, provided by nextMillennium | '12345' |
String |
Required one of the two parameters placement_id or group_id.
Further information for the auction on NextMillennium side is generated automatically.
For video ad requests, we recommend that you configure the mediaTypes.video
parameters in your Ad Units (https://docs.prebid.org/dev-docs/adunit-reference.html#video).
Additional options
disabledSendingStatisticData
The disabledSendingStatisticData
parameter disables sending statistics data to the nextMillennium server, such as bidRequested, bidResponse, noBid and bidTimeout events.
An example of enabling this option:
pbjs.setBidderConfig({
bidders: ['nextMillennium'],
config: {
disabledSendingStatisticData: true,
},
})
Currency
By default, the currency used for requires is USD
. But you can use any other currency in the request. To do this, you must set this currency through the Prebid.js configuration and all responses will be returned in this currency.
pbjs.setConfig({
// ...
"currency": {
"adServerCurrency": "JPY",
}
// ...
});
OpenRTB 2.5 supported parameters
The adapter for Prebid.js supports the following options:
site.pagecat
site.content.cat
site.content.language
device.sua
site.keywords
site.content.keywords
user.keywords
bcat
badv
wlang
wlangb
You can set these parameters through the Prebid.js configuration setup functions: pbjs.setConfig or pbjs.setBidderConfig. An example of setting openrtb parameters for the entire prebid.js script.
pbjs.setConfig({
ortb2: {
site: {
pagecat: ['IAB2-11', 'IAB2-12', 'IAB2-14'],
content: {
cat: ['IAB2-11', 'IAB2-12', 'IAB2-14'],
language: 'EN'
},
}
}
});
An example of setting openrtb parameters only for the NextMillennium adapter.
pbjs.setBidderConfig({
bidders: ['bidderB'],
config: {
ortb2: {
site: {
pagecat: ['IAB2-11', 'IAB2-12', 'IAB2-14'],
content: {
cat: ['IAB2-11', 'IAB2-12', 'IAB2-14'],
language: 'EN'
},
}
}
}
});
"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_nextMillennium |
hb_bidder_nextMillen |
hb_adid_nextMillenni |
hb_size_nextMillenni |
hb_source_nextMillen |
hb_format_nextMillen |
hb_cache_host_nextMi |
hb_cache_id_nextMill |
hb_uuid_nextMillenni |
hb_cache_path_nextMi |
hb_deal_nextMillenni |