Skip to content
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

Closed
klinde-inuvo opened this issue Sep 15, 2016 · 7 comments
Closed

Impression Discrepancy with Prebid 12 #634

klinde-inuvo opened this issue Sep 15, 2016 · 7 comments
Assignees
Labels

Comments

@klinde-inuvo
Copy link

klinde-inuvo commented Sep 15, 2016

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?

@mkendall07
Copy link
Member

Hi @klinde-inuvo
I haven't heard of this yet. Can you give some more details? Which version where you running previously? Any customizations? Are the discrepancies consistent? Which bidders are showing the highest % for you?

@klinde-inuvo
Copy link
Author

klinde-inuvo commented Sep 20, 2016

Hi Matt,
Thanks for reaching out. I have attached a spreadsheet of our bidders that we had onboard prior to upgrading v12. We were running v8 prior to the update. Our developer thinks it was 8.1.1. We didn’t do any customization other than adding the standard GA events.
The discrepancies are fairly consistent across Sovrn, Pulsepoint and AOL. You can see the increase in discrepancy that started on 8/29 when we upgraded. Appnexus and bRT were not affected. We also added Sonobi on 8/29. Sonobi has had a <10% difference in impressions since coming on board. Let me know if you need any additional information.

Regards

@mkendall07
Copy link
Member

@klinde-inuvo
Sorry didn't get the spreadsheet. Can you email it to me (check my profile for email). Thanks

@protonate protonate self-assigned this Oct 17, 2016
@protonate
Copy link
Collaborator

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.

@protonate
Copy link
Collaborator

Update: with #706 Pulsepoint is syncing bid request / response IDs.

@headerbidding
Copy link

I also experience a discrepancy of > 20% with Sonobi.
Sonobi tech support says "There isn't anything my team can do for you especially since we are implemented via another wrapper (prebid). "

@mkendall07
Copy link
Member

@headerbidding please open a new ticket with details of your setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants