Overview
Prebid.js is an open-source solution for the implementation of header bidding by the publishers. The Video SSP’s Prebid.js adaptor will allow a publisher to integrate the Video SSP as a demand partner to help them improve their yield.
This document will help guide you to set up the integration of the Video SSP Adaptor in a prebid.js header bidding container
Prerequisites
- The publisher needs to create a Video SSP Account and get a publisher ID.
- The publisher should be using a supported version of Prebid.js
Optional
Especially for DAP integrations - Publishers have the option to add their own video content within the video player so long as they provide the content file or a content feed that will play after the video pre-roll ad when served. At a minimum, a static image is required and acceptable.
Implementation Details
- Download the prebid.js code with oneVideo adaptor selected. (Note: The Video SSP is still referred to as “oneVideo” in all Prebid documentation. We will update this in a future date.)
- Use the Prebid guide to setup the Prebid integration.
- Provide your Video SSP partner manager with the list of domains being sent through the oneVideo Adaptor. Your partner manager will help create an RTB inventory source with these domains allowlisted in that inventory source.
- Add the “oneVideo” line in the ads.txt of all these domains
- Configure “oneVideo” adaptor ad unit using the following parameters:
|
Name |
Description |
Required |
Example |
|
playerWidth |
Width of the player in pixels |
Yes |
250 |
|
playerHeight |
Height of the player in pixels |
Yes |
300 |
|
mimes |
Content MIME types supported by the player |
Yes |
["*/*"] |
|
Id |
Identification number of the site |
No |
12345 |
|
page |
Full url of the page on which adunit is being served |
Yes |
http://abc.com/xyz |
|
pubId |
Publisher ID of the publisher provided by Video SSP |
Yes |
mypub |
|
position |
Ad unit position on the screen (Refer to Table 4) |
No |
1 |
|
sid |
Seller ID (Org ID) to pass Supply Chain information to buyers |
No |
87654 |
|
hp |
Indicates whether this node will be involved in the flow of payment for the inventory. Considered only if sid id passed |
No |
1 |
|
display |
Is the inventory 300X250 MREC 1 = Yes |
Yes |
1 |
|
inventoryid version 2.39 and up, for previous versions, use placement param for this purpose |
ID of the RTB Inventory source setup in Video SSP platform for this ad unit |
No |
34567 |
|
placement version 2.39 and up, for previous versions, use as instructed for inventoryid |
Placement Type for the impression |
No |
1,2,3,4,5 |
|
bidfloor |
Floor price ($) for the configured Ad Unit |
No |
12 |
Example Configuration
var adUnits = [{
code: 'video1',
sizes: [300, 250],
mediaTypes: {
video: {
context: "instream"
}
},
bids: [{
bidder: 'oneVideo',
params: {
bidfloor: 10
video: {
playerWidth: 250,
playerHeight: 300,
mimes:["*/*"],
position: 1,
display: 1,
inventoryid: 12345,
placement: 1,
sid: 9876,
hp: 1
},
site: {
id: 1,
page:'http://abhi12345.com'
},
pubId: 'mypub'
}
}]
}];
6. Inform your Video SSP partner manager when the configuration is complete
Appendix
Table 1: Placement
|
Value |
Description |
|
1 |
In-Stream |
|
2 |
In-Banner |
|
3 |
In-Article |
|
4 |
In-Feed |
|
5 |
Interstitial/Slider/Floating |