Also to clarify, we will remove the origin trial requirement for all platforms.
The feature will be shipped on all platforms except for Android WebView. Android WebView may have a slower rollout using Finch. Thanks, Nan On Fri, Feb 2, 2024 at 8:00 AM Nan Lin <lin...@chromium.org> wrote: > Contact emails > > lin...@chromium.org, 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 > > 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. > > > 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 > > 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). > On iOS, some web to app measurement is supported via SKAdNetwork ( > https://developer.apple.com/documentation/skadnetworkforwebads). There is > currently no interop between these proposals and the cross app web API for > Attribution Reporting. > > Gecko: No official position ( > https://github.com/mozilla/standards-positions/issues/791#issuecomment-1908359889 > ) > > WebKit: No official position ( > 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). > > 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 > > Link to entry on the Chrome Platform Status > > 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%3DqVQ6-80XQXkJAVQ6c4e%3Do%2B%2B562Kk3k81CB9Ow_pG%2B5w%40mail.gmail.com.
