Developers interested in the Topics API can also join the Topics API announcements group for updates and announcements.
The intent of the Topics API is to provide callers (including third-party ad-tech or advertising providers on the page that run script) with coarse-grained advertising topics that the page visitor might currently be interested in. These topics will supplement the contextual signals from the current page and can be combined to help find an appropriate advertisement for the visitor.
Gecko: issue – requested March 17th 2022
WebKit: webkit-dev thread – requested March 17th 2022
Web developers: Lots of interest in issues in the explainer. Concerns center around utility. Balancing privacy/utility and making tweaks to the algorithms so that we get this right is what the OT is all about.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
The intent is for experimenters to try Topics out and see how it performs for them. We expect there to be bumps along the road toward optimizing privacy and utility trade-offs. We also expect it may be necessary to change parameters and algorithms along the way (e.g., we’re already having discussions around adding Topics in request headers and weighting topics by frequency). So please experiment and provide feedback on the issue tracker to help us improve it.
The origin trial for this experiment will be shared among various Privacy Sandbox APIs. Our goal is to allow for coordinated experiments to be run by multiple different sites, across multiple APIs in one OT.
This shared origin trial, Privacy Sandbox Ads APIs, will be a third-party origin trial. To ensure that developers can run coordinated experiments without concern for exceeding page load usage thresholds, this Origin Trial will be available for a subset of users by default. Therefore, it will be necessary to feature test to ensure that the API surface you want to use is available after providing your OT token. A second advantage of this configuration is that different experimenters will experiment with the same users, which enables coordination for APIs like FLEDGE across third parties.
There are no particular debugging APIs made available or dev-tools integrations for this OT.
All but webview.
Not yet, but those tests are coming.
We hope to start the Origin Trial sometime during M101 beta. We plan to continue the Origin Trial until at least M104 to give developers time to test the API and provide feedback. Once we are confident that the APIs are working properly, we will transition the OT from beta to stable channel.
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/b845db21-f158-4bf3-9109-7f4665126ec1n%40chromium.org
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/CAANMuaNXE3KYymq%3Dd0jcOmw%2Br2si_DOJK4cc%2BqMCU8mCoQBWTA%40mail.gmail.com.