Updated docs for Vidoomy blocking supported

[nimasrn]

🏷 Type of documentation

• update bid adapter
• new feature

📋 Checklist

• Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself

[netlify]

✅ Deploy Preview for prebid-docs-preview ready!

Name	Link
🔨 Latest commit	4a96e1e
🔍 Latest deploy log	https://app.netlify.com/sites/prebid-docs-preview/deploys/643eac2773028d0008354b28
😎 Deploy Preview	https://deploy-preview-4493--prebid-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[bretg]

@nimasrn - please clarify this support. The requirement is that your adapter first prioritize ORTB-level parameters as you note in the example: $.bcat, $.battr, etc.

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.

[nimasrn]

@nimasrn - please clarify this support. The requirement is that your adapter first prioritize ORTB-level parameters as you note in the example: .bcat,.battr, etc.

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.