Private Aggregation API (removed)
Noisy aggregate reports from Protected Audience and Shared Storage. Removed in Chrome 152 (Aug 2026).
In one line
Can't send noisy ad totals from Chrome anymore, since it was removed in August 2026
Noisy aggregate reports from Protected Audience and Shared Storage. Removed in Chrome 152 (Aug 2026).
Worklet code could contribute values to histograms that a server summed with differential privacy noise. Retired Oct 2025, deprecated Chrome 144, removed in Chrome 152 (released Aug 25 2026). The Aggregation Service is scheduled for phaseout.
What it can and can't do
What the user does: Nothing. It used to happen inside ad tests
It can
- Have sent grouped reports with added noise from ad auctions
- Have helped measure ads without naming you
It cannot
- Run in Chrome 152 or later
- Name an individual in a report
- Work in Edge, Firefox or Safari
- Replace other ad measurement tools
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Removed | 152 | 2026-08-25 | Removed 2026-08-25 |
| Edge | Not supported | Not available | Not listed | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Removed | 152 | 2026-08-25 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | privateAggregation.contributeToHistogram() |
| Permissions policy | private-aggregation |
| Browser compat keys | api.PrivateAggregation |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Reports delayed 10 min to hours; budget per 10 min and 24 hours |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Histogram contribution
Shape: event
How often: delayed batch
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
budget | integer | units per 10 min | 0 to 65536 | exact |
Technical limits
- Contribution budget of 2^16 units per 10 min and per day per origin
- Reports are encrypted to an Aggregation Service
- Chrome only
The story
What it is
A Chrome tool for adding up noisy ad numbers in secret. It has been removed.
For you
You never saw it work. Ad code in a locked box could add a value to a tally that a server read only with random noise. It was removed in Chrome 152, so you will not meet it.
For makers
It was the reporting arm of Protected Audience and Shared Storage. Advertisers got totals without person level data. With those tools retired, the reports lost their reason to exist.
Where you see it
| Type | Example | Apps |
|---|---|---|
| ads | An ad network counted how many people saw an ad in a group, with random noise so no single person showed. | Google Ads, Criteo |
| analytics | A publisher tallied reach and frequency across sites without sharing a person level list. | None named |
| games | A game ad campaign got a daily total of ad views and installs, in noisy form. | None named |
| media | A video site reported how many viewers watched each ad past 50 percent, in aggregate. | None named |
| shopping | A retailer measured the effect of a retargeting ad without a list of shoppers. | Criteo |
| security | Fraud teams disliked the noise, because it made fake traffic harder to find. | None named |
Risks
- Removed in Chrome
- Noise made small campaigns hard to measure
What the platform says
- Google Chrome: Private Aggregation API. Chrome pitched it as a way to measure ad results with summed, noised reports that hide any one person.
Good uses and abuse
Legitimate uses
- Aggregate measurement (historical)
Known abuse
- Not meaningful abuse; limited by noise
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2022-11, Chrome 107: Shipped
- 2026-01, Chrome 144: Deprecated
- 2026-08, Chrome 152: Removed (stable Aug 25 2026)
Related capabilities
Related
- Shared Storage API (retired). Can't store cross site data for ads in Chrome anymore, since it was retired in 2025
- Attribution Reporting API (retired). Can't measure which ad click led to a purchase in Chrome anymore
Sources
- Privacy Sandbox feature status page (updated Aug 14, 2026)
- Privacy Sandbox history and removal timeline (checked Oct 2, 2026)
- Private Aggregation spec
How well checked: Checked against real behavior.