-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Updated docs for Vidoomy blocking supported #4493
Conversation
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
@nimasrn - please clarify this support. The requirement is that your adapter first prioritize ORTB-level parameters as you note in the example:
For Prebid Server, do you also accept these parameters as bidder-specific params? i.e. $.imp[].ext.prebid.bidder.vidoomy.{bcat, battr, etc}
That's what placing these values in the bidder params table implies. You should be aware that Prebid Server supports the ORTB Blocking module, so it's not clear why bidder-specific blocking params would be useful. But there's nothing wrong with supporting them as long as ORTB-supplied values are utilized.
Yes, We support and first prioritize ORTB-level parameters for bcat, badv, bapp, btype and battr. |
🏷 Type of documentation
📋 Checklist