-
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
Port currency fix from PBS-Java #1067
Comments
Hey @bretg ! Sorry about that but would it be possible to explain what are Cheers ! |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@bretg : Do we see a real need to provide the option to be a string rather than an array? In the Go version, it would take significant number of cycles to check for the possible existence of singe string. It also breaks the openrtb 2.5 spec to provide a single string. |
@hhhjort objects to flexibility in accepting a string value for cur outside of the OpenRTB standard.
I don't know the history for this other than I have a few test files incorrectly formatted. Don't see evidence that the Prebid Server Bid adapter does the wrong thing, so I'm ok with PBS-Go being firm here. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
There's a currency conversion issue in PBS. We've fixed this in PBS-Java with prebid/prebid-server-java#457
Here are the requirements and some test cases:
the client only ever specifies one entry in the
cur
array: the one expected by their adServerIf there are more than one cur specified, use the first and warn.
This cur value must be sent to each adapter
PBS must try to convert bid responses to the first currency in the array
if PBS can't convert a bid, then it should error with "unable to covert bid currency XYZ to desired ad server currency ABC."
Test cases:
cur
field or in the config is the same behavior)The text was updated successfully, but these errors were encountered: