Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Intent to Ship: Protected Audience (B&A) - Selectable Reporting IDs

137 views
Skip to first unread message

Paul Jensen

unread,
Dec 13, 2024, 10:42:49 AM12/13/24
to blink-dev

Contact emails

paulj...@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 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).


Blink component

Blink>InterestGroups


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. 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).


Debuggability

On-device API surfaces should be debuggable in Chrome DevTools, and we’ve added extensive mechanisms for debugging Bidding and Auction services.


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?

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.

Mike Taylor

unread,
Dec 13, 2024, 1:09:13 PM12/13/24
to Paul Jensen, blink-dev

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.

Paul Jensen

unread,
Dec 16, 2024, 9:08:07 AM12/16/24
to Mike Taylor, blink-dev
On Fri, Dec 13, 2024 at 1:09 PM Mike Taylor <mike...@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.

Mike Taylor

unread,
Dec 18, 2024, 10:44:28 AM12/18/24
to Paul Jensen, blink-dev

LGTM1 - feature parity makes sense between Chrome & Chrome/B&A.

Chris Harrelson

unread,
Dec 18, 2024, 11:25:01 AM12/18/24
to Mike Taylor, Paul Jensen, blink-dev

Alex Russell

unread,
Jan 8, 2025, 11:23:44 AMJan 8
to blink-dev, Chris Harrelson, Paul Jensen, blink-dev, Mike Taylor
LGTM3

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.
Reply all
Reply to author
Forward
0 new messages