Add details about server orchestrated multi seller flow for PAS auctions #184
Conversation
| encrypted Protected Audience request payload. The top-level seller’s code in the publisher web page asks the browser | ||
| for this encrypted Protected Audience data to include in the unified request. | ||
| encrypted Protected Audience request payload. The top-level seller’s code in the publisher web page/app asks the browser/android API | ||
| for the encrypted Protected Audience/Protected App Signals data to include in the unified request. |
There was a problem hiding this comment.
Should we instead do the following here:
s@Protected Audience/Protected App Signals@Protected Auction(Protected Audience OR Protected App Signals)@ and then use Protected Audience everywhere else below?
There was a problem hiding this comment.
It sounds good to me, but does have the risk of adding a new term in the middle of the explainer. Have we used Protected Auction in other explainers to refer to both as a group?
There was a problem hiding this comment.
Yes, we do use Protected Auction to cover both- https://github.com/privacysandbox/protected-auction-services-docs/blob/main/bidding_auction_services_api.md#bidding-and-auction-services
There was a problem hiding this comment.
Sounds good. will update today.
No description provided.