Skip to Content
Platform.Ontology

Private Aggregation API (removed)

Noisy aggregate reports from Protected Audience and Shared Storage. Removed in Chrome 152 (Aug 2026).

Used to track youTracking across apps and sitesPrivacy SandboxWeb browsersAfter you leave the site

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

BrowserStatusFirst versionReleasedNote
ChromeRemoved1522026-08-25Removed 2026-08-25
EdgeNot supportedNot availableNot listedNone
FirefoxNot supportedNot availableNot listedNone
SafariNot supportedNot availableNot listedNone
Safari on iPhoneNot supportedNot availableNot listedNone
Chrome on AndroidRemoved1522026-08-25None
Samsung InternetNot supportedNot availableNot listedNone

How a site asks for it

APIprivateAggregation.contributeToHistogram()
Permissions policyprivate-aggregation
Browser compat keysapi.PrivateAggregation
How access is grantednone
What the user seesNone
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsReports delayed 10 min to hours; budget per 10 min and 24 hours
How to take it backClear site data, browser privacy settings
Inside an iframeNot listed

Data you get

What comes back: Histogram contribution
Shape: event
How often: delayed batch

FieldTypeUnitRangePrecision
budgetintegerunits per 10 min0 to 65536exact

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

TypeExampleApps
adsAn ad network counted how many people saw an ad in a group, with random noise so no single person showed.Google Ads, Criteo
analyticsA publisher tallied reach and frequency across sites without sharing a person level list.None named
gamesA game ad campaign got a daily total of ad views and installs, in noisy form.None named
mediaA video site reported how many viewers watched each ad past 50 percent, in aggregate.None named
shoppingA retailer measured the effect of a retargeting ad without a list of shoppers.Criteo
securityFraud 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

Good uses and abuse

Legitimate uses

  • Aggregate measurement (historical)

Known abuse

  • Not meaningful abuse; limited by noise

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction3 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2022-11, Chrome 107: Shipped
  • 2026-01, Chrome 144: Deprecated
  • 2026-08, Chrome 152: Removed (stable Aug 25 2026)

Sources

How well checked: Checked against real behavior.

On this page