On Fri, Jun 7, 2024 at 8:12 PM 'Akash Nadan' via blink-dev < blink-dev@chromium.org> wrote:
> Contact emails > > akashna...@google.com, lin...@chromium.org, johni...@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/ > > 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 changes to the Attribution Reporting API > focused on: > > - > > improving debugging capabilities > > > This change is based on ad-tech feedback and the need to support debugging > capabilities after third-party cookie deprecation. > > Currently the API supports debug reports that are tied to third-party > cookies. In order for an API caller to receive a debug report of any kind > they need to make sure a specific third-party cookie (i.e. ar_debug) is > properly set. The API will check to make sure this cookie is set before > providing any kind of debug report. Once third-party cookies are deprecated > these debug reports will no longer be available. > > This change is so the API can continue to provide debugging information > after third-party cookie deprecation when the current debug reports that > are tied to third-party cookies are no longer available. This is a new > report type that is not tied to third-party cookies and provides similar > debug information. This feature allows API callers to request and receive > debug signals in aggregate form. This feature is very similar to current > Aggregate Reports supported by the API, except these new reports will be > specifically for debug signals. > Can you expand on what debug signals are being aggregated? Are they developer-defined somehow? > > This new feature will allow API callers to continue receiving debugging > information even after third-party cookie deprecation. > > Explainer/Spec changes > > 1. > > Explainer: > > https://github.com/WICG/attribution-reporting-api/blob/main/aggregate_debug_reporting.md > 2. > > Spec: > 1. > > https://github.com/WICG/attribution-reporting-api/pull/1310 > 2. > > https://github.com/WICG/attribution-reporting-api/pull/1292 > > > Risks > Interoperability and Compatibility > > This is an optional and fully backwards compatible change. This feature > provides a new mechanism for receiving debugging information and does not > break any pre-existing API or web functionality. > > Gecko: No signal (Original request: > https://github.com/mozilla/standards-positions/issues/791) > > WebKit: No signal (Original request: > https://github.com/WebKit/standards-positions/issues/180) > > Web developers: > https://github.com/WICG/attribution-reporting-api/issues/705 > > > 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? > > No > > > 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 of Chrome 127 > <https://chromiumdash.appspot.com/schedule>. > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5086433709916160 > > 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> > > 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/588cb91a-d7df-4796-8b6d-d1e406f64008n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/588cb91a-d7df-4796-8b6d-d1e406f64008n%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/CAOmohSKkGS8n8ZjK6sDDqFA0isLqkHTVSkEFYwL%2BVsE-xDOiCg%40mail.gmail.com.
