*Contact emails* pauljen...@chromium.org, kle...@google.com, ajvelasq...@google.com
Explainer https://github.com/WICG/turtledove/blob/master/FLEDGE.m <https://github.com/WICG/turtledove/blob/master/FLEDGE.md>d Specification https://wicg.github.io/turtledove Summary The Protected Audience API (formerly known as FLEDGE) provides a method of interest-group advertising without having to track individual users’ detailed browsing history as is done today with third-party cookies. Additional advantages over cookies include time limits on group membership, better user controls, and more user transparency. Blink component Blink>InterestGroups <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EInterestGroups&can=2> TAG review https://github.com/w3ctag/design-reviews/issues/723 TAG review status Pending since March 2022 Risks Compatibility This is not a breaking change. To use it, sites will need to call the Protected Audience API. There is no change to existing behavior for sites not calling the API. It’s worth noting that the spec uses WebIDL to describe the script runners <https://wicg.github.io/turtledove/#script-runners> but the implementation does not. There may be minor compat issues as we align the implementation with the WebIDL semantics over time. Interoperability Gecko: No signal, requested March 2023 <https://github.com/mozilla/standards-positions/issues/770> WebKit: No signal, requested March 2023 <https://github.com/WebKit/standards-positions/issues/158> Edge: Edge explored interest group based advertising, namely with the PARAKEET proposal <https://github.com/WICG/privacy-preserving-ads/blob/main/Parakeet.md>. PARAKEET shares much of its API with Protected Audience but as discussed in TPAC 2022 <https://docs.google.com/presentation/d/1QQgrm4oaRRRBr1gfvKj7D8rS2EW8kRgRUHPscvR8BNo/edit#slide=id.g15545e7b627_0_173>, involves proxying data to non-trusted servers in real-time whereas Protected Audience does not have long term plans to do this. Web developers: Significant interest from many web developers. Significant Origin Trial participation <https://github.com/WICG/turtledove/blob/main/fledge-tester-list.md>. WICG FLEDGE calls <https://github.com/WICG/turtledove/issues/88> are heavily attended. Interest in Protected Audience is further evidenced by the many related discussions and proposals that Protected Audience’s design draws from, most notably: - The original TURTLEDOVE <https://github.com/WICG/turtledove/blob/main/Original-TURTLEDOVE.md> from Chrome. - SPARROW <https://github.com/WICG/sparrow> from Criteo. - Outcome-based TURTLEDOVE <https://github.com/WICG/turtledove/blob/main/OUTCOME_BASED.md> and Product-level TURTLEDOVE <https://github.com/WICG/turtledove/blob/main/PRODUCT_LEVEL.md> from RTB House. - Dovekey <https://github.com/google/ads-privacy/tree/master/proposals/dovekey> from Google Ads. - PARRROT <https://github.com/prebid/identity-gatekeeper/blob/master/proposals/PARRROT.md> from Magnite. - TERN <https://github.com/WICG/turtledove/blob/main/TERN.md> from NextRoll. Demo linkhttps://developer.chrome.com/docs/privacy-sandbox/fledge-api/#demo Debuggability To learn more about debugging Protected Audience in Chrome please follow these links: https://developer.chrome.com/blog/fledge-api/#debugging https://developer.chrome.com/blog/fledge-api/#observe-fledge-events Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? All except WebView Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ? We've tested all of the primary functionality in WPT. This API has a lot of surface area and so we're continuing to add platform tests over time. https://wpt.fyi/results/?q=fledge Flag name InterestGroupStorage,AdInterestGroupAPI,Fledge,AllowURNsInIframes,BiddingAndScoringDebugReportingAPI Requires code in //chrome? Yes, for settings UI controls and k-anonymity server communication. Estimated milestones Has been in Origin Trial since M101. We intend to start an incremental ramp to 100% in Stable with Chrome Release M115. Anticipated spec changes - We’re addressing some remaining TODOs and specifying some recently added non-breaking features (e.g. #304 <https://github.com/WICG/turtledove/issues/304>, #305 <https://github.com/WICG/turtledove/issues/305>, #310 <https://github.com/WICG/turtledove/issues/310>, #166 <https://github.com/WICG/turtledove/issues/166>). - Moving beyond our core use cases, we anticipate the need to support new functionality going forward. We don’t currently anticipate changes that would break backwards compatibility. - Support for Bidding and Auction services <https://groups.google.com/a/chromium.org/g/blink-dev/c/bGd_nPuUrUg/m/j39WQ7e2AwAJ> is in progress. This is a non-breaking additional feature. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5733583115255808 Links to previous Intent discussions Intent to Prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/w9hm8eQCmNI Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/0VmMSsDWsFg/m/_0T5qleqCgAJ Intent to Extend Origin Trial: https://groups.google.com/a/chromium.org/g/blink-dev/c/SD8Ot2gpz4g/m/A9uA-_cGAwAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/gpmaOi3of_w/m/SyMclFhMAAAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/CBrV-2DrYFI/m/RTojC6kHAgAJ -- 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/CABQTWrn8eM3wOtUY3RzmDrt7SVxR_y_6Fo02bJ%2BF1bzbwpFfkQ%40mail.gmail.com.
