On Fri, Dec 13, 2024 at 1:09 PM Mike Taylor <miketa...@chromium.org> wrote:
> Hey Paul, > > The UX of reviewing multiple PRs without the surrounding context is pretty > bad. Could you maybe give some code examples of using selectable reporting > IDs with and without B&A? > This document has various examples of using selectable reporting IDs: https://developers.google.com/privacy-sandbox/private-advertising/protected-audience-api/use-case/deals There shouldn't be significant usage differences between with and without B&A, except that with B&A, generateBid() gets the selectable reporting IDs from the trusted bidding signals rather than the interest group. This difference arises from wanting to keep the blob returned from navigator.getInterestGroupAdAuctionData() as small as possible. With or without B&A, any selectable reporting IDs returned from generateBid() are checked for k-anonymity and verified to be present in the interest group. > Also, more meta question: are there scenarios where you would ship a > feature to PA but not ship support for PA/B&A? > I can't think of any. I think we always design PA features so they'll be feasible on B&A. > On 12/13/24 10:42 AM, Paul Jensen wrote: > > Contact emails > > pauljen...@chromium.org > > > Explainer > > For original Protected Audience Selectable Reporting IDs support: > https://github.com/WICG/turtledove/pull/1237 > > > Specification > > Web spec: https://github.com/WICG/turtledove/pull/1348 > > Protocol spec: > https://github.com/privacysandbox/draft-ietf-bidding-and-auction-services/pull/14 > > > Summary > > Chrome already provides a selectable reporting ID to the Protected > Audience API > <https://groups.google.com/a/chromium.org/g/blink-dev/c/1cWqBPHngd0> to > facilitate event-level Protected Audience auction reporting on Deal and > Seat IDs which are sometimes associated with programmatic deals(aka private > marketplace). This feature adds Chrome support for selectable reporting IDs > for Protected Audience ad selection auctions run on Bidding and Auction > Services (B&A) > <https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md> > . > > > 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 > > For Protected Audience Bidding and Auction Services: > https://github.com/w3ctag/design-reviews/issues/1009 > > > TAG review status > > Completed for Protected Audience, resolved unsatisfied. > > > Risks Interoperability and Compatibility > > Feature represents optional new behavior that shouldn’t break existing > usage. > > > Gecko & WebKit: For Protected Audiences in general - Negative from Mozilla > <https://github.com/mozilla/standards-positions/issues/770#issuecomment-2432124085>. > No signal from Webkit > <https://github.com/WebKit/standards-positions/issues/158#issuecomment-2432121278> > . > > > Edge: Edge is running an Origin Trial of the Ad Selection API > <https://github.com/WICG/privacy-preserving-ads/blob/main/README.md> > which shares a Web API and services protocol with PA. > > > Web developers: Selectable reporting IDs in Protected Audience 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 > > On-device API surfaces should be debuggable in Chrome DevTools, and we’ve > added extensive mechanisms for debugging > <https://github.com/privacysandbox/fledge-docs/blob/main/debugging_protected_audience_api_services.md> > Bidding > and Auction services > <https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md#related-documents> > . > > > 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> > ? > > We plan to add WPTs to cover this API shortly. We already have WPTs for > Protected Audience Bidding and Auction Services and for Protected Audience > selectable reporting IDs and will extend these accordingly. > > > Flag name on chrome://flags > > None > > > Finch feature name > > EnableBandADealSupport > > > Requires code in //chrome? > > False > > > Estimated milestones > > Shipping on desktop and Android in M132. > > > Anticipated spec changes > > None > > > Link to entry on the Chrome Platform Status > > http://chromestatus/6112108595642368 > > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > -- > 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 visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnv-kyAnRATmzj1mVNKQSOJockCt_bs%3D%3Da5K75E%2BiMArA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnv-kyAnRATmzj1mVNKQSOJockCt_bs%3D%3Da5K75E%2BiMArA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrk5ratpoTq0g9Gj2reiR9zYkNHVS2YMubWt7FGG3MO30Q%40mail.gmail.com.
