Info: Starting in June 2025, Index is pausing support for the Protected Audience API. After this date, you will no longer receive Protected Audience API demand from Index, even if your inventory is configured to be eligible for it.
The Protected Audience API is an in-browser API available on Chrome for banner ads. It allows DSPs to create and target interest groups without relying on third-party cookies, while protecting users from cross-site tracking. The final bidding happens on the device, within the browser. Publishers using Prebid.js and Google Ad Manager as their ad server, can configure their inventory to be eligible for the Protected Audience API and to receive on-device auction signals from Index Exchange (Index)'s demand partners.
For more information about the privacy measures that the Protected Audience API introduces and how it functions in web environments, see the Index Explains video explaining what is the Protected Audience API.
Note:
- Currently, ad quality blocks are not enforced on ads that are rendered using the Protected Audience API.
- Bids that use
selectedBuyerAndSellerReportingIdto signal deal IDs are shown as open market bids in Index's reporting and utilize the Media Owner's open market revenue share. For more information about reporting IDs, see Google's Deals in Protected Audience documentation.
Depending on the Prebid.js version that you are using, the steps to configure Prebid.js will differ. From the list below, follow the steps for the version of Prebid.js that you are using:
If you are using a Prebid.js version that is between 8.18.0 and 8.36.0, see Configure Protected Audience API for Prebid.js versions 8.18.0 to 8.36.0.
If you are using a Prebid.js version that is from 8.37.0 and up to 9.0.0, see Configure Protected Audience API for Prebid.js versions 8.37.0 and up to 9.0.0.
(Recommended) If you are using Prebid.js version 9.0.0 or later, see Configure Protected Audience API for Prebid.js version 9.0.0 or later.