DistrictM DMX
Features
| Bidder Code | dmx | Prebid.org Member | no |
|---|---|---|---|
| Media Types | display, video | GDPR TCF Support | yes |
| User IDs | none | 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 | no |
| IAB GVL ID | 144 | 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_dmx |
hb_bidder_dmx |
hb_adid_dmx |
hb_size_dmx |
hb_source_dmx |
hb_format_dmx |
hb_cache_host_dmx |
hb_cache_id_dmx |
hb_uuid_dmx |
hb_cache_path_dmx |
hb_deal_dmx |
Bid Params
| Name | Scope | Description | Example | Type |
|---|---|---|---|---|
| seller_id | required | The DMX Partner ID provided upon onboarding, this is for specific setup BURL, NURL or ADM support | ‘seller_id’ | string |
| publisher_id | required | Boost MemberId from DistrictM UI | ‘member1’ | string |
| tagid | required | Represent the placement ID from DistrictM or your own | ‘123abc’ | string |
| bidfloor | optional | The minimum price acceptable for a bid | ‘1.0’ | string |
| memberid | optional | MemberId from DistrictM UI (legacy: replaced by publisher_id) | ‘member1’ | string |
| dmxid | optional | Placement ID from DistrictM (legacy: replaced by tagid) | ‘123abc’ | string |
(See districtmDMX for Prebid.js)