Conversation
added boldwin endpointId param
✅ Deploy Preview for prebid-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
bretg
left a comment
There was a problem hiding this comment.
@Wls-demo - it's an unusual change to remove a formerly required parameter. What does this statement mean "in case you integrate with Boldwin bidder via an endpoint URL."? Where would such a URL be specified?
Also, note that there are many header fields requested in https://docs.prebid.org/dev-docs/bidder-adaptor.html#submitting-your-adapter missing from this file. Please consider adding as many as possible so publishers are aware of your capabliities.
tcfeu_supported: true/false
gvl_id: none
usp_supported: true/false
coppa_supported: true/false
gpp_supported: true/false
schain_supported: true/false
dchain_supported: true/false
userId: (list of supported vendors)
media_types: banner, video, native
safeframes_ok: true/false
deals_supported: true/false
floors_supported: true/false
fpd_supported: true/false
pbjs: true/false
pbs: true/false
prebid_member: true/false
multiformat_supported: will-bid-on-any, will-bid-on-one, will-not-bid
ortb_blocking_supported: true/partial/false
|
@bretg it was not required parameter. Its required to use one parameter - either placementId or endpointId, but for now we are good to use only endpointId. |
🏷 Type of documentation
📋 Checklist