Intent to Ship: Attribution Reporting Features (Reduced Aggregate Delays, Event-Level Report Epsilon Field, Reserved Keys)

[Akash Nadan]

Contact emails

akash...@google.com, lin...@chromium.org, john...@chromium.org

Explainer

Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification

https://wicg.github.io/attribution-reporting-api/

Blink component

Internals > AttributionReporting

Summary

We plan on landing the following changes to the Attribution Reporting API focused on:

• reducing transmission loss by supporting reduced aggregatable report delays with trigger context ID

• additional API configurability by supporting an event-level reporting epsilon field

• improve extensibility of the API by failing registrations when encountering reserved keys

Explainer/Spec changes

• Reduce aggregate delays and support trigger context ID 

• Event-level reporting epsilon field 

• Reserve keys starting with an underscore 

Risks
Interoperability and Compatibility

The first two changes (1. supporting reduced aggregatable report delays and 2. supporting event-level reporting epsilon field) are fully backwards compatible changes. Both of these features are optional features.

The third change (3. failing registrations when encountering reserved keys) is backwards incompatible. Any keys starting with an underscore will cause the registration to fail. We have checked the usage of such keys, and the data shows that keys that start with an underscore are not currently used. Therefore this change will most likely not break any current registrations or have minimal impact.

              

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

All except Android WebView

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

Yes

Estimated milestones

Chrome 121

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5181611197071360

Links to previous Intent discussions

Previous I2S: 

Intent to Ship: Attribution Reporting API

Intent to Ship: Attribution Reporting features M117

Intent to Ship: Attribution Reporting features M118

Intent to Ship: Attribution Reporting features M119

Intent to Ship: Attribution Reporting features M120

[Mike Taylor]

Hi Akash,

Can you request reviews for the various review gates on your chromestatus entry?

thanks,
Mike

--
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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e20140d1-74ea-4535-b20a-9bfd89e27954n%40chromium.org.

[Akash Nadan]

Hi Mike,

I have requested the various reviews needed.

Thanks,

Akash

[Rick Byers]

LGTM1

On the interoperability risks front I see there's still no official position on the API from Mozilla or WebKit. 

[Mike Taylor]

LGTM2

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9PJTQ%2Bv3saBbBs3rzJT%3DrZPR35EQfVU%2BgYt-HUtTgzaQ%40mail.gmail.com.

[Yoav Weiss]

LGTM3

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

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e20140d1-74ea-4535-b20a-9bfd89e27954n%40chromium.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.