-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Index Exchange adapter refresh bug #396
Comments
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 |
We are still running final QA on the proposed changes. On Mon, Jun 13, 2016 at 4:07 PM, Matt Kendall notifications@github.com
|
@mkendall07 changes committed, PR was made. |
thanks @indexexchange @jeff-crosby |
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.
The text was updated successfully, but these errors were encountered: