Providing interest group ad metadata to on-device publisher auction logic

[sbelov]

Publisher auction logic – including aspects such as publisher brand safety controls, ad quality checks, pricing rules and fee computation – may often take into account information about an ad candidate for making accurate eligibility and pricing decisions. Examples of information about an ad candidate can include category and advertiser classification and ad quality check results; such ad candidate metadata may originate from a publisher ad network (SSP), an advertiser ad network (DSP) or both.

In #70, I asked whether TURTLEDOVE API can include support for on-device publisher-specified auction eligibility and ranking logic. Since such logic often needs to take into account ad candidate metadata, can you consider adding support for attaching metadata (arbitrary from the browser’s standpoint) with interest group ad candidates for use in the on-device auction? Could interest group ad candidate metadata be provided either as part of the interest group response, or, as suggested in TERN, at the time a browser joins an interest group?

[JensenPaul]

Closing as I think this was addressed by allowing metadata in the interest group via the userBiddingSignals field, and in the bid via the ad field returned by generateBid().