Closed jeff-crosby closed 8 years ago
cc: @indexexchange @headerbid
Thanks for your feedback.
There is additional javascript logic that is returned alongside with the demand that ensures that this doesn't happen in production; in general, some of those variables should be persisted across refreshes.
A fix for this issue will be submitted ASAP.
@indexexchange Any update on this? Thanks!
We are still running final QA on the proposed changes.
On Mon, Jun 13, 2016 at 4:07 PM, Matt Kendall notifications@github.com wrote:
@indexexchange https://github.com/indexexchange Any update on this? Thanks!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/prebid/Prebid.js/issues/396#issuecomment-225692768, or mute the thread https://github.com/notifications/unsubscribe/AQzvq3uGnNybZURAbkvSy55aiQdg6hfPks5qLbhkgaJpZM4Iw9Ll .
@mkendall07 changes committed, PR was made.
thanks @indexexchange
@jeff-crosby I've tested the updated indexAdapter, however, I only receive a static bid price so I can't confirm if this resolves the issue. Can you please test it quickly to see if it solves the problem on your end?
Members of our team discovered a significant bug in the IndexExchange adapter that centers around accurately handling new bid data when refreshing the ads on the page.
The bug causes IndexExchange bids to be "sticky." That is, if Index Exchange bids $5 for the first ad call, then $1 for every future ad call, the $5 bid is still active for all the later auctions.
Thus, if Index bids $1 and another bidder like OpenX bids $3, Index could still win with the "sticky" $5 bid.
We actually resolved the bug with the below diff, but we certainly hope a fix like below can be included in the core prebid project.