adops mobile outstream #5240
adops mobile outstream #5240
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
typo in adserver
|
FYI - going to review this recommendation with several Prebid committees |
|
|
||
| The 'outstream' format requires different ways of rendering for Prebid.js vs Mobile: | ||
|
|
||
| - For Prebid.js web integrations, outstream ads are rendered like banners. |
There was a problem hiding this comment.
This isn't accurate. To render outstream you can use the same tech used for instream. It seems that many publishers using Prebid.js don't have an outstream player and rely on HTML being delivered with a renderer, but this is not a requirement and we shouldn't state it as so. If a Publisher has an outstream player, you don't want to get HTML you just want a VAST tag or a VAST xml.
There was a problem hiding this comment.
To render outstream you can use the same tech used for instream.
I disagree. For instream and outsteam-in-mobile, the GAM setup requires a video line item with a VastUrl creative. For outstream-in-prebid.js, the GAM setup requires a display line item and the PUC or alternate.
So I'm willing to change "rendered like banners." to "set up in the ad server like banners." would that help?
There was a problem hiding this comment.
I don't understand why prebid.js needs outstream video to be setup as a display line item. Perhaps it would be easier to discuss tomorrow at the Video PMC meeting.
Technology wise, rendering an outstream video ad is the same as rendering an instream video ad, given a video player that supports both instream and outstream video ads. So i'm confused why GAM would need it to be setup as a display line item.
There was a problem hiding this comment.
I admit I haven't spent much time with GAM and line items. Does GAM not treat outstream as video by definition?
| not render properly. | ||
|
|
||
| Prebid's recommendation is to | ||
| consider setting up outstream adunits as slightly different sizes. |
There was a problem hiding this comment.
Should this recommendation not apply for publishers who have a player capable of rendering outstream ?
There was a problem hiding this comment.
If they're using outstream, they've defined a renderer that can play VAST. But the problem is in the ad server line item setup.
|
|
||
| One decision you'll want to make is which version of the PUC you want to use. Prebid hosts a copy, which you're free to use. But some publishers might want to use their own copy of the PUC so as to have greater control over the upgrade windows. | ||
| 1. Call the [Prebid Universal Creative](/overview/prebid-universal-creative.html) to display the correct image. This also applies to outstream for Prebid.js, though outstream for Mobile requires a video creative. |
There was a problem hiding this comment.
Why is the PUC the preferred way of rendering outstream ?
There was a problem hiding this comment.
Seems like a lot of these problems would go away if the PUC just rendered VAST tags
There was a problem hiding this comment.
The PUC will never be an outstream renderer. There are dozens (hundreds?) of outstream renderers out there and Prebid gives publishers the choice of which one to use in which scenario.
| - Instream video is normally created as a separate set of line items because they are usually priced higher than other formats, often requiring custom price granularity. | ||
| - Outstream video needs to run with a set of line items that will support appropriate rendering. For Prebid.js, outstream is delivered along with banner, while for Prebid Mobile, outstream goes with instream video. |
There was a problem hiding this comment.
Does Prebid Mobile have a player capable of parsing vast tags ? That's all you need for outstream in a browser, it shouldn't have to be delivered with banner
There was a problem hiding this comment.
Prebid SDK uses the google sdk to render outstream. It, in turn, requires that the GAM creative be directly VAST, which conflicts with how rendering needs to happen in Prebid.js
| Note that running "outstream" video ads requires special attention if you're a publisher | ||
| that utilizes both Prebid.js and Prebid Mobile. See the [planning guide note](/adops/adops-planning-guide.html#rendering-mobile-outstream-ads) for more background. |
There was a problem hiding this comment.
not if you have a player that can play outstream. Maybe the right thing is to force publishers to use a valid outstream player; it could reduce complexity.
There was a problem hiding this comment.
I think you may be missing the root problem here -- it's that GAM gets confused and serves the wrong line item unless there's special targeting or we use the size hack.
|
Appreciate the thorough review @karimMourra . Perhaps we can cover in tomorrow's PMC? |
|
Update: looks like this approach will be canceled. Keeping it open for a little longer. |
See https://docs.google.com/document/d/1kTqgRPvWI111_oDBkCbmvdBG3nqfJLM5WcryT64j-sE/edit for background