Bidder specific info from the client request is applied to all aliases of the same bidder

[YuriyVelichkoPI]

Not sure if this is a bug or intentional behaviour but we noticed that

• if requests have several aliases for the same bidder, let's say "my_bidder_1" and "my_bidder_2"
• the $.imp[].ext.prebid.imp contains the floor for one of the aliases for example for "my_bidder_1"

--- > this floor will be applied to all other aliases as well. So that both requests for "my_bidder_1" and "my_bidder_2" will have the bidder specific floor for "my_bidder_1".

It looks like incorrect behaviour since we expect to see that only bidder request for specific alias will have the floor defined in $.imp[].ext.prebid.imp but the request for other alias will have the floor from the $.imp[].bidfloor.

Probably the reason in this line of code:

prebid-server-java/src/main/java/org/prebid/server/auction/ImpAdjuster.java

Line 105 in 413779f

if (bidderAliases.isSame(fieldName, bidderName)) {

Maybe server should also check the exact alias name matching in addition to the current condition.

In this case the behaviour is applicable not only to floors but to all info in $.imp[].ext.prebid.imp.

[AntoxaAntoxic]

Hi @YuriyVelichkoPI Could you share the whole ortb request if possible?

That feature is quite cumbersome in some ways and at first glance the behavior you've described looks unexpected.

[YuriyVelichkoPI]

Hi @YuriyVelichkoPI Could you share the whole ortb request if possible?

That feature is quite cumbersome in some ways, and at first glance, the behavior you've described looks unexpected.

Hi @AntoxaAntoxic, thanks for taking a look. Sorry, I need some time to prepare the request based on the vanilla prebid server, and I don't have the bandwidth right now. I'll provide it as soon as possible.

[bsardo]

The backlog committee discussed. Each bidder, regardless of whether they are an alias, should have their own bidder info. This is how PBS-Go behaves. It is possible this was a design decision for PBS-Java. The Java team will investigate.

[Net-burst]

Yeah, can confirm that this is indeed a bug. We're working on a fix. Thansk for raising this, @YuriyVelichkoPI !