orrb1
commented
6 months ago Thanks for the feedback. My understanding of how an additional bid would typically be generated is that, at auction time, the seller would issue the contextual request to the buyer's server, which would clearly indicate who the seller is for that auction, and could also communicate who the top-level seller would be for that auction alongside the auction nonce, and that the buyer would use these values to construct an additional bid. Given that each additional bid has to be uniquely generated for the auction because each auction has a unique nonce, what would the use case be for not populating the seller or top-level seller fields?
Today - additional bids must include both a seller URL and a top-level seller URL; both seller and top-level seller fields must be known by the buyer (and cannot be filled by an intermediary seller) since the entire additional bid must be signed by a buyer’s private key. This is contrary to the typical buyer-seller relationship where a buyer only has a relationship with their direct seller (but not a seller removed further away from the buyer, such as an ad server or a header bidding wrapper).
In standard FLEDGE bidding, buyers have control over which sellers or top-level sellers that they bid on via the browserSignals in generateBid. However, buyers can choose to ignore these seller signals and bid into any seller or top-level seller. In contrast, additional bids require that buyers explicitly specify the seller and top-level seller. We propose that additional bids’ seller fields should include an optional wildcard ‘*’ which matches any seller or top-level seller.