LGTM2
On 7/17/24 6:22 PM, Chris Harrelson wrote:
LGTM1
On Fri, Jul 12, 2024 at 1:10 PM 'Akash Nadan' via blink-dev
<blink-dev@chromium.org> wrote:
Hi All,
*
*
Just adding some additional detail regarding the interoperability
and compatibility of this feature:
*
*
Interoperability and Compatibility
This change is optional and will be fully backwards compatible
once Aggregation Service release 2.3 reaches end-of-support on
August 2nd (before M128 reaches Stable).
*
*
Additionally, developers that want to use this new feature will
need to upgrade their Aggregation Service release to version 2.5
or later. The Aggregation Service is used to process the
aggregatable reports that a developer receives. We have notified
partners of these considerations through the API mailing list
<https://groups.google.com/a/chromium.org/g/attribution-reporting-api-dev/c/aGd-gkBR0JE>.
A similar feature is being released for thePrivate Aggregation
API, with the same Aggregation Service considerations
<https://groups.google.com/a/chromium.org/g/blink-dev/c/_04scQwbWhk/m/utgjQDacAgAJ>.
Thanks,
Akash
On Thursday, July 11, 2024 at 12:54:08 PM UTC-7 Akash Nadan wrote:
Contact emails
akash...@google.com, lin...@chromium.org, john...@chromium.org
Explainer
Attribution Reporting with event-level reports
<https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md>
Attribution Reporting API with Aggregatable Reports
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md>
Aggregation Service for the Attribution Reporting API
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATION_SERVICE_TEE.md>
Specification
https://wicg.github.io/attribution-reporting-api/
<https://wicg.github.io/attribution-reporting-api/>
Blink component
Internals > AttributionReporting
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting>
TAG review
Still under review
<https://github.com/w3ctag/design-reviews/issues/724>under the
original I2S for the Attribution Reporting API
TAG review status
Pending
Summary
We are landing the following change to the Attribution
Reporting API focused on:
*
Improving API report batching capabilities
This change is based on ad-tech feedback that we heard
regarding the need for additional report batching flexibility
so that different report contributions can be batched at
different cadences.
Currently aggregatable reports generated by the API can
consist of multiple separate contributions which are key:value
pairs. API callers can batch together aggregatable reports and
then process them in the aggregation service, which consists
of decrypting the reports, aggregating the values, and adding
noise, before returning a summary report to the API caller.
Additionally, all contributions in an aggregatable report must
currently be processed by aggregation service at the same time.
With this change, the API will now allow API callers to
specify filtering IDs as part of each contribution (i.e. each
key:value pair) in the aggregatable report. API callers can
then use these filtering IDs, which will also be part of the
encrypted payload of the report, to specify which
contributions they want to have processed by the aggregation
service at a given time.
This will allow API callers to process contributions with
different filtering IDs at different cadences. Allowing this
flexibility is a utility improvement, because the noise added
in the aggregation service per key:value pair bucket may have
a lower relative impact on values that are batched on a longer
cadence.
Explainer/Spec changes
1.
Flexible contributions filtering
<https://github.com/WICG/attribution-reporting-api/pull/1290>
Risks
Interoperability and Compatibility
This is an optional and fully backwards compatible change.
This feature provides a new filtering ID that can be set as
part of the aggregatable report contributions and does not
break any pre-existing API or web functionality.
Gecko: No signal (Original request:
https://github.com/mozilla/standards-positions/issues/791
<https://github.com/mozilla/standards-positions/issues/791>)
WebKit: No signal (Original request:
https://github.com/WebKit/standards-positions/issues/180
<https://github.com/WebKit/standards-positions/issues/180>)
Web developers:
https://github.com/patcg-individual-drafts/private-aggregation-api/issues/92
<https://github.com/patcg-individual-drafts/private-aggregation-api/issues/92>
*although this is a private aggregation issue link, it also
applies to ARA use cases*
WebView application risks
Does this intent deprecate or change behavior of existing
APIs, such that it has potentially high risk for Android
WebView-based applications?
None
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The attribution reporting feature will be supported on all
platforms with the exception of Android WebView
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
Estimated milestones
This feature is anticipated to ship as part ofChrome 128
<https://chromiumdash.appspot.com/schedule>.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5487434799513600
<https://chromestatus.com/feature/5487434799513600>
Links to previous Intent discussions
Previous I2S:
Intent to Ship: Attribution Reporting API
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY>
Intent to Ship: Attribution Reporting features M117
<https://groups.google.com/a/chromium.org/g/blink-dev/c/nWF61c8xu-M/m/uMmH1ewcAQAJ>
Intent to Ship: Attribution Reporting features M118
<https://groups.google.com/a/chromium.org/g/blink-dev/c/Mh-mJiyJZFk/m/HlgzpphYBQAJ>
Intent to Ship: Attribution Reporting features M119
<https://groups.google.com/a/chromium.org/g/blink-dev/c/6e44SBtEtcQ>
Intent to Ship: Attribution Reporting features M120
<https://groups.google.com/a/chromium.org/g/blink-dev/c/jSk3xpNPzGQ/m/VZPsdYgGCAAJ>
Intent to Ship: Attribution Reporting features M121
<https://groups.google.com/a/chromium.org/g/blink-dev/c/g9KiC6Rg_mA/m/V679WcWuAQAJ>
Intent to Ship: Attribution Reporting features M123
<https://groups.google.com/a/chromium.org/g/blink-dev/c/NE7VGke1Bjc/m/bIX00t4CAAAJ>
Intent to Ship: Attribution Reporting features M124
<https://groups.google.com/a/chromium.org/g/blink-dev/c/aregp1li6xk/m/IhBB2z8tBQAJ>
Intent to Ship: Attribution Reporting features M125
<https://groups.google.com/a/chromium.org/g/blink-dev/c/9UyhI6SRyxM/m/zgWWckgWAQAJ>
Intent to Ship: Attribution Reporting features M126
<https://groups.google.com/a/chromium.org/g/blink-dev/c/7UQR2lPn5KE/m/q_kL6ZiJDgAJ>
Intent to Ship: Attribution Reporting features M127
<https://groups.google.com/a/chromium.org/g/blink-dev/c/LAgnyPsJyJg?pli=1>
Thanks,
Akash
--
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+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ccf4f345-f1e8-4216-bd21-1231214dc0ben%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ccf4f345-f1e8-4216-bd21-1231214dc0ben%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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_Eb6PwjOArQqsbFDVgs6jgsx6vf9SRw-9v6_6H2bAXkw%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_Eb6PwjOArQqsbFDVgs6jgsx6vf9SRw-9v6_6H2bAXkw%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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/db55d5d9-8c21-4df2-b110-1cdf69cafd43%40chromium.org.
