For original Protected Audience Selectable Reporting IDs support: https://github.com/WICG/turtledove/pull/1237
Web spec: https://github.com/WICG/turtledove/pull/1348
Protocol spec: https://github.com/privacysandbox/draft-ietf-bidding-and-auction-services/pull/14
Chrome already provides a selectable reporting ID to the Protected Audience API 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).
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
Completed for Protected Audience, resolved unsatisfied.
Feature represents optional new behavior that shouldn’t break existing usage.
Gecko & WebKit: For Protected Audiences in general - Negative from Mozilla. No signal from Webkit.
Edge: Edge is running an Origin Trial of the Ad Selection API 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,2,3,4).
On-device API surfaces should be debuggable in Chrome DevTools, and we’ve added extensive mechanisms for debugging Bidding and Auction services.
It will be supported on all platforms that support Protected Audience, so all but WebView.
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.
None
EnableBandADealSupport
False
Shipping on desktop and Android in M132.
None
http://chromestatus/6112108595642368
This intent message was generated by Chrome Platform Status.
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?
Also, more meta question: are there scenarios where you would
ship a feature to PA but not ship support for PA/B&A?
--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrnv-kyAnRATmzj1mVNKQSOJockCt_bs%3D%3Da5K75E%2BiMArA%40mail.gmail.com.
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?
Also, more meta question: are there scenarios where you would ship a feature to PA but not ship support for PA/B&A?
LGTM1 - feature parity makes sense between Chrome &
Chrome/B&A.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/434c7455-3401-40a1-a462-eacdf1396199%40chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.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+unsubscribe@chromium.org.