Skip to content

Latest commit

 

History

History
121 lines (95 loc) · 4.05 KB

rtbhouse.md

File metadata and controls

121 lines (95 loc) · 4.05 KB
Raw
layout title description gvl_id tcfeu_supported dsa_supported pbjs pbs biddercode prebid_member floors_supported safeframes_ok media_types schain_supported userIds pbs_app_supported ortb_blocking_supported sidebarType
bidder
RTBHouse
Prebid RTB House Bidder Adapter
16
true
true
true
true
rtbhouse
true
true
true
banner, native
true
id5Id, identityLink, pubProvidedId
true
partial
1

Bid Params

{: .table .table-bordered .table-striped }

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:

  1. Reach out to your RTB House representative for setup coordination.

  2. 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 as seller and has to respond with X-Allow-FLEDGE: true http header.

    sellerTimeout is optional, defaults to 50 as per spec, will be clamped to 500 if greater.