Sharethrough
Features
Bidder Code | sharethrough | Prebid.org Member | no |
---|---|---|---|
Media Types | display, video | GDPR TCF Support | yes |
User IDs | all | USP/CCPA Support | yes |
Supply Chain Support | yes | COPPA Support | yes |
Demand Chain Support | no | GPP Support | no |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | check with bidder | Prebid Server Adapter | yes |
Floors Module Support | yes | First Party Data Support | yes |
Multi Format Support | check with bidder | ORTB Blocking Support | partial |
Safeframes OK | 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_sharethrough |
hb_bidder_sharethrou |
hb_adid_sharethrough |
hb_size_sharethrough |
hb_source_sharethrou |
hb_format_sharethrou |
hb_cache_host_sharet |
hb_cache_id_sharethr |
hb_uuid_sharethrough |
hb_cache_path_sharet |
hb_deal_sharethrough |
Disclosure:
This adapter is known to use an HTTP 1 endpoint. Header bidding often generates multiple requests to the same host and bidders are encouraged to change to HTTP 2 or above to help improve publisher page performance via multiplexing.
Note:
The Sharethrough bidder adapter requires additional setup and approval from the Sharethrough Integrations team. Please reach out to your account manager for more information to start using it.
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
pkey |
required | The placement key | 'DfFKxpkRGPMS7A9f71CquBgZ' |
string |
bcat |
optional | (deprecated) Array of blocked IAB Categories | ['IAB1-2', 'IAB1-3'] |
string[] |
badv |
optional | (deprecated) Array of blocked Advertisers by their domains | ['ford.com', 'pepsi.com'] |
string[] |
Note: Providing bcat
and badv
via Bid Params is deprecated, the First Party Data method should be preferred (see below).
When both methods are provided, first party data values will be used and bid param values will be ignored.
First Party Data
Publishers should use the ortb2
method of setting First Party Data. The following fields are supported:
ortb2.site.*
ortb2.user.*
For example:
pbjs.setConfig({
ortb2: {
site: {
name: "example",
cat: ["IAB2"],
keywords: "power tools, drills",
content: {
userrating: "4"
}
},
user: {
yob: 1985,
gender: "m",
keywords: "a,b",
ext: {
data: {
registered: true,
interests: ["cars"]
}
}
}
}
});
ORTB Blocking
Sharethrough supports blocking advertiser domains (badv
) and/or IAB Categories (bcat
) via First Party Data.
For example:
pbjs.setConfig({
ortb2: {
bcat: ["IAB1", "IAB2-1"],
badv: ["domain1.com", "domain2.com"],
}
});