Telaria
Features
Bidder Code | telaria | 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 | Safeframes OK | check with bidder |
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 |
"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_telaria |
hb_bidder_telaria |
hb_adid_telaria |
hb_size_telaria |
hb_source_telaria |
hb_format_telaria |
hb_cache_host_telari |
hb_cache_id_telaria |
hb_uuid_telaria |
hb_cache_path_telari |
hb_deal_telaria |
Overview
This documentation covers some of the parameters that the Telaria (previously Tremor Video)
exchange accepts. And is intended to be referenced by publishers using prebid 1.x. Documentation for prebid 0.x can be found under tremor
Bid Params
Please refer to the Tag Parameters section in the Telaria Console
Example Ad Unit
var adUnit = {
"code": "video1",
"mediaTypes": {
"video": {
"playerSize": [640, 480],
"context": "instream"
}
},
"bids": [{
"bidder": "telaria",
"params": {
"supplyCode": "ssp-demo-rm6rh",
"adCode": "ssp-!demo!-lufip",
"videoId": "MyCoolVideo"
}
}]
}
Supply Chain Object:
// There are two ways of passing the SupplyChain Object to our adapter:
// 1) set it in the config
pbjs.setConfig({
"schain": {
"ver":"1.0",
"complete": 1,
"nodes": [
{
"asi":"indirectseller.com",
"sid":"00001",
"hp":1
}
]
}
});
// 2) pass it in the params object of the adunit:
var adUnit = {
"code": "video1",
"mediaTypes": {
"video": {
"playerSize": [640, 480],
"context": "instream"
}
},
"bids": [{
"bidder": "telaria",
"params": {
"supplyCode": "ssp-demo-rm6rh",
"adCode": "ssp-!demo!-lufip",
"videoId": "MyCoolVideo"
}
}]
}
Delivery
1
: In-Stream: Played before, during or after the streaming video content that the consumer has requested (e.g., Pre-roll, Mid-roll, Post-roll).2
: In-Banner: Exists within a web banner that leverages the banner space to deliver a video experience as opposed to another static or rich media format. The format relies on the existence of display ad inventory on the page for its delivery.3
: In-Article: Loads and plays dynamically between paragraphs of editorial content; existing as a standalone branded message.4
: In-Feed: Found in content, social, or product feeds.5
: Interstitial/Slider/Floating: Covers the entire or a portion of screen area, but is always on screen while displayed (i.e. cannot be scrolled out of view). Note that a full-screen interstitial (e.g., in mobile) can be distinguished from a floating/slider unit by the imp.instl field.
Placement
1
: Streaming2
: Progressive3
: Download
Supply Chain Object
The adapter has been enhanced to accept the supply chain object (schain) if provided. Please refer to SupplyChain for Non RTB Requests for more information