Closed npeceniak closed 5 years ago
@npeceniak
1) You need to also include spotxBidAdapter
while downloading prebid. As of now there is a dependency on client side adapter even we you are doing just server side header bidding.
2) Prebid server adapter does not ignore adapter options. It copies the value in setConfig to imp[0].ext.spotx
. In above shared sample snippets, if you update the value in setConfig you will see the results.
3) I think what you are looking for is extPrebid
.
pbjs.setConfig({
s2sConfig: {
extPrebid: {
spotx: {
ortb_version: '2.5',
channel_id: 85394
}
}
}
});
@jaiminpanchal27 Thank you for such a quick reply. I did download a the latest prebid.js and included both the spotdBidAdapter
and the prebidServer
so this latest test was done on version 2.31.0. I also tried using the extPrebid object as you suggested but that results in my spotx object being a child of the request.ext.prebid
object and the server adapter expects the spotx object to be a sibling to the prebid one. Do you have any suggestions on how to add a object as a sibling to the prebid object instead of a child?
@npeceniak I looked at prebidServerAdapter
again and conclude that we cannot add object as sibling as of today. Can you create a feature request explaining your use case ? Prebid core team will take a look and get back to you.
You're right @npeceniak that the prebid.org documentation was wrong on this. The adapterOptions setting affects request.imp[].ext.BIDDER. Doc has been fixed.
So we currently support defining
s2sConfig.extPrebid
)s2sConfig.adapterOptions
)Sounds like you're asking for adding ext.BIDDER
as an option. I suppose that could be a new s2sConfig.ext
option. We discussed that when designing s2sConfig.extPrebid and thought it best for us to limit Prebid stuff to ext.prebid.
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.
Type of issue
Question
Description
I am trying to test out a new prebid server adapter that requires a few bidder specific parameters in the JSON request.ext.{BIDDER} object and based on the documentation it looks like I should be able to use the adapterOptions object in s2sConfig to add the parameters I need however the adapterOptions object I set seems to be ignored.
Steps to reproduce
Configure adUnits and s2sConfig as listed below.
Test page
The need for that request.ext.spotx object in the request body can be seen with the cURL requests below.
Request missing required spotx object returns error code 999 "Unexpected end of JSON input:
cURL request including required spotx object returns a valid response:
Expected results
When hitting the openrtb2/auction endpoint on the prebid server I expect the request JSON to look like the following:
Actual results
The request JSON is generated as the following, missing the request.ext.spotx object.
Platform details
Prebid Version. 2.30.0
Other information