LGTM3 - per previous proclamations
/Daniel
On 2025-11-12 17:23, Chris Harrelson wrote:
LGTM2 with the same conditions.
On Wed, Nov 12, 2025 at 8:21 AM Vladimir Levin <[email protected]>
wrote:
LGTM1 to deprecate. The plan to keep deprecation for 6 milestones
also sounds good. Please come back to this thread at a time when
you think the removal can proceed. Since the amount of page loads
is high, we would like to reserve the right to pause the removal
if this amount of page loads does not decrease substantially.
On Friday, November 7, 2025 at 2:02:34 PM UTC-5 Alex Turner wrote:
Contact emails
[email protected]
Explainer
https://github.com/patcg-individual-drafts/private-aggregation-api
<https://github.com/patcg-individual-drafts/private-aggregation-api>
Specification
https://patcg-individual-drafts.github.io/private-aggregation-api
<https://patcg-individual-drafts.github.io/private-aggregation-api>
Summary
The Private Aggregation API is a generic mechanism for
measuring aggregate, cross-site data in a privacy preserving
manner. It was originally designed for a future without
third-party cookies.
Following Chrome's announcement that the current approach to
third-party cookies will be maintained, we are now planning to
deprecate and remove the Private Aggregation API (along with
certain other Privacy Sandbox APIs, as outlined on the Privacy
Sandbox feature status page
<https://privacysandbox.google.com/overview/status>). This API
is only exposed via the Shared Storage and Protected Audience
APIs, which are also planned to be deprecated and removed. So,
no additional work will be required for Private Aggregation.
Blink component
Blink>PrivateAggregation
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EPrivateAggregation%22>
Web Feature ID
None
Motivation
Chrome has announced
<https://privacysandbox.com/news/update-on-plans-for-privacy-sandbox-technologies/>that
the current approach to third-party cookies will be
maintained. Given this, we expect adoption of the Private
Aggregation API to decrease over time as cross-site
measurement will remain possible in Chrome using third-party
cookies. Further, other browser engines have not signaled
interest in launching the API. Removing this (and certain
other Privacy Sandbox APIs
<https://privacysandbox.google.com/overview/status>) will help
focus efforts on the proposed interoperable Attribution
<https://github.com/w3c/attribution>standard.
Possible breakage
Sites that rely on Private Aggregation reports for cross-site
measurement and do not migrate to alternative solutions will
experience a disruption on the removal of the API.
No specific JavaScript API changes are required to remove
Private Aggregation as the API is only exposed within
Protected Audience and Shared Storage contexts. So, Private
Aggregation’s functionality is planned to be transitively
removed by the removal of those two APIs.
If usage warrants, the Protected Audience and Shared Storage
APIs may be temporarily retained with stub/no-op
implementations of their calls to avoid any risk of page
breakage. In that case, the isolated contexts where Private
Aggregation is exposed would still no longer be created and
there would be no need to retain a stub implementation of
Private Aggregation.
User-facing risks
Please see Protected Audience and Shared Storage’s Intents to
Deprecate and Remove.
Debuggability
N/A
Requires code in //chrome?
False
Estimated milestones
Deprecate in M144 and then remove in M150.
There will be one aspect of the API that will end sooner.
Server-side
<https://privacysandbox.google.com/private-advertising/aggregation-service>summary
report computation will no longer operate by late December
2025. We have already communicated to the users of that
service of these plans. Such users can use debug reports
instead until the removal of the API surface as a whole. Since
this impacts post-facto server-side operations, it will not
incur any user-facing breakage.
Currently ~3%
<https://chromestatus.com/metrics/feature/timeline/popularity/4333>of
page loads use the Private Aggregation API. While this usage
is quite high for a deprecation and removal, it is driven by a
small number of third-party ad tech scripts present on a large
number of sites. We will continue to monitor usage in addition
to providing comprehensive updates on
privacysandbox.google.com
<https://privacysandbox.google.com/>with the status of the API
and deprecation plans
<https://privacysandbox.google.com/overview/status>.
We will proactively work toward reducing usage to low levels
once this intent is approved, including disallowing any new
enrollment sign-ups, and contacting enrolled sites to inform
them about the deprecation timelines.
Please see Protected Audience and Shared Storage’s Intents to
Deprecate and Remove for plans in case usage is still too high
to fully remove those APIs at M150 due to user-facing breakage
concerns.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4683382919397376?gate=6554931293192192
<https://chromestatus.com/feature/4683382919397376?gate=6554931293192192>
This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.
--
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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/eb13ea77-5253-40b6-a383-dec33cfd9a62n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/eb13ea77-5253-40b6-a383-dec33cfd9a62n%40chromium.org?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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_QnuFz%2Bi5wHhWMC2YbvCffTBy32J3uHGaRXr15c-9%2BWA%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_QnuFz%2Bi5wHhWMC2YbvCffTBy32J3uHGaRXr15c-9%2BWA%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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/25c82acd-0abb-4925-9d8f-a85c90550462%40gmail.com.
