[null,null,[],[[["Header bidding enables publishers to receive bids from various demand sources for a single ad slot, potentially increasing revenue."],["Protected Audience auctions utilize cross-site data to facilitate targeted advertising while prioritizing user privacy."],["In a sequential auction setup, contextual auctions (including header bidding) run first, followed by a Protected Audience auction, allowing publishers to consider bids from both."],["The winning contextual auction bid price acts as a bid floor for the Protected Audience auction, ensuring the final ad selection is revenue-optimal."],["The Publisher Ad Server ultimately decides which ad to render based on the results of both contextual and Protected Audience auctions."]]],["Protected Audience auctions can return ad candidates as either an opaque URN for `iframe` rendering or a `FencedFrameConfig` for fenced frame rendering. Fenced frames, unlike `iframe`s, restrict communication between the frame and its embedding context, preventing data sharing. They use `FencedFrameConfig` for navigation, setting it to the frame's `config` attribute. A `FencedFrameConfig` is obtained when `resolveToConfig` is set to `true` in the `AuctionConfig`; otherwise, an opaque URN is returned, suitable for an `iframe`.\n"]]
