Closed bszekely1 closed 4 years ago
Hi. I am currently working on a video based app with ads and came across prebid.org and then here. I am currently using ima ads and from what i know prebid is a way to make bidding possible for every consecutive ad. I was thinking of using prebid, but from this issue, i am guessing that using prebid for bidding of runtime vast ads is currently not possible. Is this the case?
If so, i would like to mention a few things and make some requests. Please make this library flexible enough to allow usage of other video players and vast handlers. VideoView and Mediaplayer in android are very outdated method for playing videos, so please give us the flexiblity to use other players.
Similarly many people these days are not using Ima sdk or handling most of the components of Ima sdk by themselves, so it would be difficult if the core components of IMA are tightly coupled with this library.
That's all , Thank you very much for reading this and making this awesome library!
Hi Ansh, we are always welcome to feedback. This is our initial iteration of many into our video integration via Prebid SDK. Additionally this is the fist time we as in Prebid are providing a video renderer (i.e. video player) to facilitate easier integrations into video, especially for publishers who do not have video inventory.
I will reach out to you privately to discuss your feedback.
Type of issue
Intent to implement
Description
The goal of this intent to implement is to provide video format support to the Prebid SDK product. The initial build is intended to integrate into Google Ad Manager (GAM) as GAM provides an easy VAST API (via the Mobile Ads SDK) for processing and handling VAST ads. Future iterations may include other ad servers or rendering without an ad server for publishers who do not have a direct sales team that don't require an ad server.
SDK Public API
This section will cover the public facing API in the SDK to set video specific features:
Ad Unit types:
Outstream
Impression Config ID
player size in DIPS (w, h)
placement type
Interstitial
Impression Config ID
player size in DIPS (w,h)
Event listener callbacks:
AdLoadSuccess
AdLoadFail
Note: The default player behavior will be autoplay sound off, non-skippable in the first iteration. The next iteration will include the option for publishers to define these fields in the stored request, where PBS will echo back to the SDK for the device player to signal on playback method and skippability. Both fields will be set by a private field.
Video Player
VAST handler:
The media player will default to autoplay on, sound off, with a UI feature for the user to enable sounds as they wish.
The supported video attributes intrinsic to the video player are defined by the limitations for the respective video player of each platform. The statically defined video attributes and values from the SDK to Prebid Server are below:
Stored Requests
The following video fields will be entered in the stored request specific to video:
Ad Server Integration
Prebid SDK will make a request for a VAST ad using the Google IMA SDK, triggering a VAST Prebid Line item as a standard Prebid video integration
Fields for the GAM API
Prebid SDK <> Prebid Server
This section will cover communication between Prebid SDK and Prebid Server. Since the video solution for Prebid SDK will provide the
Request
Outstream
Insterstial The main differences between the standard outstream and interstitial is the interstial flag in each bid object.
Response
Platform details
Support for Android
Other information
Video supported will be broken out into a new module in the build process for the SDK defined in the modularization issue 239.