[null,null,[],[[["The Protected Audience API enables interest-based advertising without sharing user data with third parties by storing interest group memberships locally on the user's device."],["Advertisers define interest groups using properties like `owner`, `name`, `biddingLogicUrl`, and `ads`, specifying criteria and relevant ad creatives."],["Advertisers can add users to interest groups via `joinAdInterestGroup()` and remove them using `leaveAdInterestGroup()`, requiring permission from both the site being visited and the interest group owner."],["The API incorporates privacy measures, including k-anonymity thresholds to ensure sufficient user numbers within interest groups for ad targeting, and restrictions on data sharing."],["Comprehensive developer resources, including guides and explainers, are available to facilitate implementation and understanding of the Protected Audience API."]]],["Controlling audience management involves setting permissions for `joinAdInterestGroup()`. By default, the site being visited grants same-origin permission, but cross-origin permission needs explicit allowance via a permissions policy. Interest group owners can implicitly grant permission by calling the function from a same-origin iframe. Alternatively, they can delegate permission to other domains through a `.well-known` URL, which defines permissions for joining and leaving interest groups for various origins. The function also uses cors mode for the fetched response.\n"]]
