Skip to content

Standardize Video Bidder Params #11095

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

Closed
fowler446 opened this issue Feb 14, 2024 · 7 comments
Closed

Standardize Video Bidder Params #11095

fowler446 opened this issue Feb 14, 2024 · 7 comments

Comments

@fowler446
Copy link
Collaborator

fowler446 commented Feb 14, 2024

Type of issue

feature request

Description

Many SSPs expect different parameters when it comes to the video mediaTypes object. It would be great to do a sweep and standardize which fields are passed/required. I'm making this issue as a placeholder where we can aggregate these differences in SSPs. Maybe Prebid 9.0 would be a good place to enforce something like this. If we were using typescript we could enforce a video object type. I'm not sure the best way to enforce this otherwise.

There's also a wide variety in the video documentation that bidders supply. A standardization sweep would go a long way here.

@patmmccann
Copy link
Collaborator

related: #10452

@fowler446
Copy link
Collaborator Author

@patmmccann patmmccann moved this from Triage to Blocked in Prebid.js Tactical Issues table Feb 26, 2024
@patmmccann
Copy link
Collaborator

I know we plan to disallow requiring deprecated fields but should we also require that those passing the deprecated field also pass the updated field?

@fowler446
Copy link
Collaborator Author

I know we plan to disallow requiring deprecated fields but should we also require that those passing the deprecated field also pass the updated field?

@patmmccann for sure we should be requiring the new plcmt field.

@fowler446
Copy link
Collaborator Author

33across requires the old placement field but only supports placement values 1, 2, 3, 4....

@fowler446
Copy link
Collaborator Author

Closed this issue in favour of moving the discussion here: #9988

I think it would be good for us to ditch playerSize all together and move towards the openRTB standard of w and h.

@patmmccann
Copy link
Collaborator

@fowler446 did you mean to close this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants