RTBHouse
Features
Bidder Code | rtbhouse | Prebid.org Member | yes |
---|---|---|---|
Prebid.js Adapter | yes | Prebid Server Adapter | yes |
Media Types | display, native | Multi Format Support | check with bidder |
TCF-EU Support | yes | IAB GVL ID | 16 |
GPP Support | check with bidder | DSA Support | yes |
USP/CCPA Support | check with bidder | COPPA Support | check with bidder |
Supply Chain Support | yes | Demand Chain Support | check with bidder |
Safeframes OK | yes | Supports Deals | check with bidder |
Floors Module Support | yes | First Party Data Support | check with bidder |
User IDs | id5Id, identityLink, pubProvidedId | ORTB Blocking Support | partial |
Privacy Sandbox | check with bidder | Prebid Server App Support | yes |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
publisherId |
required | Unique publisher ID | 'ABCDEF' |
string |
region |
required | Assigned region | 'prebid-eu' |
string |
bidfloor |
optional | Minimal CPM value | 0.01 |
float |
channel |
optional | Inventory channel identifier, limited to 50 characters | Partner 1 - News |
string |
Please note
-
Since 4.43 the bidfloor param will be ignored if a value is specified via floor module.
-
The channel param is available starting from Prebid 6.6.0. Please reach your RTBHouse representative for details on how to enable and use the channel param.
ORTB Blocking
RTB House supports blocking advertisers in badv
and categories in bcat
parameters.
The blocked advertisers/categories list has no length limitation, but response timeout is more likely to occur as the number of entries grow.
Blocked advertisers list (badv
) is an array of domains as strings.
Blocked categories list (bcat
) is an array of IAB categories as strings.
For example:
Globally defined ORTB Blocking
pbjs.setConfig({
ortb2: {
badv: ["domain1.com", "domain2.com"],
bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
}
)};
ORTB Blocking specific only to rtbhouse bidder
pbjs.setBidderConfig({
bidders: ['rtbhouse'],
config:{
ortb2: {
badv: ["domain1.com", "domain2.com"],
bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
}
}
});
Setting up the Prebid Server Adapter
If you’re a Prebid Server host company looking to enable the RTB House server-side adapter, you’ll need to contact prebid@rtbhouse.com. They will guide you through the process. Do not use the default bidder config file as it will require custom partner code to be entered. It will be provided by RTB House.
Protected Audience API (PAAPI) support
There’s an option to receive demand for Protected Audience API (FLEDGE/PAAPI) ads using RTB House bid adapter. Prebid’s paapiForGpt module and Google Ad Manager is currently required.
The following steps should be taken to setup Protected Audience for RTB House:
-
Reach out to your RTB House representative for setup coordination.
-
Build and enable PAAPI module as described in paapiForGpt module documentation.
a. Make sure to enable RTB House bidder to participate in PAAPI. If there are any other bidders to be allowed for that, add them to the bidders array:
pbjs.setConfig({ paapi: { enabled: true, bidders: ["rtbhouse"] } })
b. If you as a publisher have your own decisionLogicUrl you may utilize it by setting up a dedicated
fledgeConfig
object:pbjs.setBidderConfig({ bidders: ["rtbhouse"], config: { fledgeConfig: { seller: 'https://seller.domain', decisionLogicUrl: 'https://seller.domain/decisionLogicFile.js', sellerTimeout: 100 } } });
The
decisionLogicUrl
must be in the same domain asseller
and has to respond withX-Allow-FLEDGE: true
http header.sellerTimeout
is optional, defaults to 50 as per spec, will be clamped to 500 if greater.
"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_rtbhouse |
hb_bidder_rtbhouse |
hb_adid_rtbhouse |
hb_size_rtbhouse |
hb_source_rtbhouse |
hb_format_rtbhouse |
hb_cache_host_rtbhou |
hb_cache_id_rtbhouse |
hb_uuid_rtbhouse |
hb_cache_path_rtbhou |
hb_deal_rtbhouse |