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:
|
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.
Not sure if this is a bug or intentional behaviour but we noticed that
$.imp[].ext.prebid.impcontains 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.impbut 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
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.