Panxo
Features
| Bidder Code | panxo | Prebid.org Member | yes |
|---|---|---|---|
| Prebid.js Adapter | yes | Prebid Server Adapter | no |
| Media Types | display | Multi Format Support | will-not-bid |
| TCF-EU Support | yes | IAB GVL ID | 1527 |
| 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 |
| Endpoint Compression | check with bidder | ORTB Blocking Support | no |
| User IDs | none | Privacy Sandbox | check with bidder |
Before You Begin
The Panxo adapter requires the Panxo RTD Module to be included in your Prebid.js build. The RTD module detects AI-referred traffic and enriches bid requests with classification signals that the adapter needs to participate in the auction.
Please register at app.panxo.com to obtain your siteId (for the RTD module) and propertyKey (for the bid adapter).
Important: Without the Panxo RTD module configured, the adapter will not participate in the auction.
Bid Params
| Name | Scope | Description | Example | Type |
|---|---|---|---|---|
propertyKey |
required | Property identifier from Panxo dashboard | 'abc123def456' |
string |
floor |
optional | Minimum CPM floor price in USD | 0.50 |
number |
Setup Example
Step 1: Build Prebid.js with required modules
Include both panxoRtdProvider and panxoBidAdapter in your Prebid.js build:
gulp build --modules=rtdModule,panxoRtdProvider,panxoBidAdapter,...
Or select both Panxo RTD Module and Panxo on the Prebid Download page.
Step 2: Configure RTD module and ad units
pbjs.setConfig({
realTimeData: {
auctionDelay: 300,
dataProviders: [{
name: 'panxo',
waitForIt: true,
params: {
siteId: 'your-site-id'
}
}]
}
});
var adUnits = [{
code: 'banner-ad',
mediaTypes: {
banner: {
sizes: [[300, 250], [728, 90]]
}
},
bids: [{
bidder: 'panxo',
params: {
propertyKey: 'your-property-key'
}
}]
}];
First Party Data
This adapter supports First Party Data via ortb2:
ortb2.site.*(name, cat, content, keywords, etc.)ortb2.user.*(data, ext)
User Sync
Panxo supports pixel-based user sync:
pbjs.setConfig({
userSync: {
filterSettings: {
pixel: {
bidders: ['panxo'],
filter: 'include'
}
}
}
});
Additional Notes
- Net Revenue: Bids are returned as net revenue.
- TTL: 300 seconds (5 minutes)
- Currency: USD
- Safeframes: Supported
- Advertiser Domains: Available in bid responses at
meta.advertiserDomains
"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_panxo |
hb_bidder_panxo |
hb_adid_panxo |
hb_size_panxo |
hb_source_panxo |
hb_format_panxo |
hb_cache_host_panxo |
hb_cache_id_panxo |
hb_uuid_panxo |
hb_cache_path_panxo |
hb_deal_panxo |