Contact emails pauljen...@chromium.org
Explainer https://github.com/WICG/turtledove/pull/1237 https://github.com/WICG/turtledove/pull/1265 Specification https://github.com/WICG/turtledove/pull/1275 Summary Adtechs often use “deals” (aka private marketplace) when auctioning ad space on web pages. This can facilitate a seller and a buyer negotiating a deal together, for example a bulk-buy deal with the seller offering a specific discount if the buyer agrees to buy at least a specific number of impressions for a specific ad campaign. Deals are often referred to, at auction time, using a deal ID which is an identifier that buyers and sellers can use to refer to a particular deal that they negotiated previously. This proposal adds a selectable reporting ID to the Protected Audience API to facilitate using deals with the Protected Audience ad selection auctions. The new reporting ID is held to the same joint k-anonymity requirement of existing reporting IDs so there is no impact to user privacy. Blink component Blink>InterestGroups <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestGroups> TAG review For Protected Audience: https://github.com/w3ctag/design-reviews/issues/723 TAG review status Completed for Protected Audience, resolved unsatisfied. Risks Interoperability and Compatibility This feature represents optional new behavior that shouldn’t break existing usage. Gecko & WebKit: No signal on parent proposal, Protected Audience. Asked in the Mozilla forum here <https://github.com/mozilla/standards-positions/issues/770>, and in the Webkit forum here <https://github.com/WebKit/standards-positions/issues/158> . Edge: Edge has announced plans to support the Ad Selection API <https://github.com/WICG/privacy-preserving-ads/blob/main/README.md> which shares much of its API surface with Protected Audience. Web developers: Requested by 6+ companies (including Microsoft Ads) in 4 GitHub issues (1 <https://github.com/WICG/turtledove/issues/873>,2 <https://github.com/WICG/turtledove/issues/716>,3 <https://github.com/WICG/turtledove/issues/682>,4 <https://github.com/WICG/turtledove/issues/686>). Debuggability The selectable reporting IDs should be visible in the DevTools Application -> Storage -> Interest Groups tab and their selection should be debuggable via DevTools debugging of Protected Audience bidding and scoring scripts. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)? It will be supported on all platforms that support Protected Audience, so all but WebView. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ? Yes <https://chromium-review.googlesource.com/c/chromium/src/+/5868409> Flag name on chrome://flags None Finch feature name FledgeAuctionDealSupport Requires code in //chrome? False Estimated milestones Shipping on desktop and Android in M130. Anticipated spec changes None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5091868904521728?gate=5207096837275648 -- 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/b974a1df-6a03-413e-9d2c-2fadd0844ae0n%40chromium.org.
