Private Aggregation API: aggregation coordinator selection

Category: Miscellaneous
Type: New or changed feature
Status: Enabled by default (Chrome 121)
Intent stage: None

Summary

Modification to the Private Aggregation API to provide a mechanism for selecting which coordinator to use for payload encryption (from an vendor-specified allowlist). The choice of service is made with an additional option in Shared Storage’s run() and selectURL() calls, and in Protected Audience’s runAdAuction() and joinAdInterestGroup() calls. The broad approach largely aligns with Attribution Reporting’s approach (see https://chromestatus.com/feature/5197591256236032).

Motivation

To support multiple deployment options for the aggregation service, e.g. deployments on different cloud providers

Standards & signals

Specification: https://github.com/patcg-individual-drafts/private-aggregation-api/pull/106
Firefox: Closed Without a Position — We have not requested a signal for this change specifically. The Gecko position on Shared Storage (one of the ways Private Aggregation is exposed) is negative.
Safari: Closed Without a Position — We have not requested a signal for this change specifically
Web developers: No signals
Tracking bug: https://crbug.com/1481254

Explainers: https://github.com/patcg-individual-drafts/private-aggregation-api#aggregation-coordinator-choice

View on chromestatus.com