Skip to content
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

Client connecting to S2S adapter failing #575

Closed
smithaammassamveettil opened this issue Jun 19, 2018 · 17 comments
Closed

Client connecting to S2S adapter failing #575

smithaammassamveettil opened this issue Jun 19, 2018 · 17 comments

Comments

@smithaammassamveettil
Copy link
Contributor

Problem:
One of our publishers is trying to test S2S adapter(brightroll) using Prebid.js version 0.34.1
By following the documentation here https://github.com/prebid/prebid.github.io/pull/834/files, they are using endpoint/requestURL https://prebid.adnxs.com/pbs/v1/openrtb2/auction, And also
passing all custom params and bidder details in Request payload, something like this :
{"account_id":"XXX","tid":"XXXX","max_bids":1,"timeout_millis":1000,"url":"xxx","prebid_version":"0.23.1","ad_units":[{"code":"div-gpt-ad-919604695-1","sizes":[{"w":728,"h":90},{"w":970,"h":250},{"w":970,"h":90},{"w":468,"h":60},{"w":1800,"h":600}],"bids":[{"bidder":"brightroll","params":{"publisherName":"adthrive","slot":229},"bid_id":"15adcac0bc90f8"}],"transactionId":"43c7e84a-25f6-4c9a-85d1-fc85d7dc2457"},.......]}

But receiving "400 Bad Request" and error message as "Invalid request: request missing required field: "id" "

Question:

  1. Not sure what is this missing required field "id"?
  2. Client is using Prebid.js version 0.34.1 from their test page, which they were using for client side adapter calls before. Just updated the endpoint to /openrtb2/auction and updated the brightroll required custom parameters to test S2S bidder calls. But receiving some msising required field error. Brightroll bidder has only "publisherName" as the required field. No such "id" field required for the adapter. Is there anything else which Prebid Server is expecting while making an /openrtb2/auction call?
  3. Is it because the client has to use the latest Prebid.js build to connect to S2S adapter? If so, which version?
  4. Any other reason for this issue?

Please advise

@dbemiller
Copy link
Contributor

dbemiller commented Jun 20, 2018

yeah, Prebid.js 0.x versions aren't really supported at all anymore. I'm pretty sure /openrtb2/auction was never implemented there... the missing "id" comes from the openrtb spec. They'll need to use a Prebid.js 1.x version to call you.

My recommendation would be:

  1. Wait for Max origin concurrent auctions Prebid.js#2743 to get merged, and the next 1.x release (they happen every 2 weeks). It's a super important bugfix.
  2. Set s2sconfig.timeout to be the same as their client-side auction timeout. If they don't define a client-side auction timeout, they should use 3000 milliseconds. That works around another PBJS bug described by this comment.

Then upgrade to the latest 1.x version.

@smithaammassamveettil
Copy link
Contributor Author

smithaammassamveettil commented Jun 20, 2018 via email

@smithaammassamveettil
Copy link
Contributor Author

One more thing, I hope the Prebid.js 1.x.x. version will support both client side adapter calls along with server side adapter calls as well. Please confirm.

@smithaammassamveettil
Copy link
Contributor Author

Also I just noticed that this prebid/Prebid.js#2743 got merged. Should we wait for anything else to take latest Prebid.js for testing?

@dbemiller
Copy link
Contributor

So I recommend to make your bidder backward compatible if this truly
should be the issue.

The publisher seems... a little confused. I can understand why.

They're right that some publishers have reasons to avoid using Prebid.js 1.x. They may be overestimating how many. That was a major problem ~2 months ago, but mainly because a few really major bidders weren't in it yet. They were added recently, though... so I'm not sure how widespread of a concern it is anymore.

If they can't upgrade to 1.x, it would take some significant work for them to be able to call you. This has nothing to do with your adapter--just the features built into the core project.

Compare the Prebid.js code which calls Prebid Server in 1.x and 0.x. It was almost completely rewritten, and the 0.x version has no ability to use OpenRTB in Prebid Server at all.

Another issue is that prebid/Prebid.js#2704, which supports your adapter, was made in 1.x only.

Both these features would have to be ported back to 0.x to make it work... which is a significant time investment.

Also I just noticed that this prebid/Prebid.js#2743 got merged. Should we wait for anything else to take latest Prebid.js for testing?

Nope, you're all set. Make sure they use the latest release, and set s2sconfig.timeout to be the same as the overall auction timeout.

@dbemiller
Copy link
Contributor

As a very rough estimate, we see ~2/3 of our prebid impressions being served through 1.x, with ~1/3 being served through 0.x.

@smithaammassamveettil
Copy link
Contributor Author

Thanks @dbemiller for your responses.
I hope Prebid 1.x version is 0.x version plus openRTB support for S2S right? I mean it will do both client side full fledged auctioning which it has before PLUS bid calls and auctioning through S2S adapter as well.

Please confirm.

@dbemiller
Copy link
Contributor

Yes, that is correct.

@smithaammassamveettil
Copy link
Contributor Author

One of our publishers updated their test page with the latest prebid version. However, it doesn’t seem to work correctly. They don’t see the s2s call being initiated
Please find below their testpage:
http://sprudeln.com/brightroll.html

Can you please check the way they are calling brightroll adapter is correct or not? Please advise

@dbemiller
Copy link
Contributor

dbemiller commented Jun 22, 2018

You'll probably get better answers about that one in the Prebid.js repo.

If there's no server call, then the issue can't be a Prebid Server one. The community over there is more active, and many people there are more familiar with debugging publisher pages than I am.

@dbemiller
Copy link
Contributor

dbemiller commented Jun 22, 2018

For what it's worth, I set a breakpoint on the requestBids() call:

screen shot 2018-06-22 at 3 17 58 pm

and don't see any bidders defined in the s2sconfig:

screen shot 2018-06-22 at 3 18 25 pm

So.... that strikes me as a bit suspicious.

@smithaammassamveettil
Copy link
Contributor Author

I see, thanks for looking into it.
They tried some fixes on their side and made progress. Now receiving some other error

I also enabled debug mode. It looks like “bidsBackHandler” is not defined.

image001

@smithaammassamveettil
Copy link
Contributor Author

Please discard my above comment

@dbemiller
Copy link
Contributor

ok... should we close this, then? Or are there any other outstanding issues?

@smithaammassamveettil
Copy link
Contributor Author

We havn't successfully finished our client testing yet. Lets keep it open for couple of days, in case if we have to troubleshoot or need any help from your side for any issues. Thanks!

@hhhjort
Copy link
Collaborator

hhhjort commented Aug 23, 2018

Seems like enough time has passed to close this now?

@smithaammassamveettil
Copy link
Contributor Author

smithaammassamveettil commented Aug 23, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants