You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@SyntaxNode In a prior PR you had suggested for 33Across adapter to handle multi-imp requests by breaking them up into multiple http requests #1557 (comment)
We are in the process of implementing this suggestion. However, I have a question for you. How would Prebid Server handle the individual bid responses and associate them with the incoming mult-imp bid request? The adapter will of course pass the Imp ID in each of the bid response during MakeBids. Will this be sufficient? Does the adapter need to do anything more?
The text was updated successfully, but these errors were encountered:
Prebid Server will call your adatper's MakeBids method once for each response received and combine the bids from all of those calls together as a single OpenRTB Seat Bid for your adapter. I recommend you perform end-to-end testing to make sure it looks right when all is said and done, but I don't anticipate any problems.
FYI: The code for this behavior is found in exchange/bidder.go in the requestBid method if you'd like to explore the logic further. Look for the for i := 0; i < len(bidResponse.Bids); i++ { loop.
@SyntaxNode In a prior PR you had suggested for 33Across adapter to handle multi-imp requests by breaking them up into multiple http requests #1557 (comment)
We are in the process of implementing this suggestion. However, I have a question for you. How would Prebid Server handle the individual bid responses and associate them with the incoming mult-imp bid request? The adapter will of course pass the Imp ID in each of the bid response during
MakeBids
. Will this be sufficient? Does the adapter need to do anything more?The text was updated successfully, but these errors were encountered: