FYI: We are planning to ramp k-anonymity enforcement back up to 50% of eligible traffic on Beta channel later today.
Best, --Benjamin "Russ" Hamilton On Wed, Apr 3, 2024 at 1:25 PM Russ Hamilton <behamil...@google.com> wrote: > Recently, we became aware that Chrome was mistakenly applying k-anonymity > enforcement on reporting to a portion of Mode A and Mode B testing traffic > <https://developers.google.com/privacy-sandbox/relevance/setup/web/chrome-facilitated-testing>. > This did not affect ad selection and therefore should have had little or no > impact on auction dynamic or pressure. To mitigate this issue, we briefly > turned off k-anonymity enforcement on all Chrome traffic. We have landed a > high confidence fix for this issue and have started ramping back up > k-anonymity enforcement on eligible traffic1 that has the fix. > > > The application of k-anonymity enforcement in Mode A and Mode B traffic > did not affect ad selection, i.e. no winning ads were removed because the > creative URLs were below the k-anonymity threshold and the creative URLs > would continue to be available in reportWin() and reportResult(). The > k-anonymity enforcement on reporting means that some Mode A and Mode B > traffic may have been inadvertently missing interestGroupName, > buyerReportingId, or buyerAndSellerReportingId in reportWin(), and > buyerAndSellerReportingId in reportResult(), in cases where the value, when > combined with the interest group owner, bidding script URL, and ad creative > URL was not jointly k-anonymous. Adtech scripts should properly handle the > lack of these values in reportWin() and reportResult() as they’ve always > been intended and specified as optional and missing when they don’t meet > the k-anonymity threshold. However, we understand that the current > implementations may not have reached this stage of development. Here’s a > timeline of how k-anonymity enforcement was ramped: > > > Jan 24 - Feb 12 > > <1% > > Feb 12 - Mar 7 > > <4% > > Mar 7 - Mar 13 > > <13% > > Mar 13 - Mar 22 > > 1% > > Mar 22 - Apr 2 > > k-anon enforcement disabled, ~0% > > Apr 2 > > fix deployed, ramping back up, <1% > > > > We have started ramping k-anonymity enforcement up on pre-stable and plan > to continue ramping on eligible traffic1. We apologize for the > inconvenience caused by this disruption. > > > 1 Eligible traffic is pre-stable and stable channels, excluding Mode A > and Mode B traffic. > > > Best, > --Benjamin "Russ" Hamilton > > On Thu, Jan 25, 2024 at 6:59 PM Russ Hamilton <behamil...@google.com> > 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-DU2mz-0QXAqxUdX8v%3DcxPS2RXeV0hphBmSozL2%3D0nvZLBA%40mail.gmail.com.
