-
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
Impression Discrepancy with Prebid 12 #634
Comments
Hi @klinde-inuvo |
Hi Matt, Regards |
@klinde-inuvo |
I've had a chance to analyze the spreadsheet and notice that the adapters with increased discrepancies starting with version 12 were not matching bid request / response IDs as recommended in #509. At least two (AOL and Sovrn) now are doing so in master, and Sovrn is also doing so as of current release Prebid 0.13.1. I recommend upgrading to version 0.13.1 and then as soon as possible moving to the upcoming 0.14.0 release. You should see these discrepancies fall off. Note that Pulsepoint is not yet implementing #509. Closing as answered. Please reopen with any new info. |
Update: with #706 Pulsepoint is syncing bid request / response IDs. |
I also experience a discrepancy of > 20% with Sonobi. |
@headerbidding please open a new ticket with details of your setup. |
We implemented version 12 on 8/29. Since then we have seen a dramatic increase in the difference in impressions between DFP and several of our bidders. For one of our bidders it went from <5% to >30%. Interestingly, impression volume between DFP and Appnexus remained the same, ~5-6%. Has anyone seen anything similar?
The text was updated successfully, but these errors were encountered: