Skip to content

Commit

Permalink
in-renderer integration (formerly: outstream) updates
Browse files Browse the repository at this point in the history
  • Loading branch information
IrinLen committed Oct 1, 2024
1 parent cb31724 commit a34b773
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions prebid-video/video-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -68,29 +68,29 @@ The video player loads the master video ad server tag URL, which makes a call to
b. The Prebid.js video creative returns a VAST XML document containing the cached video bid, which was returned by the Prebid demand partner in its bid response.
c. The demand partner’s VAST tag URL is rendered in the video player.

### Outstream Video
### In-renderer Integration

Outstream video is displayed in banner ad slots using video renderers that are provided either by the demand partner with the bid response or by a renderer that the publisher has associated with the ad unit. This is a high-level diagram showing how header bidding works with outstream video:
In-renderer integration (formerly known as “outstream”) implies that a video ad is displayed using video renderers that are provided either by the demand partner with the bid response or by a [renderer](https://docs.prebid.org/overview/glossary.html#renderer) that the publisher has associated with the ad unit. This is a high-level diagram showing how header bidding works with this type of integration:

![Outstream Video Diagram]({{site.baseurl}}/assets/images/prebid-video/outstream-video.png){: .pb-img.pb-lg-img :}
![In-renderer Integration Diagram]({{site.baseurl}}/assets/images/prebid-video/outstream-video.png){: .pb-img.pb-lg-img :}

1. **Prebid sends request to demand partners.**
Prebid.js code loads within the page header and sends a bid request to each video demand partner included on a given Prebid video ad unit.

2. **Demand partners respond.**
Demand partners respond with their respective bids, which may contain a video renderer. (Publishers are encouraged to associate their own video renderer with each outstream video ad unit to include video demand that was not returned with its own renderer.)
Demand partners respond with their respective bids, which may contain a video renderer. (Publishers are encouraged to associate their own video renderer with each video ad unit to include video demand that was not returned with its own renderer.)

3. **Prebid.js may cache video bids.**
If the configuration is set up, video bids are cached server-side and mapped to a unique cache ID. This may be used at render time. See [Notes on Prebid Cache](/dev-docs/show-video-with-a-dfp-video-tag.html#notes-on-prebid-cache) for details.

4. **Prebid passes key-value targeting to ad server.**
Prebid assigns a unique hb_adid to each video bid/renderer combination, and passes this ID to the ad server via key-value targeting (along with other standard Prebid key-value pairs). This ad ID serves the same role for outstream video ad units as it does for banner ad units.
Prebid assigns a unique hb_adid to each video bid/renderer combination, and passes this ID to the ad server via key-value targeting (along with other standard Prebid key-value pairs). This ad ID serves the same role for [standalone/no-content video ad units](https://docs.prebid.org/formats/video.html) as it does for banner ad units.

5. **Ad server chooses winning line item.**
The ad server chooses the winning line item. If a Prebid line item is selected, the Prebid creative is returned. The creative can be the standard call to `renderAd` or the Universal Creative.

6. **Prebid renders the outstream video.**
Prebid retrieves the winning outstream video bid and renderer from the ad ID (hb_adid). Prebid renders the outstream video into the banner slot. It is up to the rendering code to retrieve the VAST, which may have been returned fully-formed to the browser, or it may be just a URL where the VAST is cached that the renderer has to load.
6. **Prebid renders the video.**
Prebid retrieves the winning video bid and renderer from the ad ID (hb_adid). Prebid then places the renderer into the ad slot. It is up to the rendering code to retrieve the VAST, which may have been returned fully-formed to the browser, or it may be just a URL where the VAST is cached that the renderer has to load.

### Long-form Video

Expand Down

0 comments on commit a34b773

Please sign in to comment.