You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying aliases in prebid as suggested in the documentation (http://prebid.org/dev-docs/get-started-with-prebid-server.html) we are seeing that in the payload to the syncEndpoint we are not using the proper bidder name but the alias instead, therefore failing due to not finding the bidder in the server.
Steps to reproduce
Adding any alias in the bidders inside the s2sConfig will send them directly to the syncEndpoint without checking for the proper bidder name.
Expected results
Only sending actual bidders to the syncEndpoint
Actual results
Everything set in the s2sConfig.bidders is sent to syncEndpoint
Platform details
Prebid 1.23
The text was updated successfully, but these errors were encountered:
@adriafolchmrf Thanks for reporting this.
When publisher is using alias s2sConfig.bidders list, PBS adapter should find the actual bidderCode and use that to send to userSyncEnpoint.
Type of issue
Bug
Description
When specifying aliases in prebid as suggested in the documentation (http://prebid.org/dev-docs/get-started-with-prebid-server.html) we are seeing that in the payload to the syncEndpoint we are not using the proper bidder name but the alias instead, therefore failing due to not finding the bidder in the server.
Steps to reproduce
Adding any alias in the bidders inside the s2sConfig will send them directly to the syncEndpoint without checking for the proper bidder name.
Expected results
Only sending actual bidders to the syncEndpoint
Actual results
Everything set in the s2sConfig.bidders is sent to syncEndpoint
Platform details
Prebid 1.23
The text was updated successfully, but these errors were encountered: