AMX RTB
Features
Bidder Code | amx | Prebid.org Member | no |
---|---|---|---|
Prebid.js Adapter | yes | Prebid Server Adapter | no |
Media Types | display, video | Multi Format Support | true |
TCF-EU Support | yes | IAB GVL ID | 737 |
GPP Support | some (check with bidder) | DSA Support | check with bidder |
USP/CCPA Support | yes | COPPA Support | yes |
Supply Chain Support | yes | Demand Chain Support | check with bidder |
Safeframes OK | yes | Supports Deals | check with bidder |
Floors Module Support | yes | First Party Data Support | yes |
User IDs | all | ORTB Blocking Support | yes |
Privacy Sandbox | check with bidder |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
tagId |
required | Tag ID | 'cHJlYmlkLm9yZw' |
string |
testMode |
optional | Activate 100% fill ads | true |
boolean |
adUnitId |
optional | Ad Unit ID used in reporting. Will default to bid.adUnitCode |
'sticky_banner' |
string |
Bidder Settings
The AMX RTB bid adapter uses local storage. Please add storageAllowed
in your bidder settings.
Prebid note: please review with your legal counsel before enabling storageAllowed. Bidders utilizing browser storage may trigger the need for additional disclosures in your privacy policy and may imply that the bid adapter is performing an activity redundant with user ID systems like SharedID. See the ePrivacy Directive article 5(3) reference to ‘comprehensive information’.
// https://docs.prebid.org/dev-docs/publisher-api-reference/bidderSettings.html
pbjs.bidderSettings = {
amx: {
storageAllowed: true,
},
};
Test Parameters
To enable 100% fill test ads, you can use the following params
:
{
testMode: true,
tagId: "cHJlYmlkLm9yZw"
}
This will produce a bid at $10 with a test creative.
Note that the tagId
is case-sensitive. Do not use cHJlYmlkLm9yZw
in production environments: this ID is for testing only.
First Party Data
From Prebid.js >= 4.30, publishers can use the ortb2
configuration parameter to provide First Party Data. We accept all standard OpenRTB fields for both:
ortb2.site
ortb2.user
Note that all fields are optional. For contextual data (e.g. categories), standard IAB taxonomies are supported. We do not support passing first party data via bid parameters.
Example - Setting ortb2.site and ortb2.user fields
pbjs.setBidderConfig({
bidders: ["amx"],
config: {
ortb2: {
site: {
keywords: "kw1,kw2",
cat: ["IAB2"],
sectioncat: ["IAB2-1"],
pagecat: ["IAB2-22"],
content: {
context: 5,
},
},
user: {
yob: 1981,
keywords: "kw3",
},
},
},
});
"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_amx |
hb_bidder_amx |
hb_adid_amx |
hb_size_amx |
hb_source_amx |
hb_format_amx |
hb_cache_host_amx |
hb_cache_id_amx |
hb_uuid_amx |
hb_cache_path_amx |
hb_deal_amx |