Recommended fields to send for outstream video inventory in OpenRTB bid requests
For better monetization of your outstream video inventory, we strongly recommend that you pass as many fields as possible to describe your inventory. Outstream inventory could include accompanying content Pre-roll, mid-roll, and post-roll ads that are played before, during, or after streaming video content.It starts playback upon entering the viewport. It may convert to a floating/sticky player as it scrolls off the page., interstitial A ad that covers the entire screen of the device/host app., or no content/standalone Video ads that are played without streaming video content. This can be in placements like slideshows, native feeds, in-content or sticky/floating. content. We have included a list of recommended fields that you can pass in the bid request An OpenRTB request that is sent from a supply-side platform (SSP) or ad exchange to the DSP requesting a bid response for potential impressions. A bid request contains information about the impression that allows the DSP to decide whether to bid on the impression. Video object.
Recommended fields | Type | Description |
---|---|---|
|
Integer; optional |
The video's placement type according to the IAB Digital Video Guidelines. For more information about the recommended Note: If you send both the |
|
String array; required |
List of supported content MIME types, where we recommend that you send the following:
|
|
Integer array; optional |
For VPAID ads, you must specify the supported api framework, where we recommend that you send one of the following:
If your video ad unit supports OMID 1.0, which is Open Measurement for Web Video, we recommend that you send the following:
|
|
Integer; required |
The minimum video ad duration in seconds. We recommend that you decrease the duration by one second to allow for any VAST Video ad-serving template (VAST). A communication standard between ad servers and video players in XML-format that describes the video player's expected behavior. encoding nuances. Example: For a minimum 6 seconds video ad duration, you can specify the |
|
Integer; required |
The maximum video ad duration in seconds. We recommend that you increase the duration by one second to allow for any VAST encoding nuances. Example: For a 30 seconds maximum video ad duration, you can specify the |
|
Integer array; required |
An array of supported video protocols, where we recommend that you send the following:
|
|
Integer; optional |
The minimum bit rate in Kbps. We recommend a minimum bit rate of 300 Kbps. |
|
Integer; optional |
The maximum bit rate in Kbps. We recommend a maximum bit rate of 30,000 Kbps. |
|
Integer array; optional |
A list of allowed playback methods, where we recommend that you send the following:
This also provides a better user experience. |
|
Integer array; optional |
A list of supported delivery methods, where we recommend that you send one or more of the following:
|
|
Integer; optional |
Specifies whether the ad impression is linear or non-linear, where we recommend that you send the following:
Sending this makes sure that the response you receive is a VAST message containing video assets. |
|
Integer; optional |
Specifies the position of the ad as a relative measure of visibility or prominence, where:
|