-
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
Yieldbot: Multiple requestBids Not Working #481
Comments
I believe that PR #498 can address this if the Yieldbot adapter can be updated to set the bid response ID to match the bid request ID in these locations: |
is this still an issue? |
@mkendall07 Yes unfortunately. |
@elljoh @amcmillan01 |
@mkendall07 Yes. Please assign to me. |
@elljoh You might try removing the cache=true flag from the |
We have identified problem and expect to have a PR submitted in the next couple of days to reference a fix for this issue. |
So we currently split our ad auctions up amongst our ATF and BTF units and run multiple Prebid auctions. Unfortunately, the Yieldbot adaptor does not work with this.
Easy to replicate. Define two ad units. Run requestBids twice - once the first ad unit and a separate one on the second . Then run yieldbot.dumpLog() in the console.
You'll see that only the initial ad slot that is defined gets a call to getSlotCriteria() with the handleUpdateState() is run. You'll only get bid responses on the initial slots.
The text was updated successfully, but these errors were encountered: