-
Notifications
You must be signed in to change notification settings - Fork 748
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
User sync Issue introduced by PR 2948 #3477
Comments
PR #2948 accounts for the change from syncer key to bidder name by swapping the I tested this flow to ensure it's working as intended and could not find an issue. Are you experiencing a problem? |
@matthieularere-msq This functionality appears to be working correctly. Please confirm if you're seeing an issue in production. |
I happened to have an issue with my setuid endpoint, I guess it was caused by a merge issue with my fork. |
I've just found an issue introduced by this PR : #2948 👍
prebid-server/usersync/syncer.go
Line 129 in 9693132
By using
bidderName
it makes that if the usersync key has a different value, then request sent to the bidder won't have any value for the User.BuyerUID openrtb field.It happens that this is precisely the case for appnexus adapter which use
adnxs
as a key. It makes that user sync for this bidder no longer works.The text was updated successfully, but these errors were encountered: