[blink-dev] Intent to Ship: Attribution Reporting Feature: Prevent Coalescing of Headers

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

[blink-dev] Intent to Ship: Attribution Reporting Feature: Referrer Policy for Attributionsrc Requests

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Additional Verbose Debug Reports, Further Gating Source Verbose Debug Reports, Splitting the Attribution Rate Limit

-limit and source-destination-rate-limit errors, since >> they would most likely be interested in also understanding any error >> signals that may be impacting their conversions as well. >> >> Thanks, >> >> Akash >> >> >> On Thursday, Ap

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Additional Verbose Debug Reports, Further Gating Source Verbose Debug Reports, Splitting the Attribution Rate Limit

her for rate limits?) > On 4/19/24 12:51 PM, 'Akash Nadan' via blink-dev wrote: > > Contact emails > > akash...@google.com, lin...@chromium.org, john...@chromium.org > > Explainer > > Attribution Reporting with event-level reports > <https://github.com/WICG

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Additional Verbose Debug Reports, Further Gating Source Verbose Debug Reports, Splitting the Attribution Rate Limit

hallenging to review 4 features > at once. > > (Aside: it seems like this particular intent could have been split into > 2... one for 2 debug report features, and another for rate limits?) > On 4/19/24 12:51 PM, 'Akash Nadan' via blink-dev wrote: > > Contact emails

[blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Additional Verbose Debug Reports, Further Gating Source Verbose Debug Reports, Splitting the Attribution Rate Limit

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

[blink-dev] Re: Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

Hi Yoav, the reasoning behind this change is that there is a privacy gap with the current attribution flow and position of the source deactivation logic. The current position of the source deactivation logic makes it possible for API callers to identify when a source is noise (versus a real

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

those comparisons, although given that this scenario is rare, it may not > cause any issues or change in comparison. > > Let me know if you have any other questions. > > Thanks, > Akash > > > On Wednesday, March 20, 2024 at 8:30:31 AM UTC-7 Mike Taylor wrote: > >>

Re: [blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

in those comparisons, although given that this scenario is rare, it may not cause any issues or change in comparison. Let me know if you have any other questions. Thanks, Akash On Wednesday, March 20, 2024 at 8:30:31 AM UTC-7 Mike Taylor wrote: > On 3/18/24 7:17 PM, 'Akash Nadan' via blink-

[blink-dev] Intent to Ship: Attribution Reporting Feature Bundle: Header Error Debug Reports, Preferred Platform field, Changing Source Deactivation

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

Re: [blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

it would be in >> https://source.chromium.org/chromium/chromium/src/+/main:android_webview/browser/aw_field_trials.cc;l=72-73 >> ). >> On 2/23/24 1:38 PM, 'Akash Nadan' via blink-dev wrote: >> >> Hi Peter, >> >> The Attribution Reporting Web API is curren

Re: [blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

ion Reporting API is supported in Android WebView, > why won't these extensions be? > > Thanks, > Peter > > On Thu, Feb 22, 2024 at 8:32 PM 'Akash Nadan' via blink-dev < > blin...@chromium.org> wrote: > >> Hi All, >> >> We did not do an OT for thes

[blink-dev] Re: Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

Hi All, We did not do an OT for these features. But we have discussed and collected feedback regarding these features with multiple ad-techs and have shared these features during the WICG (web platform incubator community group) weekly calls. Thanks, Akash On Wednesday, February 21, 2024 at

[blink-dev] Intent to Ship: Attribution Reporting API Features (Trigger Data Customization and Aggregatable Value Filters)

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

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

3 12:37 PM, 'Akash Nadan' via blink-dev 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/EVE

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

Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

Re: [blink-dev] Intent to Ship: Attribution Reporting API feature (further gating for trigger verbose debug reports)

. Thanks, Akash On Monday, November 6, 2023 at 9:40:50 AM UTC-8 Mike Taylor wrote: > > On 11/3/23 6:12 PM, 'Akash Nadan' via blink-dev wrote: > > > Contact emails > > lin...@chromium.org, john...@chromium.org > > Explainer > > Attribution Reporting with event-lev

[blink-dev] Intent to Ship: Attribution Reporting API feature (further gating for trigger verbose debug reports)

Contact emails lin...@chromium.org, johni...@chromium.org Explainer Attribution Reporting with event-level reports Attribution Reporting API with Aggregatable Reports

[blink-dev] Intent to Ship: Attribution Reporting features (change registration limit, remove 1hr delay)

Contact emails johni...@chromium.org, csharri...@chromium.org Explainer https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md