Skip to content
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.

Sign up for GitHub

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

4.0 changes to video params #2158

Merged
merged 1 commit into from
Jul 29, 2020
Merged

4.0 changes to video params #2158

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion dev-docs/bidder-adaptor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -562,7 +562,24 @@ If your adapter supports banner and video media types, make sure to include `'ba

### Step 2: Accept video parameters and pass them to your server

Video parameters are often passed in from the ad unit in a `video` object.
Video parameters are often passed in from the ad unit in a `video` object. As of Prebid 4.0 the following paramters should be read from the ad unit when available; bidders can accept overrides of the ad unit on their bidder configuration parameters but should read from the ad unit configuration when their bidder parameters are not set. Parameters one should expect on the ad unit include:

| parameter |
|-|
| mimes |
| minduration |
| maxduration |
| protocols |
| startdelay |
| placement |
| skip |
| skipafter |
| minbitrate |
| maxbitrate |
| delivery |
| playbackmethod |
| api |
| linearity |

The design of these parameters may vary depending on what your server-side bidder accepts. If possible, we recommend using the video parameters in the [OpenRTB specification](https://iabtechlab.com/specifications-guidelines/openrtb/).

Expand Down