[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["Protected Audience allows running auctions with cross-site data, involving multiple sellers."],["In multi-seller auctions, component sellers run parallel auctions, submitting their top ad to a final top-level auction."],["The top-level auction scores ads from component auctions and selects the winning ad based on desirability."],["Publishers utilize this mechanism to diversify ad demand and optimize revenue by incorporating multiple platforms."],["The process ensures user privacy by keeping data within the browser and leveraging bidding and scoring logic from different parties."]]],["Publishers use header bidding to gather bids from various sources for ad slots. In a sequential setup, a header bidding library first runs a contextual auction. This is followed by a server-side contextual auction by the Publisher Ad Server, combining results from multiple sources. Finally, a Protected Audience auction occurs, leveraging cross-site data. The contextual auction's winning bid serves as a bid floor for the Protected Audience auction. If no Protected Audience bid exceeds this floor, the contextual ad is shown. Otherwise, the winning Protected Audience ad is displayed.\n"]]
