Scalibur
Features
| Bidder Code | scalibur | Prebid.org Member | no |
|---|---|---|---|
| Prebid.js Adapter | yes | Prebid Server Adapter | no |
| Media Types | display, video | Multi Format Support | will-bid-on-any |
| TCF-EU Support | no | IAB GVL ID | 1471 |
| GPP Support | tcfeu, usstate_all, usp | DSA Support | check with bidder |
| USP/CCPA Support | check with bidder | COPPA Support | yes |
| Supply Chain Support | yes | Demand Chain Support | no |
| Safeframes OK | yes | Supports Deals | no |
| Floors Module Support | yes | First Party Data Support | yes |
| Endpoint Compression | check with bidder | ORTB Blocking Support | no |
| User IDs | all | Privacy Sandbox | check with bidder |
The Scalibur Bid Adapter connects publishers to Scalibur’s programmatic advertising platform. It supports both banner and video ad formats through OpenRTB 2.x protocol and provides full compliance with privacy regulations.
Bid Params
| Name | Scope | Type | Description | Example |
|---|---|---|---|---|
placementId |
required | String | Placement identifier provided by Scalibur | 'test-placement-123' |
Test Parameters
For testing purposes, you can use the following ad unit configurations:
Banner Ad Unit
var adUnits = [
{
code: 'test-banner-div',
mediaTypes: {
banner: {
sizes: [[300, 250], [728, 90], [320, 50]]
}
},
bids: [
{
bidder: 'scalibur',
params: {
placementId: 'test-scl-placement'
}
}
]
}
];
Video Ad Unit
var adUnits = [
{
code: 'test-video-div',
mediaTypes: {
video: {
playerSize: [[640, 480]],
context: 'instream',
mimes: ['video/mp4'],
protocols: [2, 3, 5, 6],
minduration: 5,
maxduration: 30,
startdelay: 0,
playbackmethod: [1, 2],
api: [1, 2]
}
},
bids: [
{
bidder: 'scalibur',
params: {
placementId: 'test-scl-placement' // Required
}
}
]
}
];
Multi-format Ad Unit
var adUnits = [
{
code: 'test-multiformat-div',
mediaTypes: {
banner: {
sizes: [[300, 250], [728, 90]]
},
video: {
context: 'instream',
playerSize: [[300, 169]],
mimes: ['video/mp4'],
protocols: [2, 3, 5, 6],
minduration: 15,
maxduration: 30
}
},
bids: [
{
bidder: 'scalibur',
params: {
placementId: 'test-scl-placement'
}
}
]
}
];
First Party Data
The adapter supports First Party Data (FPD) in multiple ways:
- Global FPD: Automatically includes
pbjs.setConfig({ortb2: {...}})data - AdUnit FPD: Includes ad unit specific
ortb2Impdata - Local Storage: Generates and stores first-party identifiers for enhanced targeting
User Sync
The Scalibur adapter supports user synchronization through:
- Iframe syncs: For enhanced matching capabilities
- Image syncs: For lightweight synchronization
All privacy parameters are automatically included in sync requests.
Configuration Example
pbjs.que.push(function() {
pbjs.addAdUnits(adUnits);
pbjs.setConfig({
debug: true,
userSync: {
filterSettings: {
iframe: {
bidders: ['scalibur'],
filter: 'include'
},
image: {
bidders: ['scalibur'],
filter: 'include'
}
}
}
});
pbjs.requestBids({
timeout: 3000,
bidsBackHandler: function(bidResponses) {
// Handle bid responses
}
});
});
Support
For technical support or integration assistance:
- Email: support@scalibur.io
- Documentation: Contact Scalibur Support Team
Notes
- Video ads support instream context with standard IAB video parameters
- Banner ads support multiple sizes including standard IAB sizes
- All requests are sent via secure HTTPS endpoints
- The adapter automatically handles device detection and targeting
"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_scalibur |
hb_bidder_scalibur |
hb_adid_scalibur |
hb_size_scalibur |
hb_source_scalibur |
hb_format_scalibur |
hb_cache_host_scalib |
hb_cache_id_scalibur |
hb_uuid_scalibur |
hb_cache_path_scalib |
hb_deal_scalibur |