-
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 7: Freestar Bid Adapter initial release & Deprecate Sortable Bid Adapter #8263
Conversation
…reestar sans Native/Video
@nicgallardo - you can remove sortable from the docs, but it's considered a breaking change to remove it from the code repo. Please restore the .js files and explain in the .md files that the sortable bidder and analytics adapter are deprecated. You can remove them formally in PBJS 7.0, which is next month! |
@bretg I am attempting to merge our branch to the |
Thanks Nic. Adding @dgirardi for guidance on how to get this change into 7, and @patmmccann to consider for the release notes (remove sortable bid and analytics adapters) |
This PR looks correct for getting this into 7; you will need to post a separate PR if you also want it in 6 - I suggest waiting until this gets approved. |
tagging #7796 for linkage, thanks! |
)) | ||
const isBanner = !bid.mediaTypes || bid.mediaTypes[BANNER]; | ||
const bannerSizes = isBanner ? deepAccess(bid, `mediaType.${BANNER}.sizes`) || bid.sizes : null; | ||
return !!(bid.params.tagId && haveSiteId && validFloor && validKeywords && (!isBanner || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you really rejecting biid requests if the keywords are invalid? why not just drop the keywords
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we are validating just as we did in the SortableBidAdapter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this validation is quite aggressive, doesnt seem best for your company or your publisher partners
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also why not fallback to no floor when the floor is invalid?
if (floor) { | ||
rv.floor = floor; | ||
} | ||
if (bid.params.keywords) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please support reading keywords from ortb2 object
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use the keywords in our param a bit differently than the ortb2 documentation.
We can support keywords as the spec states in the future. However, we do not have it on our roadmap at this moment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you have to fix or delete support for keywords
@nicgallardo looks good, just two requested changes with respect to keywords |
Type of change
Description of change
Accompanying Documentation
Other information