Video signaling

[bszekely1]

Type of issue

In the original implementation of video support for Prebid SDK, several video specific fields were either hardcoded or assumed to be set in the Prebid Server DB as a Stored Request. The intent of this ticket is to allow for more dynamic flexibility of providing signaling either from the SDK itself or the Prebid DB or both.

Goals

• Expose statically defined video fields in the Prebid SDK API
• Pass video specific fields to PBS

Proposed Design

The design is to provide OpenRTB signals to the prebid SDK API. Below are the following signals that should be supported as methods for outsream, interstitial and rewarded:

• Mimes
  • array of strings
• Protocols
  • type array of integers
• Playbackmethod
  • array of one integer
• API Frameworks
  • array of integers
• maxbitriate
  • integer
• maxduration
  • integer
• minbitrate
  • integer
• minduration
  • integer
• startdelay
  • integer

In-Scope

Out of Scope

Prebid SDK Changes

New methods for all video ad unit types

Prebid Server OpenRTB Changes

"video": {
            "api": [1, 2],
            "maxbitrate": 1500, 
            "maxduration": 30, 
            "mimes": ["video/x-flv", "video/mp4"], 
            "minbitrate": 300, 
            "minduration": 5, 
            "playbackmethod": [1, 3], 
            "protocols": [2, 3], 
            "startdelay": 0, 
            "w": 640,
            "h": 480 
        }

Prebid Server Changes

Prebid Server will simply be a passthrough. No changes to PBS behavior should be required for these fields.

Other information