-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Video Support for Prebid Server #1487
Comments
That part of the doc is very outdated. Prebid Server supports video. Are you looking for outstream or instream using SSAIs? |
Ah gotcha. We are looking to support both instream and outstream. Is that possible in Prebid Server? |
Sure is! Outstream auctions are run through the Instream auctions are done through a specialized endpoint designed for SSAI integration. Take a look at this doc: https://docs.prebid.org/prebid-server/use-cases/pbs-lfv.html |
Great! Thanks for the links. I see that the doc linked to instream actually discusses long form video. Does that mean that instream is considered the same as long form? I ask since Prebid.js treats the two as separate? Also, I should have clarified...we are a bidder (33Across) looking to add video support to our adapter. I am guessing as far as the adapter is concerned support for instream vs outstream is not different and it only entails setting the right ORTB? |
"Short form" (e.g. pre-roll) instream video is supported by the /openrtb2/auction endpoint as described in the 2nd diagram here -- https://docs.prebid.org/prebid-server/use-cases/pbs-pbjs.html The "long form" video support is about ad pods. Thanks for pointing out the old doc -- will get that updated. |
Doc updated. Can we close this @curlyblueeagle ? |
Yes you may close this. Thank you. |
Hello, I am seeing contradictory docs about support for video. According to this page https://docs.prebid.org/formats/video.html only Prebid.js supports video and not Prebid Server. Can someone please confirm that Prebid Server does support video?
The text was updated successfully, but these errors were encountered: