Hi, Two questions: * Can you demonstrate any substantial progress <https://www.chromium.org/blink/launching-features/#step-3-optional-origin-trial:~:text=An%20initial%20origin,previous%20extension%20request.> since the original OT request towards the requirements for shipping the feature? * Could you share any learnings or experimental feedback gathered so far?
On Wed, Oct 4, 2023 at 10:20 AM Nan Lin <lin...@chromium.org> wrote: > Contact emails > > johni...@chromium.org, csharri...@chromium.org, lin...@chromium.org > > Explainer > > 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-we> > > > Summary > > 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, within other applications such as > mobile applications, or vice-versa. > > The proposal here takes advantage of OS-level support for attribution. In > particular, it gives the developer an option to allow events on the mobile > web to be joinable with events in 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. > > The experiment will be on Android T > <https://developer.android.com/about/versions/13>, S > <https://developer.android.com/about/versions/12>, and R > <https://developer.android.com/about/versions/11> devices only. > > We are planning to extend the experiment for 4 more milestones M120 to > M123 inclusive. > > > 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 (Attribution > Reporting API) > > TAG review status > > Pending > > Risks > Interoperability > > Web developers: Some testers are currently implementing and providing > feedback, and commitment from an additional 5+ testers to begin engagement > later this year. > > > Goals for experimentation > > For experimentation with the new extension of the Attribution Reporting > API, we hope to see that the measurement data made available through the > API provides useful ad conversion data cross app and web, and that > developers are able to work against both the Chrome and Android Attribution > APIs. > > > Justification for extension > > Cross app web Attribution Reporting API is currently enabled on Android T+ > devices on the following platforms/channels: > > Android: Canary/Dev (50%), Beta (50%), Stable (99%) > > Android WebView: Canary/Dev (50%), Beta (50%), Stable (10%) > > The Android API itself is available on 90% on Android T. > > Currently the page load for the Cross App Web Attribution Reporting API is > at 0.0128% > <https://chromestatus.com/metrics/feature/popularity#AttributionReportingCrossAppWeb>, > which we feel also mitigates burn-in risk. > > The experiment on Android WebView is still being ramped up with a few > planned enhancements. We plan to start the experiment on Android S and R > devices soon as well. > > Given the complexity of using the new Web API in conjunction with the new > Android APIs, partner testing has taken longer than expected. With this > extension, we hope to get additional data on the usefulness of this API and > insights into any issues in the system. > > Ongoing technical constraints > > None. > > > Debuggability > > The Attribution Reporting API utilizes DevTools and an internal page > (chrome://attribution-internals) to facilitate testing and integration. Debug > reports > <https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports> > are supported (and when configured in a third-party context, require > third-party cookies to be available). > > > The debugging information for OS registrations is displayed in DevTools > and in chrome://attribution-internals as well. Android Measurement is also > implementing a similar debugging reports framework 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)? > > No, only on Android and Android WebView for this experiment. > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ? > > No, web platform tests are not supported for Android. > > Flag name > > privacy-sandbox-ads-apis > > Requires code in //chrome? > > No. > > Launch bug > > https://launch.corp.google.com/launch/4238495 > > Estimated milestones > > We’d like to extend the origin trial for 4 additional milestones, with the > extension starting in M120 continuing through M123. The experiment is > therefore running from Chrome M114 through M123. > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/4994430156668928 > > Links to previous Intent discussions > > Cross App Web Attribution Measurement I2E > <https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/gTvI5x-qex8> > > -- > 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%2BVrgPmJasGYbdxfO9vkT%3D6jqCub0kefGP9a9im_ta3cv3ig-Q%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPmJasGYbdxfO9vkT%3D6jqCub0kefGP9a9im_ta3cv3ig-Q%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/CAOMQ%2Bw-1fcntT2-1F9fOWqvUjo-c1bp8F3BM29Q8PScDrvOZ9Q%40mail.gmail.com.
