-
Notifications
You must be signed in to change notification settings - Fork 739
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
Getting alias bidder name in the bid.ext.prebid.meta.adaptercode instead of corebidder #3363
Comments
@Pubmatic-Supriya-Patil - the original issue in question is #2174 -- here's where we defined:
So I'm against changing this without a deeper understanding of why it's causing you a problem? What piece of code upstream is "not expecting" the aliased biddercode? |
@bretg Wasn't the initial intention of the |
What you're saying makes sense, but it's an important change to something that was discussed and approved by the committee a year ago. We will have to go back to the committee to discuss and approve the change. Here's the proposed new wording:
Sound ok? |
sounds good to me |
Discussed in committee. We need to define the use cases and expected results. @patmmccann pointed out that there's an additional related field, which is seatbid.bid.ext.prebid.meta.demandSource. It's not clear to me that this field is useful in a Prebid Server context because I think it should always be the same as the ORTB seatbid.seat, right? Here's a cut at the use cases:
Pubmatic team -- if we need both the base biddercode and the aliased biddercode, please help us understand why. |
Current behaviour:
Expected behaviour:
Current behaviour (alias):
Expected behaviour (alias):
Suggested change (alias) - @bretg
For Alias, we're ok with the orginal behaviour (<v0.275.0) as well as the one suggested by Bret but for non-alias, adapterCode should be pubmatic and not groupm since groupm adapter does not exist in PBS. We use all these data for reporting purposes. |
Discussed in committee. This topic has gotten complicated with various features:
Here are the definitions and source for each field:
Here's a table that outlines all the combinations.
(*) Found that aliases are not case insensitive in PBS-Java, at least when using storedresponses. |
Updated the table to include DemandSource. |
👍 I agree with the table presented above by @bretg. @Pubmatic-Supriya-Patil, in that case, because PBS-Go does not currently have a generic adapter, PBS-Go will always set |
PBS-Go is now correctly setting the adaptercode for all scenarios except for the hard alias case. In that scenario adaptercode is currently set to the hard alias just like the seat. PBS-Go will address this in a separate PR in the near future. |
As a part of PR(#3100),
code is removed and added
With this change, there is change in bid response where adaptercode is expected as corebidder but from response we are getting aliase bidder name which is not expected.
Example: Suppose pubmatic is the core bidder and pubmatic-1 is aliase bidder so in the bidresponse we should get pubmatic as a adapter code but we are getting pubmatic-1 as a adapter code.
Another point is that with this PR, adapter name is only set in case of seatbid so not sure this is expected or not.
The text was updated successfully, but these errors were encountered: