Show Outstream Video Ads
Unlike instream video ads, which require you to have your own video inventory, Outstream video ads can be shown on any web page, even pages that only have text content.
This page has information you’ll need to set up Prebid.js to show outstream video.
Other than using a slightly different ad unit in your Prebid code on the page, you shouldn’t have to make any major engineering changes from a standard Prebid setup.
There should be no changes required on the ad ops side, since the outstream units use the standard Prebid creative, line item targeting setup, etc.
- Step 1: Set up ad units with the video media type and outstream context
- Step 2: Show ads in the page body
- Working Examples
- Inclusion of at least one demand adapter that supports the
Step 1: Set up ad units with the video media type and outstream context
adUnit.mediaTypes object to set up your ad units with the
video media type and assign the appropriate context
The fields supported in a given
bid.params.video object will vary based on the rendering options supported by each bidder. For more information, see Bidders’ Params.
To display an outstream video, two things are needed:
- A VAST URL or VAST XML document, provided by the Prebid video demand partner.
- A Client-side player environment capable of playing a VAST creative. We will refer to this as the
Prebid.js will select the
renderer used to display the outstream video in the following way:
- If a
rendereris associated with the Prebid adUnit, it will be used to display any outstream demand associated with that adUnit. Below, we will provide an example of an adUnit with an associated
- If no
rendereris specified on the Prebid adUnit, Prebid will invoke the renderer associated with the winning (or selected) demand partner video bid.
At this time, since not all demand partners return a renderer with their video bid responses, we recommend that publishers associate a
renderer with their Prebid video adUnits, if possible. By doing so, any Prebid adapter that supports video will be able to provide demand for a given outstream slot.
Renderers are associated with adUnits through the
adUnit.renderer object. This object contains two fields:
url– Points to a file containing the renderer script.
render– A function that tells Prebid.js how to invoke the renderer script.
Some demand partners that return a renderer with their video bid responses may support renderer configuration with the
adUnit.renderer.options object. These configurations are bidder specific and may include options for skippability, player size, and ad text, for example. An example renderer configuration follows:
For more technical information about renderers, see the pull request adding the ‘Renderer’ type
Step 2: Show ads in the page body
Option 1: Serving through a primary ad server
Invoke your ad server for the outstream adUnit from the body of the page in the same way that you would for a display adUnit
For a live example, see Outstream with DFP.
Option 2: Serving without an ad server
Prebid can serve outstream demand directly without going through a primary ad server.
For a live example, see Outstream without an Ad Server.
In the Prebid.js event queue, you’ll need to add a function that:
- Adds your video ad units
- Requests bids, adding a callback that:
- Selects the bid that will serve for the appropriate adUnit
- Renders the ad
For more information, see the API documentation for:
Below, find links to end-to-end “working examples” demonstrating Prebid Outstream: