WICG/turtledove

The Protected Audience official demo contradicts the official documentation

kianooshyn opened this issue · 5 comments

kianooshyn commented

The Protected Audience API doc says "The browser will only render an ad if the same rendering URL is being shown to a sufficiently large number of people (e.g. at least 50 people would have seen the ad, if it were allowed to show)."

But the demo in https://protected-audience-demo.web.app/ successfully renders an ad with just a single user being added to an interest group and (on the publisher side) seeing a relevant ad to that group.

How should these two be reconciled? Is the limit of 50 a future thing? Then perhaps it needs clarification in the API doc.

TheTamFamily commented

I may be mistaken but k-anon is not yet enforced.

kianooshyn commented

I'm pretty noob in this community. What's the best way to get an authoritative answer?

michaelkleber commented

Welcome @kianooshyn. The developer documentation that David pointed to is a good place to see what we expect to happen in the future. In particular it explains that the initial k-anonymity threshold is k=10 people.

For updates on what is happening live in Chrome, the "blink-dev" mailing list is the authoritative source of truth. The thread on k-anonymity enforcement is here:

https://groups.google.com/a/chromium.org/g/blink-dev/c/exVncc_qAME/m/WeloGetYAAAJ

In particular, as the last message in that thread indicates, we are currently experimentally enforcing the k-anonymity requirement on about 1% of Chrome stable traffic, and never enforcing it on the explicitly labeled ("Mode A" and "Mode B") slices.

kianooshyn commented

Thank you. Much appreciated.