[blink-dev] PSA: Protected Audience k-Anonymity Enforcement

We plan to start enabling the k-anonymity enforcement feature for the Protected Audience API (Intent to Ship

Re: [blink-dev] PSA: Protected Audience k-Anonymity Enforcement

Mike Taylor 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 Hami

[blink-dev] Re: Intent to Experiment: Cookie Deprecation Labeling

FYI, based on feedback from testers (https://github.com/WICG/turtledove/issues/946) we are going to send the Cookie-Deprecation label headers during the trusted bidding and trusted scoring signals fetches for Protected Audience auctions beginning in M122. Note that if the user is not part of th

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

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 . This did not affect ad selection and therefore should

[blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

Contact emails pauljen...@chromium.org, behamil...@google.com Explainer Chrome: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md Note that this explainer has

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

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 wrote: > Recently, we became aware that Chrome was mistakenly applying k-anonymity > enforcement on

Re: [blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

y in one spot would be helpful, thanks. > On 4/4/24 12:19 PM, 'Russ Hamilton' via blink-dev wrote: > > Contact emails > > pauljen...@chromium.org, behamil...@google.com > > Explainer > > Chrome: > https://github.com/WICG/turtledove/blob/main/FLEDGE_browse

Re: [blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

t;> TAG review >> bit.ly/blink-signals requests >> Outreach for feedback from the spec community >> WPT tests >> >> I recognize some of this is touched on in your email - but having it >> explicitly in one spot would be helpful, thanks. >> On 4

[blink-dev] Re: PSA: Protected Audience k-Anonymity Enforcement

FYI: We are currently in the process of ramping k-anonymity enforcement back up to 1% of eligible traffic on Stable channel. As before, eligible traffic is pre-stable and stable channels, excluding Mode A and Mode B traffic. Best, --Benjamin "Russ" Hamilton On Mon, Apr 8, 2024 at 1:20 PM Russ Ham

[blink-dev] Intent to Extend Experiment: Protected Audience Bidding & Auction Services

Contact emails pauljen...@chromium.org, behamil...@google.com Explainer Chrome: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md Note that this explainer has

[blink-dev] Fwd: Intent to Extend Experiment: Protected Audience Bidding & Auction Services

(Now *To* blink-dev instead of just CC) Contact emails pauljen...@chromium.org, behamil...@google.com Explainer Chrome: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_servic

Re: [blink-dev] Fwd: Intent to Extend Experiment: Protected Audience Bidding & Auction Services

d3Yz7I/m/Pm842qm_AAAJ >> >> >> Requesting M127 to M130 on 6/20/24, >> https://groups.google.com/a/chromium.org/g/blink-dev/c/2bwMHd3Yz7I/m/RigQFZilAgAJ >> >> >> Question: what happened between M122 and M124? Was the experiment

[blink-dev] Intent to Ship: Protected Audience Bidding & Auction Services

Contact emails pauljen...@chromium.org, behamil...@google.com Explainer Chrome: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md Specification The web platf

Re: [blink-dev] Intent to Ship: Protected Audience Bidding & Auction Services

Wed, Oct 16, 2024 at 9:59 AM Mike Taylor wrote: > On 10/7/24 10:30 AM, 'Russ Hamilton' via blink-dev wrote: > > Contact emails > > pauljen...@chromium.org, behamil...@google.com > > Explainer > > Chrome: > https://github.com/WICG/turtledove/blob/main/FLEDGE

Re: [blink-dev] Intent to Ship: Protected Audience Bidding and Auction Services: Allow trusted bidding signals to trigger interest group updates

s in your chromestatus >> entry? >> On 11/22/24 3:45 PM, 'Russ Hamilton' via blink-dev wrote: >> >> Contact emails >> >> pauljen...@chromium.org, behamil...@google.com >> >> Explainer >> >> For the Protected Audience featu

Re: [blink-dev] Intent to Ship: Protected Audience Bidding and Auction Services: Allow trusted bidding signals to trigger interest group updates

>>> >>> On Tue, Dec 3, 2024 at 8:38 PM Vladimir Levin >>> wrote: >>> >>>> >>>> >>>> On Tue, Nov 26, 2024 at 6:42 PM Mike Taylor >>>> wrote: >>>> >>>>> Could you please request the various review

[blink-dev] Intent to Ship: Protected Audience Bidding and Auction Services: Allow trusted bidding signals to trigger interest group updates

Contact emails pauljen...@chromium.org, behamil...@google.com Explainer For the Protected Audience feature that this extends to Bidding and Auction Services: https://github.com/WICG/turtledove/pull/1095 Specification Web platform: https://github.com/WICG/turtledove/pull/1294. Services protoco

[blink-dev] Intent to Ship: Protected Audience (B&A): Support multiple sellers in navigator.getInterestGroupAdAuctionData

Explainer https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md#device-orchestrated-multi-seller-auctions https://github.com/WICG/turtledove/pull/1403 Specification https://wicg.github.io/turtledove/#getInterestGroupAdAuctionData https://github.com/WICG/turtle

Re: [blink-dev] Intent to Ship: Protected Audience (B&A): Support multiple sellers in navigator.getInterestGroupAdAuctionData

? > > LGTM1 > > On Tue, Mar 25, 2025 at 12:01 PM 'Russ Hamilton' via blink-dev < > blink-dev@chromium.org> wrote: > >> Explainer >> >> >> https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md#device-orchestra

Re: [blink-dev] Intent to Ship: Protected Audience (B&A): Support multiple sellers in navigator.getInterestGroupAdAuctionData

Can I get an update on this? Thanks, --Benjamin "Russ" Hamilton On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor wrote: > LGTM2 > On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote: > > Yes, it's just a performance/ergonomics change. Developers coul

Re: [blink-dev] Intent to Ship: Protected Audience (B&A): Support multiple sellers in navigator.getInterestGroupAdAuctionData

gt; On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor >> wrote: >> >>> LGTM2 >>> On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote: >>> >>> Yes, it's just a performance/ergonomics change. Developers could >>> previously g