search

WICG / turtledove

TURTLEDOVE
https://wicg.github.io/turtledove/
Other
521 stars 222 forks source link

The Protected Audience official demo contradicts the official documentation #1229

Closed kianooshyn closed 1 month ago

kianooshyn commented 1 month ago

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 1 month ago

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

kianooshyn commented 1 month ago

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

dmdabbs commented 1 month ago

All about k-anon and its rollout: https://developers.google.com/privacy-sandbox/relevance/protected-audience-api/k-anonymity

michaelkleber commented 1 month ago

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 1 month ago

Thank you. Much appreciated.