Most users should not notice a difference. The main difference is going to be which ads are allowed to win Protected Audience auctions. Some non-k-anonymous ads that would have previously won the Protected Audience auction will not win and the auction will return a different, k-anonymous ad as the winner. In the case where there are no k-anonymous bids in an auction then that auction will return without a winner. Protected Audience auctions already return with no winner in some cases, such as when there are no bids, so this does not introduce a new behavior.
On Fri, Jan 26, 2024 at 4:24 AM Mike Taylor <miketa...@chromium.org> wrote: > Hi Russ, > > Can you say more about the compatibility implications for such a change? > AFAIU, things shouldn't "break" for users or throw errors behind the > scenes, correct? > > thanks, > Mike > On 1/26/24 12:59 AM, 'Russ Hamilton' via blink-dev wrote: > > We plan to start enabling the k-anonymity > <https://github.com/WICG/turtledove/blob/main/FLEDGE_k_anonymity_server.md#what-is-k-anonymity> > enforcement feature for the Protected Audience API > <https://github.com/WICG/turtledove/blob/main/FLEDGE.md> (Intent to Ship > <https://groups.google.com/a/chromium.org/g/blink-dev/c/igFixT5n7Bs/m/ZNrDcQ2dDQAJ>). > K-anonymity enforcement has long been a part of the Protected Audience > API’s plan for improving user privacy by limiting ads that can win > Protected Audience auctions to those ads that are k-anonymous. The > k-anonymity enforcement feature limits the ability of advertisers to target > specific users by requiring each ad be shown to a minimum number of users. > This enforcement will initially apply to up to 20% of unlabeled traffic > only, meaning the groups that are part of Chrome-facilitated testing > <https://developers.google.com/privacy-sandbox/setup/web/chrome-facilitated-testing> > for third-party cookie deprecation will not be enforced for k-anonymity > during the testing period. After the testing period, enforcement will apply > to all traffic (see timeline details at > https://developers.google.com/privacy-sandbox/relevance/protected-audience-api/k-anonymity > ). > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to blink-dev+unsubscr...@chromium.org. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU2%3DfH8Q5gDDVms%2BajMA4WzS%3DvQBRPQj8jaiVzJkCdCz7g%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU2%3DfH8Q5gDDVms%2BajMA4WzS%3DvQBRPQj8jaiVzJkCdCz7g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU3-YDn5Wbqs52R%3DacMG7%2B%3D_eB3%3DmCcgRFhRN44SYPk68A%40mail.gmail.com.
