google / ads-privacy

Apache License 2.0
333 stars 74 forks source link

ROBIN and product-level TURTLEDOVE #31

Open jonasz opened 3 years ago

jonasz commented 3 years ago

Hi,

ROBIN describes a potential information flow between SSP and DSP during an interest group request. The specification of this request is taken from vanilla Turtledove.

PLTD extends the specification of interest group request by bringing product_ids into the picture. The exact details are not formalized yet, but the following excerpt summarizes the general idea:

In requests to ../.well-known/fetch-ads endpoint browser fetches ads for specified interest groups as previously. However, it also fetches the corresponding products' web_bundles - packages with assets necessary for rendering the product's presentation. This can be done in separate requests if needed.

PLTD is an extension of critical importance to us, and it seems that ROBIN can be easily adopted to work with it. As the explainer makes no mention of PLTD, however, I'd be grateful for your opinion, do you see any potential issues when it comes to adjusting ROBIN to PLTD?

Best regards, Jonasz

suprajasekhar commented 3 years ago

Thanks for your interest in ROBIN.

Yes, the information flows suggested by ROBIN can be easily adopted to support PLTD. Interest group metadata requests from a DSP to an SSP could contain a list of ad creatives, products or a combination of the two interchangeably (both as first-class conceptual entities). In addition to the creative-level metadata, a DSP can cache the product-level metadata provided by their SSP partners. In their interest group response, a DSP can include all the relevant sspMetadata for one or more ads or products.

Based on the contextual auction signals and sspMetadata, DSPs can pre-filter disqualified products in bidding.js and return a list of eligible products and their metadata. As mentioned in FLEDGE, an SSP can compare the metadata for an ad and/or products against publisher controls and policies applicable to the request to determine the ad’s eligibility. If any of the products returned by the DSP’s bidding function is ineligible due to the applicable ad policies or publisher controls, an SSP may choose to disallow the ad from participating in the on-device auction.

Regards, Supraja