On 2/6/24 3:59 AM, Nan Lin wrote:
Hi Mike,
Thanks for reviewing. Please see responses inline.
Nan
On Mon, Feb 5, 2024 at 9:33 PM Mike Taylor <miketa...@chromium.org> wrote:
Hi Nan,
On 2/2/24 5:00 AM, Nan Lin wrote:
Contact emails
lin...@chromium.org <mailto:lin...@chromium.org>,
johni...@chromium.org <mailto:johni...@chromium.org>
Explainer
Cross App and Web Attribution Measurement
<https://github.com/WICG/attribution-reporting-api/blob/main/app_to_web.md>
Specification
https://wicg.github.io/attribution-reporting-api/#cross-app-and-web
<https://wicg.github.io/attribution-reporting-api/#cross-app-and-web>
Summary
This is an extension to the Attribution Reporting API
<https://github.com/WICG/conversion-measurement-api>that has
already shipped.
Currently, the Attribution Reporting API
<https://github.com/WICG/conversion-measurement-api>supports
attributing events within a single browser instance. This
proposal expands the scope of attribution to allow attributing
conversions that happen on the web to events that happen off the
browser on the same device, within other applications such as
mobile applications, or vice-versa.
The proposal here leverages OS-level support for attribution. In
particular, it gives the developer an option to allow events on
the mobile web to be delegated to Android’s Privacy Sandbox
<https://developer.android.com/design-for-safety/privacy-sandbox/attribution>,
although support for other platforms could also be implemented in
the future.
Note that with this proposal new features shipped by the OS may
be implicitly supported without web API changes. For example,
Android may ship support for new registration fields not
supported in the existing Attribution Reporting API. Once a
developer elects to delegate events to the OS, there is no way
web-visible to introspect this.
Could you help me better understand the implications of this? Does
it just mean that debugging becomes challenging for new fields, or
are there other possible implications depending on new OS
features? Or possibly the web API lags behind what is possible via
the platform, until the web API catches up formally?
It’s not about debugging. Currently the web API and the Android’s
implementation of the Attribution Reporting API are expected to be
interoperable. However it’s possible that Android may ship support for
new registration fields in the OS-level API, which may or may not be
supported in the web API. The web API may lag behind, or even not
implement the new features at all. Once the event is delegated to the
OS, the attribution registration will be handled by the OS and
possibly using the new features in its API.
Thanks for the response! I'm still trying to understand what a
registration field is in the context of this API - is that a possible
future item added to the OS registration struct in
https://wicg.github.io/attribution-reporting-api/#os-registration?
(Apologies, I can't find any reference to "registration field" in the
draft spec...).
This can happen without web API change and there’s no way web-visible
to introspect this.
OK, so introspection here is not about debugging, but being able to make
decisions programmatically at runtime? Is that correct?
Blink component
Internals > AttributionReporting
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting>
TAG review
https://github.com/w3ctag/design-reviews/issues/724#issuecomment-1908353938
<https://github.com/w3ctag/design-reviews/issues/724#issuecomment-1908353938>
TAG review status
Pending
Risks
Interoperability and Compatibility
See the Attribution Reporting API I2S
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY>for
information on the other general measurement proposals in this space.
Private Click Measurement in Safari supports app to web
measurement
(https://webkit.org/blog/11529/introducing-private-click-measurement-pcm/#:~:text=App%2Dto%2DWeb%20Click%20Measurement
<https://webkit.org/blog/11529/introducing-private-click-measurement-pcm/#:~:text=App%2Dto%2DWeb%20Click%20Measurement>).
On iOS, some web to app measurement is supported via SKAdNetwork
(https://developer.apple.com/documentation/skadnetworkforwebads
<https://developer.apple.com/documentation/skadnetworkforwebads>).
There is currently no interop between these proposals and the
cross app web API for Attribution Reporting.
If Blink ever ships on iOS (at least in the EU, given recent
announcements by Apple), would it be possible to expect interop
between iOS and Android?
There’s no official position from WebKit yet, but there’s some concern
on the interoperability between Safari’s Private Click Measurement and
the Attribution Reporting API. We may expect similar concerns on
supporting Attribution Reporting API on iOS, therefore would not
expect interoperability between iOS and Android in the short term.
Thanks - ignoring the PCM API proposal, my question was more along the
lines of if it would be possible to implement this proposal were Blink
to be shipped on iOS (rather than the current Bling architecture), i.e.,
do the underlying iOS APIs allow for implementing this proposal. I don't
think this is a blocking concern today, but an interesting interop
concern for a future state.
Gecko: No official position
(https://github.com/mozilla/standards-positions/issues/791#issuecomment-1908359889
<https://github.com/mozilla/standards-positions/issues/791#issuecomment-1908359889>)
Any reason we didn't file a new issue w/ Mozilla (or TAG...), but
we did with WebKit?
We initially requested feedbacks for TAG, Mozilla and Webkit all in
the comments of the Attribution Reporting API requests as it’s an
extension of that API. We were then suggested by WebKit folks to file
a new issue instead as it’s easier for their system to handle new
requests.
WebKit: No official position
(https://github.com/WebKit/standards-positions/issues/307
<https://github.com/WebKit/standards-positions/issues/307>)
Web developers: Positive. Some testers are currently implementing
and providing feedback and more usage expected in 2024.
Developers have requested expansion of coverage of this feature
(example:
https://github.com/WICG/attribution-reporting-api/issues/1125
<https://github.com/WICG/attribution-reporting-api/issues/1125>).
Debuggability
The Attribution Reporting API utilizes DevTools and an internal
page (chrome://attribution-internals) to facilitate testing and
integration. The debugging information for OS registrations from
Chrome will be displayed in DevTools and the internal page as
well.<https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports>
Additionally, debug reports
<https://github.com/WICG/attribution-reporting-api/blob/main/app_to_web.md#optional-debugging-reports>are
supported for OS registrations. The Attribution Reporting API for
Android also implements a similar debugging reports framework
<https://developer.android.com/design-for-safety/privacy-sandbox/attribution-app-to-web#transitional-debugging>to
facilitate cross app and web testing.
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, Chrome OS, Android, and Android
WebView)?
The Attribution-Reporting-Support header is supported on all
platforms. Today, only Android offers a native Attribution
Reporting API, so the ability to register with the OS is only
supported on those platforms (Android and Android WebView).
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
The Attribution-Reporting-Support header is tested by web
platform tests, but the integration with OS is not as web
platform tests are not supported for Android.
Requires code in //chrome?
False
Estimated milestones
Chrome 123
Launch bug
https://launch.corp.google.com/launch/4238495
<https://launch.corp.google.com/launch/4238495>
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4994430156668928
<https://chromestatus.com/feature/4994430156668928>
Links to previous Intent discussions
Cross App and Web Attribution Measurement Intent to Experiment
<https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/gTvI5x-qex8>
Cross App and Web Attribution Measurement Intent to Extend
Experiment
<https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/0drGQpsOKh0>
Attribution Reporting API Intent to Ship
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY>
--
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/CA%2BVrgP%3DZDhgDguTkPXBnPOk8CpOVkxKHyBoeUR9%3D43c7p6wZuw%40mail.gmail.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgP%3DZDhgDguTkPXBnPOk8CpOVkxKHyBoeUR9%3D43c7p6wZuw%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/72092349-f193-419d-801d-7891ae1f8817%40chromium.org.
