v130 · miscellaneous
Protected Audience Bidding & Auction Services
The Protected Audience API (formerly known as FLEDGE) is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed so third parties cannot track user browsing behavior across sites. This feature, Protected Audience Bidding & Auction Services, outlines a way to allow Protected Audience computation to take place on cloud servers i
concepts
-
Bidding & Auction Services pipeline
Step-by-step walkthrough of the B&A flow:
getInterestGroupAdAuctionData, seller request, TEE auction,runAdAuctionwith the server response. -
Device vs server latency
Latency calculator built from the explainer's cost model. Dial buyer count, RTT, and device CPU; see the device-side path's per-bid cost grow linearly while the B&A path holds steady at one round-trip plus TEE-side parallelism.
-
Auction tracer (8-step ladder)
Click through the eight-message exchange between browser, SSP, seller TEE, bidder TEEs, and the K/V trusted servers. Each step explains who can read what, shows the encrypted envelope contents, and filters by actor so you can audit one party's view in isolation.
-
Bid request probe
Configure up to 4 DSP buyers, call
navigator.getInterestGroupAdAuctionData(), and POST the encrypted request to the local seller endpoint without inventing a winning bid.
why it shipped
The Protected Audience API (formerly known as FLEDGE) is a Privacy Sandbox proposal to serve remarketing and custom audience use cases, designed so third parties cannot track user browsing behavior across sites. This feature, Protected Audience Bidding & Auction Services, outlines a way to allow Protected Audience computation to take place on cloud servers i