page context affecting products shown?

[michaelkleber]

In your proposal, is there any way for the set of products displayed to be affected by the publisher's rules or publisher page context?

For example, I would imagine some publishers forbid advertising alcohol on their sites. In the original TURTLEDOVE, that kind of restriction could be enforced by the publisher's ad network using their on-device JS to filter out which ads get to participate in the auction. How would this work in a product-level world?

(Maybe there are few enough forbidden categories that you could handle this at the interest group level, i.e. with one interest group for gourmet-foods and another for gourmet-foods-no-alcohol?)

[jonasz]

I think it's best to keep the mechanism as simple as possible:

• As you suggest, the ability to handle this at interest group level could be kept.
• After the bid is won, we could add a way for the ad network to filter out single items before they are passed for rendering.

This way:

• We don't need product_ids at bidding time (no privacy concerns, no additional overhead)
• Ad network has full, granular control over what is displayed on the publisher's page
• The incentive to form interest groups in a meaningful way (gourmet-foods, gourmet-foods-no-alcohol, ...) lies on DSP's side - so as to avoid winning bids for which all products would be filtered out. The content labels at interest group should be consistent with the labels for individual products.

// The mechanism of selecting / filtering out single items at rendering time could also be used for a different functionality that we were thinking of - picking items to show based on Recent Ad Events and context.

[JeremyMorvan]

We have a similar question from an Advertiser standpoint. Would it be possible to use contextual signals received at auction time to select products to be displayed? E.g. the banner size could influence the number of products or the type of products to be displayed.

[jonasz]

Hi Jeremy

I somehow missed your message here and only saw it now, really sorry about the delay.

As to the banner size, there is some discussion on it in the fenced-frame spec: https://github.com/shivanigithub/fenced-frame/blob/master/README.md#privacy-considerations

I think the answer to your question will depend highly on the direction TD will take in some other areas (see e.g. https://github.com/jonasz/product_level_turtledove/issues/8#issuecomment-678137056).

I was wondering, besides the banner size, do you see other contextual signals that would be valuable for you?