Protected Audience API: experiment and participate

Quick guide to implement and test the API. Set up privacy-preserving ad auctions to serve remarketing and custom audience use cases.

Key point: The Privacy Sandbox Relevance and Measurement origin trial ended September 20, 2023 and the APIs are now available for 99% of Chrome users, and origin trial enrollment has closed. To keep abreast of the percentage of users each API is enabled for, refer to the Chrome status graphs.

Update: FLEDGE has been renamed to Protected Audience API. To learn more about the name change, see the blog post.

Learn the essentials

• If you're a developer or software engineer, the Protected Audience API Developer Guide provides an in-depth technical reference.
• The Protected Audience API overview offers a higher level explanation for those who work in advertiser and ad tech, who are new to the Privacy Sandbox.

Try the API

Caution: Read about feature detection to learn how to determine if a feature is available before attempting to use it.

1. Learn how to use the Protected Audience API.
   • Review the Protected Audience API Developer Guide. This guide offers a reference for API methods and parameters.
   • Read about Protected Audience services. For example, the Key/Value service offers real-time information to buyers and sellers during the ad auction.
2. Try the demo.
   • Review the source code.
   • Watch the Protected Audience demo video to learn how the demo code works and how to use Chrome DevTools for FLEDGE debugging.
3. Experiment with the API.
   • Try out the Protected Audience API for a single user by enabling chrome://flags/#privacy-sandbox-ads-apis or by running Chrome from the command line with Protected Audience feature flags.
   • Troubleshoot Protected Audience worklets with Chrome DevTools. Learn how to debug Protected Audience bidding and auction code.
4. Review the Protected Audience status for updates on the implementation of the Protected Audience API. Review the pending Protected Audience capabilities for more details.

The Protected Audience API explainer provides more detail about feature support and constraints.

Get support

Is anything blocking you from experimenting with the API? Ask a question about your implementation, the demo, or the documentation:

• Open a new Issue on the Privacy Sandbox Dev Support repository. Make sure to select the Issue template for the Protected Audience API.
• Raise an issue on the demo code repo on GitHub.
• For more general questions about how to meet your use cases with the API, file an issue on the API repository.

For bugs and issues with the implementation of the Protected Audience API in Chrome:

• View existing issues reported for the API.
• Raise a new issue at crbug.com/new.

Join the discussion

Everyone is welcome to join in discussion of the Protected Audience API. In particular, if you're experimenting with the API, your feedback is essential.

Discuss the API

Like other Privacy Sandbox APIs, this API is documented and discussed publicly.

• Read the FLEDGE explainer on GitHub.
• Join the conversation about existing issues.
• Open a new issue to ask a question, propose a feature, or discuss a use case.
• Join the scheduled calls for Protected Audience (every second week). Everyone is welcome to join—to participate, first make sure to join the WICG. You can actively participate or just listen in!

Discuss related topics

Discuss industry use cases in the Improving Web Advertising Business Group.

Give feedback

Privacy Sandbox feedback explains how to provide other types of feedback, and how to engage in discussion of Privacy Sandbox APIs.

Get updates

• To be notified of status changes in the API, join the mailing list for developers.
• To closely follow all ongoing discussions on the API, click the Watch button on the API page on GitHub. This requires you have or create a GitHub account.
• To get overall updates on the Privacy Sandbox, subscribe to the RSS feed [Progress in the Privacy Sandbox].