-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Prebid 5.0 #5966
Comments
In the pub committee meeting today, it was proposed that #5863 should need double opt in by publishers, where they would both have to install the module and configure it for it to work. This may already be the case with the post url, however, publishers were particularly alarmed about the possibility of inadvertantly activating some of this functionality. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@Fawke yes I believe so, but we'll be scheduling a follow up meeting in the next few weeks to list out 5.0 more explicitly. |
need to include #5986 |
#6464 obscure change that should affect no one but it seems technically breaking |
Regarding the Taxonomy Enforcement: do we already have a strict list of the required fields? Except the meta.advertiserDomain? |
That's the only one of the meta fields with an enforcement planned for 5.0 (and no additional ones have been suggested for 6.0). The other three enforcements are: bidders supporting floors should support the floor module as an input, bidders must bid, openrtb video params should be capable of reading from the ad unit. Bidders returning non-banner demand that declare as banner are strongly encouraged to set meta.mediaType but we're not sure how to enforce that. |
Plural, I'll do the docs change today
…On Tue, May 11, 2021, 9:56 AM Denis-Admixer ***@***.***> wrote:
Could you guys give us the correct version of the field name please?
Plural or singular? Also, it will be nice to fix the spec.
[image: image]
<https://user-images.githubusercontent.com/83413943/117827378-97a6a580-b279-11eb-837b-f96c82c81cde.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5966 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM25Z375LOOQNMJJVXA4ODTNEZR7ANCNFSM4TTV5MDQ>
.
|
I can't find the typo you mention at https://docs.prebid.org/dev-docs/bidder-adaptor.html |
It's here: https://prebid.org/blog/prebid-js-release-4-0/. |
Fixed in the blog post. |
5.0 released |
Type of issue
Prebid 5.0 changes summary.
Description
Prebid 5.0 is the next major version release of Prebid.js currently scheduled for Q2 of 2021. Please use this issue to track things earmarked for inclusion in Prebid 5.0 and to discuss what should or shouldn't be included.
Currently, we have the following projects and considerations:
Official Refactor of Default Key-values
Taxonomy Enforcement - adapters that do not conform to standards regarding the communication of the following auction meta data will be removed from the download page, and all adapter modifications and commits will be expected to respect these standards.
Adoption of the RTD framework
SharedID and pubcommonID
please feel free to comment and link to PRs for the various items above, additionally, these are all up for discussion and we should use this thread to answer any questions.
The text was updated successfully, but these errors were encountered: