Contact [email protected], [email protected] Explainer
Browser API: https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md Bidding & Auction Services: https://github.com/privacysandbox/fledge-docs/blob/main/bidding_auction_services_api.md Specification None Summary The Protected Audience API <https://github.com/WICG/turtledove/blob/main/FLEDGE.md> (formerly known as FLEDGE) is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed so third parties cannot track user browsing behavior across sites. This proposal, the Protected Audience Bidding & Auction Services proposal, outlines a way to allow Protected Audience computation to take place on cloud servers in a Trusted Execution Environment, rather than running locally on a user's device. Blink component Blink>InterestGroups <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EInterestGroups> Motivation The Protected Audience API provides a privacy advancing API to facilitate interest group based and custom audience advertising. The Protected Audience Bidding & Auction Services proposal moves computations to cloud servers to help optimize the Protected Audience auction, to free up computational cycles and network bandwidth for a device. This can address one of the potential risks to the Protected Audience API <https://groups.google.com/a/chromium.org/g/blink-dev/c/0VmMSsDWsFg/m/_0T5qleqCgAJ#:~:text=Browser%20Performance,investigation%2C%20and%20improvement.> . Initial public proposal (for Protected Audience) https://discourse.wicg.io/t/advertising-to-interest-groups-without-tracking/ TAG review Protected Audience: https://github.com/w3ctag/design-reviews/issues/723 TAG review status Requested for Protected Audience API. Risks Interoperability and Compatibility The Protected Audience design draws on many discussions and proposals, most notably: - The original TURTLEDOVE <https://github.com/WICG/turtledove/blob/master/Original-TURTLEDOVE.md> from Chrome. - SPARROW <https://github.com/WICG/sparrow> from Criteo, which entered WICG incubation jointly <https://discourse.wicg.io/t/advertising-to-interest-groups-without-tracking/4565> with TURTLEDOVE. - Outcome-based TURTLEDOVE <https://github.com/WICG/turtledove/blob/master/OUTCOME_BASED.md> and Product-level TURTLEDOVE <https://github.com/WICG/turtledove/blob/master/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/master/TERN.md> from NextRoll. PARAKEET <https://github.com/WICG/privacy-preserving-ads/blob/main/Parakeet.md> from Microsoft accomplishes similar goals also using trusted servers, 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 in this proposal the Bidding & Auction services are run on trusted servers only. Gecko: No response yet on Protected Audience <https://github.com/mozilla/standards-positions/issues/770> WebKit: No response yet on Protected Audience <https://github.com/WebKit/standards-positions/issues/158> Web developers: Significant interest from many web advertising technology developers. 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 the Protected Audience design draws from. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> ? Not yet Link to entry on the Chrome Platform Status https://chromestatus.com/feature/4649601971257344 <https://chromestatus.com/feature/5733583115255808> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnSdvf7RgK2wxsmC6rWc8eRoqDZOvgwVFuEx1r2nqmAJg%40mail.gmail.com.
