Orbitsoft
Features
Bidder Code | orbitsoft | Prebid.org Member | no |
---|---|---|---|
Media Types | display | GDPR TCF Support | no |
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 | yes |
IAB GVL ID | check with bidder | Prebid Server Adapter | no |
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_orbitsoft |
hb_bidder_orbitsoft |
hb_adid_orbitsoft |
hb_size_orbitsoft |
hb_source_orbitsoft |
hb_format_orbitsoft |
hb_cache_host_orbits |
hb_cache_id_orbitsof |
hb_uuid_orbitsoft |
hb_cache_path_orbits |
hb_deal_orbitsoft |
Bid Params
Name | Scope | Description | Example | Type |
---|---|---|---|---|
placementId |
required | The placement ID (site channel ID) | 142 |
integer |
requestUrl |
required | Url to perform search request | 'http://adserver.com/ads/show/hb' |
string |
style |
optional | Creative styles. Actual only for text ads | string |
|
customParams |
optional | Permits passing any publisher key-value pairing into the bid request | {"macro_name": "macro_value" } |
object |
Example:
{
bidder: "orbitsoft",
params: {
placementId: 142,
requestUrl: "https://orbitsoft.com/php/ads/hb.php",
style: {
title: {
family: "Tahoma",
size: "medium",
weight: "normal",
style: "normal",
color: "0053F9"
},
description: {
family: "Tahoma",
size: "medium",
weight: "normal",
style: "normal",
color: "0053F9"
},
url: {
family: "Tahoma",
size: "medium",
weight: "normal",
style: "normal",
color: "0053F9"
},
colors: {
background: "ffffff",
border: "E0E0E0",
link: "5B99FE"
}
}
customParams: {
macro_name: "macro_value"
}
}
}