Video SSP Prebid.js adaptor Implementation Guide for Publishers

 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

Implementation Details

  1. 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.)
  2. Use the Prebid guide to setup the Prebid integration.
  3. 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 whitelisted in that inventory source.
  4. Add the “oneVideo” line in the ads.txt of all these domains
  5. Configure “oneVideo” adaptor ad unit using the following parameters:

 

Name

Description

Required

Example/Supported Values

playerWidth

Width of the player in pixels

Yes

640

playerHeight

Height of the player in pixels

Yes

480

mimes

Content MIME types supported by the player

Yes

['video/mp4', 'application/javascript']

protocols

version 3.6 and up

Supported VAST response versions

Yes

[1]  //VAST 1.0

[2] //VAST 2.0

[3] //VAST 3.0

[4] //VAST 1.0 Wrapper

[5] //VAST 2.0 Wrapper

[6] //VAST 3.0 Wrapper

api

List of API frameworks supported by the publisher

No

[1] //VPAID 1.0

[2] //VPAID 2.0

[3] //MRAID 1.0

[4] //ORMMA

[5] //MRAID 2.0

[6] OM SDK

delivery

Type of content delivery:

1 = Streaming

2 = Progressive

No

[2]

Id 

Identification number of the site

No

12345

page

Full url of the page on which adunit is being served

No

http://abc.com/xyz

pubId

Publisher ID of the publisher provided by Video SSP

Yes

mypub

bidfloor

Floor price ($)  for the configured Ad Unit

No

12

playbackmethod

Playback method supported by the Ad unit

No

[1] //Initiates on Page Load with Sound On

[2] //Initiates on Page Load with Sound Off by Default

[3] //Initiates on Click with Sound On

[4] //Initiates on Mouse-Over with Sound On

[5] //Initiates on Entering Viewport with Sound On

[6] //Initiates on Entering Viewport with Sound Off by Default

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 //In-stream

2 //Out-stream

//In-article

//In-feed

5 //Interstitial/Slider/Floating

position

Ad unit position on the screen (Refer to Table 4)

No

1 //Unknown

2 //Above the fold

3 //Below the fold

4 //Header

5 //Footer

6 //Sidebar

7 //Fullscreen

rewarded

Is the inventory a Rewarded Video
0 = No
1 = Yes

No

0,1

sid

Seller ID (Org ID) to pass Supply Chain information to buyers

No

87654

 

Example Configuration

 

var adUnits = [{
  code: 'video1',
  sizes: [640, 480],
  mediaTypes: {
    video: {
      context: "instream"
    }
  },
  bids: [{
    bidder: 'oneVideo',
    params: {
        bidfloor: 10
      video: {
        playerWidth: 640,
        playerHeight: 480,
        mimes: ['video/mp4', 'application/javascript'],
        protocols: [2, 5],
        api: [2],
        delivery: [2],
        playbackmethod: [1, 5],
        placement: 1,
        inventoryid: 34567,
        position: 1,
        rewarded: 1,
        sid: 87654
      },
      site: {
        id: 1,
        page: 'http://abhi12345.com’
      },
      pubId: 'mypub'
    }
  }]
}];

6. Inform your Video SSP partner manager when the configuration is complete

 

Have more questions? Submit a request