Intent to Extend Experiment: Privacy Sandbox Ads APIs through M110

[Josh Karlin‏]

Greetings. We would like to extend the Privacy Sandbox Ads APIs experiment for all APIs contained in the unified origin trial including: Topics, FLEDGE, Fenced Frames, Attribution Reporting, and Shared Storage.

We are sending a single intent for the extension because the rationale is shared among each of the APIs. Functionally, we are still asking for approval to extend each of the four API's experiments independently.

Contact emails
john...@chromium.org, jka...@chromium.org, paulj...@chromium.org, shiva...@chromium.org

Explainer
Attribution Reporting: https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md
Fenced Frames: https://github.com/WICG/fenced-frame/tree/master/explainer
FLEDGE: https://github.com/WICG/turtledove/blob/master/FLEDGE.md
Shared Storage: https://github.com/WICG/shared-storage
Topics API: https://github.com/patcg-individual-drafts/topics/blob/main/README.md

Summary
A collection of APIs to facilitate advertising: Attribution Reporting, Fenced Frames, FLEDGE, Shared Storage and Topics.
 
Link to “Intent to Experiment” blink-dev discussion
Attribution Reporting:
https://groups.google.com/a/chromium.org/g/blink-dev/c/jEnNpideO1Y/m/nlEDdjmnCgAJ
Fenced Frames: https://groups.google.com/a/chromium.org/g/blink-dev/c/y6G3cvKXjlg/m/DSNrBtxyAgAJ
FLEDGE:
https://groups.google.com/a/chromium.org/g/blink-dev/c/0VmMSsDWsFg/m/_0T5qleqCgAJ
Shared Storage: https://groups.google.com/a/chromium.org/g/blink-dev/c/jDx8z5a6ovk/m/H6w1UO-uBAAJ
Topics API: https://groups.google.com/a/chromium.org/g/blink-dev/c/oTwd6VwCwqs/m/jPkW3T-mCgAJ

Unified OT Thread:
https://groups.google.com/a/chromium.org/g/blink-dev/c/Vi-Rj37aZLs/m/wzeBWfxxEgAJ
 
Goals for experimentation
Unchanged.

Experimental timeline
We'd like to extend the origin trial for 3 additional milestones, with the extension starting in 108 continuing through Chrome 110. The initial experiment is running from Chrome 101 through 107.

Any risks when the experiment finishes?
None. The unified origin trial is only available for a subset of users requiring participants to perform feature detection to use the APIs.

Reason this experiment is being extended
We plan to address several points of feedback raised in the next several milestones, and give the ecosystem more time in stable channels to continue their experiments.. As a result, this will give developers the opportunity to perform extensive testing on higher traffic (within traditional experiment guidance).

We are requesting this change well in advance of the initial end date to make it clear we intend to support meaningful testing within Chrome Stable, and plan to release a number of improvements and bug fixes for the APIs over the next few milestones. These improvements include, but are not limited to, the following:

Attribution Reporting

• Modified default for Attribution permissions policy
• Service worker interception with redirects now uses the correct URL
• Fixed renderer-side crashes with using the API in an iframe sandbox

Fenced Frames

• Support for ARA to be invoked from inside Fenced Frames
• Completely moved to MPArch based Fenced Frames which is a more secure and private architecture as compared to the architecture based on shadowDOM iframes

FLEDGE

• Large scale latency optimizations

Shared Storage

• Support for querying how much budget is left and how much time is left before reset within the worklet.

Topics

• Support for sending topics in request headers of documents and fetch requests, and the ability to set that the target site has seen the topic via response headers
• Support for retrieving topics via the JS API, without modifying state

Additionally, we have also received feedback that developers would prefer the Origin Trial be extended well ahead of the end date to allow a larger buffer for updating Origin Trial tokens.

Ongoing technical constraints
Please see each APIs initial Intent to Experiment.

Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)?
Please see each APIs initial Intent to Experiment.

Link to entry on the feature dashboard
Attribution Reporting: https://chromestatus.com/feature/6412002824028160
Fenced Frames: https://chromestatus.com/feature/5699388062040064
FLEDGE: https://chromestatus.com/feature/5733583115255808
Shared Storage: https://chromestatus.com/feature/6256348582903808
Topics: https://chromestatus.com/feature/5680923054964736

Unified Feature Dashboard: https://chromestatus.com/feature/5100526168440832

Thanks,

Josh

[Josh Karlin‏]

Ah, I also meant to provide a link to the report on summarized feedback we've received on the experiments to date.

Josh

[Yoav Weiss‏]

LGTM to extend the experiment M108-M110 inclusive

Thanks for the detailed reports of addressed feedback. I'd also like to note that at least a few of the experimented APIs made good progress on draft specs.

For the next extension, it would be good to show progress towards a draft spec on the ones remaining :)

--
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/CAANMuaOyq%3DUr7Ut30ao6Yywg4nCx%3DoRk%3DW9vTeAnwJvM3vCMpw%40mail.gmail.com.