Back to Bidders



Bidder Code adf Member yes
Media Types display, video, native GDPR TCF Support yes
User IDs britepoolId, criteo, id5Id, identityLink, liveIntentId, netId, parrableId, pubCommonId, sharedId, unifiedId USP/CCPA Support yes
Supply Chain Support yes COPPA Support no
Demand Chain Support no Safeframes OK check with bidder
Supports Deals check with bidder Prebid.js Adapter yes
IAB GVL ID 50 Prebid Server Adapter yes
Floors Module Support yes First Party Data Support yes

"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_adf hb_bidder_adf hb_adid_adf
hb_size_adf hb_source_adf hb_format_adf
hb_cache_host_adf hb_cache_id_adf hb_uuid_adf
hb_cache_path_adf hb_deal_adf
This bidder previously had a bidder code of `adformOpenRTB`, but prefers new configurations to use `adf`.

Bid params

Name Scope Description Example Type
mid required, if inv and nmane not set Placement ID 12345 integer
inv required, if mid not set Inventory source ID 1234 integer
mname required, if mid not set Placement name "Leaderboard" string
adxDomain optional, Prebid.js only The Adform domain "" string
priceType optional, Prebid.js only Price type "gross" string

Note: Bid placement should be defined using the mid parameter or inv and mname parameters (dynamic master tag) but not both.

OpenRTB request config

OpenRTB bid request app, site, device properties configured using prebid config.

  ortb2: {
    app: {
      name: 'My APP'

Back to Bidders