demo · v130
Auction tracer
Step through a full Protected Audience Bidding & Auction Services flow — eight messages bouncing between Browser, SSP, DSP, the seller and bidder TEE-hosted services, and the K/V trusted servers. Highlights every signal envelope (Trusted Bidding Signals, Server Auction Request, BiddingAuctionResponse) and explains which actor sees what.
filter by actor
click a step to read the explanation; the message envelope appears below
Browser ↔ device
Seller path
Bidder path
TEE traffic
click a step to inspect the message body
the code
// 1. Browser calls runAdAuction with serverResponse path
await navigator.runAdAuction({
seller: "https://ssp.example",
serverResponse: bidderAuctionResponse,
decisionLogicUrl: "https://ssp.example/decision-logic.js"
});
// 2. The serverResponse was previously fetched from the SSP:
const ar = await fetch("/auction-request", { method: "POST", body: clientHints });
// 3. SSP POSTs the request to the seller Trusted Execution Environment.
// 4. Seller TEE fans out to each Bidder TEE (DSPs).
// 5. Bidder TEEs read Trusted Bidding Signals from a TEE-hosted K/V server.
// 6. Bidder TEEs return bid + BiddingAuctionResponse to seller TEE.
// 7. Seller TEE scores, picks winner, encrypts envelope back to SSP.
// 8. SSP returns the encrypted envelope to the browser, which decrypts and renders.