Prebid.js: The highest bid isn't winning
Type of issue
Bug?
Description
The highest bid is not always the bid assigned by pbjs.setTargetingForGPTAsync when enableSendAllBids=false.
Steps to reproduce
Compare pbjs.getBidResponses() to pbjs.getAdserverTargeting(). In our testing with the IX module, we saw ixBidAdapter return two bids for a slot, and the lower dollar amount was assigned.
Expected results
The higher bid is passed to GPT.
Actual results
The lower bid was passed to GPT.
Platform details
Prebid 1.30.0, Chrome.
Other information
Our use of the ixBidAdapter requests bids on every size an ad position can serve. (So one bidder object is added to the unit per size.)
whatisjasongoldstein
All 6 comments
I can't 100% confirm, but from our observation that's something we've noticed as well.
YOzaz
on 19 Nov 2018
This should be fixed!
headerbidding
on 22 Nov 2018
@whatisjasongoldstein is this only an issue for the IX bid adapter or are you seeing it as a general Prebid issue? Also, when checking pbjs.getAdserverTargeting() did you also compare those values to the request query string params (scp query) in the call to GPT to confirm KV targeting there? Looking to confirm if this is a targeting issue or just an issue of what's contained in getAdserverTargeting
bwoolcott
on 27 Nov 2018
It's not IX specific. After I opened the issue we determined that pbjs.getAdserverTargeting() was returning the wrong value but the correct ones were being sent to the network request. This appears to be a red herring. I'll defer to your judgement on whether it's still a valid bug with pbjs.getAdserverTargeting().
whatisjasongoldstein
on 28 Nov 2018
After some investigations, we also observed something new (and weird) with the behavior of the pbjs.getAdserverTargeting function.
At the end of the auction process, pbjs.getAdserverTargeting() is sending back the right values. The highest CPM bid is sent to the adserver. As you said @whatisjasongoldstein "the correct ones were being sent to the network request".
Then after the bidWon event and the renderAd(), the pbjs.getAdserverTargeting() function seems to return a new value.
I think it's a new behavior related to the bid pool logic and bid caching system. The bid has to be deleted after the rendering so the 2nd winning bid is returned by pbjs.getAdserverTargeting().
In my opinion, it's not a bug but a new dynamic behavior.
Deimos01
on 11 Dec 2018
That makes sense and is consistent with our testing. Closing.
whatisjasongoldstein
on 11 Dec 2018
Related issues
mthazin
路
6Comments
eyedar
路
6Comments
aneuway2
路
8Comments
mrpbennett
路
3Comments
jaiminpanchal27
路
3Comments
Most helpful comment
After some investigations, we also observed something new (and weird) with the behavior of the
pbjs.getAdserverTargetingfunction.At the end of the auction process, pbjs.getAdserverTargeting() is sending back the right values. The highest CPM bid is sent to the adserver. As you said @whatisjasongoldstein "the correct ones were being sent to the network request".
Then after the bidWon event and the
renderAd(), thepbjs.getAdserverTargeting()function seems to return a new value.I think it's a new behavior related to the bid pool logic and bid caching system. The bid has to be deleted after the rendering so the 2nd winning bid is returned by
pbjs.getAdserverTargeting().In my opinion, it's not a bug but a new dynamic behavior.