Intent to Ship: Protected Audience: Creative scanning via BYOS/V1 trusted scoring signals
Orr Bernstein
or...@google.com, paulj...@chromium.org, morl...@chromium.org
Explainer
https://github.com/WICG/turtledove/pull/1406
Specifically, see addition of creativeScanningMetadata to the interest group here, addition of the sendCreativeScanningMetadata boolean to the auction config here, and the addition of new query parameters sent with the BYOS/V1 trusted scoring signals request URL here.
Specification
https://github.com/WICG/turtledove/pull/1398
Specifically, see addition of creativeScanningMetadata to the interest group here, addition of the sendCreativeScanningMetadata boolean to the auction config here, and the addition of new query parameters sent with the BYOS/V1 trusted scoring signals request URL here.
Summary
As noted in https://github.com/WICG/turtledove/issues/792, one of the responsibilities of sellers is to make sure that the ad shown meets the publisher's restrictions. Today, when a seller considers an ad for which a buyer is bidding, they verify, for example, that the ad is not about any of the subjects the publisher does not want shown on their site. Determining the subject of an ad - a process called creative scanning - can be slow, as it utilizes some combination of AI and human evaluation. Sellers have historically relied on populating a creative scanning pipeline through a combination of pre-registration and by discovering ads through the bid stream. Sellers generally require creative scanning to complete before allowing an ad to win an auction. This process proves to be challenging in Protected Audience API because the auction runs in isolation, and so it can't send ads out to have them evaluated, since doing so would potentially leak information about the user's identity by associating their activity on the publisher site with past activity on advertiser sites. This change enables sellers to discover ads for creative scanning by leveraging the stream of ads sent to their bring-your-own-server (BYOS) real-time scoring signals key/value service. It does so by making it possible for sellers to request that the auction include some additional metadata alongside each ad's renderURL on the request to the real-time scoring signals key/value service. This includes some existing metadata — the buyer's origin, ad size, and buyerAndSellerReportingId — as well as a new field titled creativeScanningMetadata. This solution addresses the needs of creative scanning until a future solution is implemented that's compatible with the privacy-advancing requirement of Trusted Execution Environment (TEE)-hosting for real-time scoring signals key/value service. This solution does not regress the current privacy properties of Protected Audience.
Blink component
TAG review
https://github.com/w3ctag/design-reviews/issues/723
TAG review status
Completed for PA, resolved unsatisfied.
RisksInteroperability and Compatibility
Optional new functionality that does not break existing use.
Gecko & WebKit: For PA 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: Requested in turtledove repository GitHub issue #792
WebView application risks
Protected Audience not available in WebView
Debuggability
API is debuggable in DevTools - developers can see the BYOS/V1 trusted scoring signals request in the Network tab in DevTools, and can observe the additional query parameters added to the BYOS/V1 trusted scoring signals request URL when sendCreativeScanningMetadata is specified on the auction config.
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?
Flag name on about://flags
None
Finch feature name
FledgeTrustedSignalsKVv1CreativeScanning
Requires code in //chrome?
False
Estimated milestones
Shipping on desktop and Android in M134.
Anticipated spec changes
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6326346340630528?gate=6264312584470528
This intent message was generated by Chrome Platform Status.
Mike Taylor
On 3/28/25 1:06 PM, 'Orr Bernstein' via blink-dev wrote:
Contact emailsor...@google.com, paulj...@chromium.org, morl...@chromium.org
Explainerhttps://github.com/WICG/turtledove/pull/1406
Specifically, see addition of creativeScanningMetadata to the interest group here, addition of the sendCreativeScanningMetadata boolean to the auction config here, and the addition of new query parameters sent with the BYOS/V1 trusted scoring signals request URL here.
Specificationhttps://github.com/WICG/turtledove/pull/1398
Specifically, see addition of creativeScanningMetadata to the interest group here, addition of the sendCreativeScanningMetadata boolean to the auction config here, and the addition of new query parameters sent with the BYOS/V1 trusted scoring signals request URL here.
This intent message was generated by Chrome Platform Status. --
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/7145cde1-55d0-4016-b176-cf588057866an%40chromium.org.