AJA
Features
Bidder Code | aja | Prebid.org Member | no |
---|---|---|---|
Media Types | display, video, native | GDPR TCF Support | no |
User IDs | criteo, unifiedId, imuid | USP/CCPA Support | no |
Supply Chain Support | no | COPPA Support | no |
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 | no | First Party Data Support | check with bidder |
Multi Format Support | check with bidder | ORTB Blocking Support | check with bidder |
Safeframes OK | 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_aja |
hb_bidder_aja |
hb_adid_aja |
hb_size_aja |
hb_source_aja |
hb_format_aja |
hb_cache_host_aja |
hb_cache_id_aja |
hb_uuid_aja |
hb_cache_path_aja |
hb_deal_aja |
Note
The AJA Bidding adaptor requires setup and approval before beginning. Please reach out to ssp_support@aja-kk.co.jp for more details
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
asi |
required | ad spot hash code | '123abc' |
string |
Configuration
AJA recommends setting UserSync by iframe for monetization.
For Prebid.js v1.15.0 and later:
pbjs.setConfig({
userSync: {
filterSettings: {
iframe: {
bidders: "*", // '*' represents all bidders
filter: "include",
},
},
},
});
For Prebid.js v1.14.0 and before:
pbjs.setConfig({
userSync: {
iframeEnabled: true,
enabledBidders: ["aja"],
},
});