Thanks Akash. Follow up question: besides reading blink-dev, have we
otherwise made relevant ad techs aware of the changes coming to reports?
On 3/22/24 5:52 PM, Akash Nadan wrote:
Hi Mike, the implications of an adtech getting different reports in
some circumstances (or no report where they previously would have
gotten one) are mainly when they are comparing these reports to other
mechanisms they may be using for conversion measurement. They may see
a slight difference 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-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/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>
Summary
We are landing the following changes to the Attribution Reporting
API focused on:
*
additional debugging capabilities by supporting parsing
failure debug reports
*
improving API ergonomics by supporting a field to specify
preferred registration platform
*
improving privacy
Explainer/Spec changes
1. Response header errors debug reports
<https://github.com/WICG/attribution-reporting-api/pull/1180>
2. Supporting preferred platform for cross app attribution
<https://github.com/WICG/attribution-reporting-api/pull/1161>
3. Move source deactivation step after top level filter matching
<https://github.com/WICG/attribution-reporting-api/pull/851>
Risks
Interoperability and Compatibility
(1 <https://github.com/WICG/attribution-reporting-api/pull/1180>)
Header errors debug reports and (2
<https://github.com/WICG/attribution-reporting-api/pull/1161>)
preferred platform are both fully backwards compatible changes
and are optional features. (3
<https://github.com/WICG/attribution-reporting-api/pull/851>) The
source deactivation change has very low compatibility risk
because it does not require any developer changes and only
results in ad techs getting different reports in cases where a
user had multiple interactions across different ads when rate
limits in the API are hit, which should be very rare.
I think I understand why the potential compat issue should be rare
based on reading
https://github.com/WICG/attribution-reporting-api/issues/842#issuecomment-1612096408,
but it's not super clear to me what the implications for "adtechs
getting different reports in some circumstances (or not report
where they previously would have gotten one)" are. Mind clarifying?
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The attribution reporting feature bundle 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 bundle is anticipated to ship as part ofChrome 124
<https://chromiumdash.appspot.com/schedule>.
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5117902786396160
<https://chromestatus.com/feature/5117902786396160>
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>
--
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/c691e58e-bfbb-492b-b235-6facc6d12062n%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c691e58e-bfbb-492b-b235-6facc6d12062n%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/04c30c73-f47e-4d3b-a885-872ad6385d77%40chromium.org.
