OpenRTB 2.5 - Outstream/Inbanner Video Support

[Sam Nunez]

Hello, I am putting some thoughts together for better signaling Outstream & in-banner videos via the bid request. 

I am thinking of 2 new flags and one modif:

A new attribute in the video object indicating the type of video, with the values:

• In-stream
• In-text Video (ad-only video that sits within the main reading area of the page, without overlaying textual content)
• In-banner Video (fix location on page, typically next to the main textual content)
• Other Outstream (interstitial or slider)

A second attribute to indicate when the video starts and end:

• Video starts when in view, pause when out of view
• Video starts when in view, and stays in view until ended or closed
• Video may start out of view

And extending imp.instl to include the "slider" case:

• 0: Not interstitial and does not cover content
• 1 Full screen until ended or closed
• 2 Slider: Ad covers other content partially, but stays in view until ended or closed

I believe between this 3, it will cover all the outstream case offers by us (PulsePoint) and other major Outstream vendros.

Any thoughts?

[Tom H]

My apologies, I don't have the ability to post much at the moment, but I understand some DSPs are currently setting up different endpoints to differentiate between in-stream and oustream video. That is not the correct way to solve that problem, so wanted to make sure, as a group, we're thinking about these things.

[Sam]

Correct! currently, we are asking SSPs to use different points when they cannot send us an outstream flag in the bid request.... otherwise we ingest custom flags (we recommend the Teads ext approach, but some SSPs have their own flavor).... pretty messy....

On Sat, Jun 18, 2016 at 4:55 PM, Tom H <tom.h...@centro.net> wrote:

My apologies, I don't have the ability to post much at the moment, but I understand some DSPs are currently setting up different endpoints to differentiate between in-stream and oustream video. That is not the correct way to solve that problem, so wanted to make sure, as a group, we're thinking about these things.

--
You received this message because you are subscribed to a topic in the Google Groups "openrtb-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openrtb-dev/aOOhqeLqXfM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openrtb-dev...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ian Trider]

All, FYI:

Here is the current state of the Outstream proposal from the (somewhat stalled) subgroup on this topic:

https://docs.google.com/document/d/11hTIMSTB8QMlD3YYHqXvy-rAWo6uyOb3Pf6YWfUrT34/edit?usp=sharing

The conversations tend to break down when it comes to how to actually classify things, so buy-side feedback is definitely welcome.

[Daniela]

Hi Ian,

a feedback that I got from our video team: why not having only 2 values for the "video placement type"

1. in-stream

2. in-display

and then have an additional table for the different in-display creatives type (in-banner, in-feed, ...), a bit like we manage startdelay for in-stream? 

It seems that for some publishers having the possibility to specify in-display (plus the player size) would be enough to monetize and report on the in-display inventory. Unless the in-banner/in-feed, etc... label makes a big difference on buyer side (cosidering the way they can target in-display video inventory on the DSPs' platforms)?

A second feedback that I got is about the placement type 5 in your table 5.20 - Interstitial/Slider/Floating: it isn't clear how the creative types are grouped here, is this for rich media in general?

Thanks a lot for the massive work on this!

Kindest,

Daniela

[Ian Trider]

It works for me if it pleases the others.

for placement type 5, what if we drop the word interstitial? They might resolve the confusion.  It's for formats like q1Media's vSlider or ConvertMedia's Interstitial (which could be described as floating adequately, IMO):

http://demo.q1media.com/demo/index.php?url=http://gotchamovies.com&unit=vslider&zone=1

http://studio.convertmedia.com/#/studio/preview/interstitial/new/templates/withClose

[Daniela]

Hi Ian,

I think we need more feedback on the DSPs' side regarding how buyers are supposed to target in-stream vs in-display formats. It might help also having a look at those DSPs/SSPs which already use an ext to manage in-display. In Europe, we asked our main buyers and they want the opportunity to bid on outstream (as a whole) as opposed to just the specific formats.

Regarding placement type 5, I see what you mean, but not sure what can be a placement type name for those kind of formats...high impact?

Kindest,

Daniela 

[Ido Guterman]

Hi ,

Two additions we had to Expanded Table - 5.9 Playback Methods

1. Initiates on page load with sound on hover
   
2. Initiates on entering viewport, with sound on hover

Ido.

[Ian Trider]

Daniela -- you are right in that currently signalling is limited to instream vs. outstream.  That said, I believe Melissa shopped the proposal out to a couple of major DSPs and the feedback was positive.  In any event, can more granularity really hurt? That said, I personally don't have any objection to two fields; one for instream vs. outstream and one for type of outstream, if others want the same.

Ido -- Fair point, and these presumably cover the majority of actual cases.  I'll add it in.