perBuyerSignals in auction about turtledove

[dmdabbs]

As perBuyerSignals is generated by the Seller and passed to generateBid function of the Buyer, what can be inserted as values. Can this be arbitrarily defined by the Seller?

Those could be signals the buyer generates and provides to the seller in an OpenRTB response (what PA refers to as a 'contextual bid response') as the explainer mentions:

... This can include contextual signals about the page that come from the buyer's server, if the seller is an SSP which performs a real-time bidding call to buyer servers and pipes the response back, or if the publisher page contacts the buyer's server directly. ...

To provide partners flexibility using this 'channel,' the TechLab "OpenRTB in Sandbox" subgroup has evolved ORTB extensions for returning PA buyer intents including an optional perBuyerSignals value, pbs, that the SSP partner would plumb into the the auction config's perBuyerSignals. The 'namespacing' guideline for how sellers key the perBuyerSignals dictionary supports the seller (or other entities) providing buyer-specific info alongside this optional value from the buyer's system.

See
InterestGroupAuctionBuyer object (buyer returning signals)
InterestGroupAuctionBuyerSignals object (the 'namespaced' dict value sellers provide in the auction config's perBuyerSignals)
Example namespaced auction config

(if you're in the TechLab Slack, DM and I can connect you with the group)

[TheTamFamily]

@dmdabbs : Not sure if this is a ridiculous question, is there any reason why "buyer intent" cannot be inserted in the IG as another attribute. I'm just not clear on why this is better done via ORTB. Please could you add me [email protected] to the TechLab slack. Thanks.

[michaelkleber]

David Tam: Yes, perBuyerSignals is the place for sellers to provide to buyers whatever information they want to make available inside the auction. What ought to go there is, as David Dabbs says, an excellent thing for the industry to decide.