Intent to Ship: Protected Audience: Private Aggregation per-participant usage metrics

133 views
Skip to first unread message

Paul Jensen

unread,
Jan 17, 2025, 8:42:38 AM1/17/25
to blink-dev

Contact emails 

paulj...@chromium.org


Explainer

https://github.com/WICG/turtledove/pull/1272

Specification

https://github.com/WICG/turtledove/pull/1321

https://github.com/WICG/turtledove/pull/1328

https://github.com/WICG/turtledove/pull/1341

https://github.com/WICG/turtledove/pull/1349

https://github.com/WICG/turtledove/pull/1353


Summary

There have been industry requests to add various resource usage/performance metrics to Protected Audience, to be reported via Private Aggregation ([1], [2], [3]), and earlier feedback on similar features suggesting that it's important to report these once per auction. To address it, a new reporting event keyword "reserved.once" is added to address report timing, and new baseValue keywords are added to provide various resource usage/performance metric values.


This launch adds this new support to on-device auctions.  We anticipate extending this support to auctions run on Bidding and Auction Services in the future, and do not anticipate additional risk from that extension.


[1] https://github.com/patcg-individual-drafts/private-aggregation-api/issues/119

[2] https://github.com/WICG/turtledove/issues/1151

[3] https://github.com/WICG/turtledove/issues/1170


Blink component

Blink>InterestGroups


TAG review

For Protected Audience: https://github.com/w3ctag/design-reviews/issues/723

For Private Aggregation: https://github.com/w3ctag/design-reviews/issues/846


TAG review status

Completed for Protected Audience, resolved unsatisfied.

For Private Aggregation: declined.


Risks


Interoperability and Compatibility

Optional new functionality that does not break existing use.


Gecko & WebKit: For Protected Audiences in general - Negative from Mozilla. No signal from Webkit.


Edge: Edge is running an Origin Trial of the Ad Selection API which shares a Web API and services protocol with Protected Audience. The services protocol is currently being extended to support Private Aggregation.


Web developers: Requested by several developers, see [1] [2] [3] above.


WebView application risks

Not exposed to WebView.

Debuggability

Private Aggregation provides a debug mode which makes generated reports inspectable.


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

It will be supported on all platforms that support Protected Audience, so all but WebView.


Is this feature fully tested by web-platform-tests?

Yes to the extent possible — tests of resource usage metrics can only verify bounds, not exact values.


Flag name on about://flags

None


Finch feature name

PrivateAggregationApiProtectedAudienceAdditionalExtensions


Requires code in //chrome?

False


Estimated milestones

Stable launch in M132.


Anticipated spec changes

None


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/4515723416961024?gate=6567874628681728


Yoav Weiss (@Shopify)

unread,
Jan 20, 2025, 8:46:29 AM1/20/25
to Paul Jensen, blink-dev
Similar to past intents, please avoid sending PR diffs as your explainer/spec and link to the relevant spec/explainer sections instead.
 
--
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 blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnbtqLi1eP303dAdg4qDWANPRo-VYX6dL1ftNUewzn-yw%40mail.gmail.com.

Maksim Orlovich

unread,
Jan 21, 2025, 12:59:08 PM1/21/25
to Yoav Weiss (@Shopify), Paul Jensen, blink-dev
So for explainer it's https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#per-participant-metrics

For the spec, it's not really a separate section. Most relevant is handling of reserved.once in https://wicg.github.io/turtledove/#process-the-private-aggregation-contributions-for-an-auction 
and the cases starting from "average-code-fetch-time" in https://wicg.github.io/turtledove/#determine-a-signals-numeric-value, but there is a lot of wiring and dataflow that goes into that, so I 
don't know how helpful these highlights are on their own.



Vladimir Levin

unread,
Jan 29, 2025, 10:59:44 AM1/29/25
to blink-dev, morl...@google.com, Paul Jensen, blink-dev, Yoav Weiss
LGTM1

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.

--
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 blink-dev+unsubscribe@chromium.org.

Chris Harrelson

unread,
Jan 29, 2025, 11:10:05 AM1/29/25
to Vladimir Levin, blink-dev, morl...@google.com, Paul Jensen, Yoav Weiss
LGTM2

LGTM1

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

--
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 blink-dev+...@chromium.org.

--
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 blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/aa8aca27-7e3b-4e92-adbe-89334ba0f16en%40chromium.org.

Philip Jägenstedt

unread,
Jan 29, 2025, 11:10:59 AM1/29/25
to Chris Harrelson, Vladimir Levin, blink-dev, morl...@google.com, Paul Jensen, Yoav Weiss
Reply all
Reply to author
Forward
0 new messages