Aseal
Features
Bidder Code | aseal | Prebid.org Member | no |
---|---|---|---|
Media Types | display | GDPR TCF Support | no |
User IDs | none | USP/CCPA Support | no |
Supply Chain Support | no | COPPA Support | no |
Demand Chain Support | no | Safeframes OK | check with bidder |
Supports Deals | check with bidder | Prebid.js Adapter | yes |
IAB GVL ID | check with bidder | Prebid Server Adapter | no |
Floors Module Support | no | First Party Data Support | check with bidder |
Multi Format Support | check with bidder | ORTB Blocking Support | check with bidder |
"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_aseal |
hb_bidder_aseal |
hb_adid_aseal |
hb_size_aseal |
hb_source_aseal |
hb_format_aseal |
hb_cache_host_aseal |
hb_cache_id_aseal |
hb_uuid_aseal |
hb_cache_path_aseal |
hb_deal_aseal |
BidParams
Name | Scope | Description | Example | Type |
---|---|---|---|---|
placeUid |
required | The Place UID from Aotter | 'f4a74f73-9a74-4a87-91c9-545c6316c23d' |
string |
Configuration
Following configuration is required:
pbjs.setConfig({
aseal: {
clientId: "YOUR_CLIENT_ID"
}
});
Ad Unit Example
var adUnits = [
{
code: "banner-div",
mediaTypes: {
banner: {
sizes: [
[300, 250],
[300, 600]
]
}
},
bids: [
{
bidder: "aseal",
params: {
placeUid: "f4a74f73-9a74-4a87-91c9-545c6316c23d"
}
}
]
}
];