Back to Bidders

AdPort

Features

Bidder Code adport Prebid.org Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display, video, native Multi Format Support will-bid-on-any
TCF-EU Support no IAB GVL ID none
GPP Support none DSA Support no
USP/CCPA Support no COPPA Support no
Supply Chain Support yes Demand Chain Support no
Safeframes OK no Supports Deals yes
Floors Module Support yes First Party Data Support yes
User IDs none ORTB Blocking Support yes
Privacy Sandbox check with bidder

Note

The AdPort Bidding adapter requires setup and approval before beginning. Please reach out to prebid@adport.com for more details.

Bid Params

Name Scope Description Example Type
adUnitId required Unique identifier for the ad unit in AdPort platform. 1 integer
auth required Authentication token provided by AdPort platform for the AdUnit. '61336e75e414c77c367eq5c47c2599ce80a8032b' string

Setting First Party Data (FPD)

Publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

  • ortb2.site.*
  • ortb2.app.*
  • ortb2.user.*

Example first party data:

pbjs.setConfig({
    ortb2: {
        site: {
            keywords: "kw1,kw2",
            content: {
                title: "title1",
                series: "series1"
            }
        },
        user: {
            keywords: "a,b",
            gender: "M",
            yob: 1984
        }
    }
});

ORTB Blocking

AdPort supports the next blocking parameters:

  • Blocked advertisers list (badv) is an array of domains as strings.
  • Blocked apps list (bapp) is an array of apps names as strings, for mobile apps in Google Play Store, these should be bundle or package names (e.g. com.foo.mygame). For apps in Apple App Store, these should be a numeric ID.
  • Blocked categories list (bcat) is an array of IAB categories as strings.
  • Blocked attributes list (battr) is an array of integers. Refer to section 5.3 of the IAB specification for a list of attributes.

Globally defined ORTB Blocking

pbjs.setConfig({
    ortb2: {
        badv: ["domain1.com", "domain2.com"],
        bapp: ["com.foo.mygame", "284708449"],
        bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
    }
});

ORTB Blocking specific only to the AdPort bidder

pbjs.setBidderConfig({
    bidders: ['adport'], // Or alias
    config: {
        ortb2: {
            badv: ["domain1.com", "domain2.com"],
            bapp: ["com.foo.mygame"],
            bcat: ["IAB23-1", "IAB23-5", "IAB25-3", "IAB25-2"]
        }
    }
});

Media Type defined ORTB Blocking

Additionally battr ORTB blocking param may be set on media types to specify blocked creative attributes. Refer to section 5.3 of the IAB specification for a list of attributes.

"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_adport hb_bidder_adport hb_adid_adport
hb_size_adport hb_source_adport hb_format_adport
hb_cache_host_adport hb_cache_id_adport hb_uuid_adport
hb_cache_path_adport hb_deal_adport

Back to Bidders