Ad Podding Support into /auction endpoint

[ccorbo]

Introduction

This issue intends to start the conversation around the work needed to port the functionality of the /openrtb2/video auction endpoint into the /openrtb2/auction endpoint. This includes adding support for OpenRTB 2.6 ad podding support into the /openrtb2/auction endpoint on Prebid Server. Ad podding is currently supported in the /openrtb2/video endpoint, but the /openrtb2/video endpoint is due to be deprecated, therefore it is needed to port the necessary changes over to the /auction endpoint.

These changes can not be made until PBS supports OpenRTB 2.6.

Points to consider:

Below is a few things we've identified that needs to be discussed / included into the /auction endpoint to support long form video. Would like to get the communities thoughts on the below high level changes / anything else that needs to be added.

Bidder Level OpenRTB 2.6 supported config:

There needs to be bidder level config that shows a bidder supports OpenRTB 2.6. This may be included in the already existing 2.6 migration work that is already taking place. This is to indicate when down versioning is needed.

Down-Version support:

Currently in the video endpoint, every podded requests are created into a multi imp request via the createImpressions function (linked below). This creates a multi-imp request out of a podded request, this function can be leveraged in its current state to downgrade dynamic ad podded requests into multi-imp requests for bidders that do not support OpenRTB 2.6 requests.

https://github.com/prebid/prebid-server/blob/master/endpoints/openrtb2/video_auction.go#L396

Bidders that support OpenRTB 2.6 requests, will not need to have their ad podded requests down versioned into multi imp requests.

What should be returned in the case of long-form video requests?

Currently in the /video endpoint the POST response contains an array of adPod objects, which contains key-value targeting. While in the /auction endpoint, standard OpenRTB bid response is returned. How should this be reconciled?

[hhhjort]

The work towards handling adapters that do/do not support OpenRTB 2.6 has started with #2540 . This has nothing video specific, but is the starting point in up/downgrading the request sent to the bidder according to their level of support in general.

[SyntaxNode]

I've opened a (currently draft) PRD: https://docs.google.com/document/d/12uYdNOlcdQE2LPjdvSTHk0AEXUAE34PGFXtOAC3MtAY/edit?usp=sharing

[bretg]

The committee has approved this document as ready-for-dev.