How the Protected Audience API can help publishers, advertisers, and ad tech providers

Protected Audience can be used in a variety of ways to support publishers, advertisers, and ad tech providers. Here are some common use cases:

For publishers:

  • Interest group delegation: Publishers can allow other parties (like advertisers or ad tech platforms) to create interest groups on their behalf, enabling more targeted advertising on their sites.
    • Off-platform audience extension: Publishers can create interest groups on their pages and target those groups on other websites as part of direct deals with buyers. This requires partnering with a DSP.
    • Off-platform audience licensing: Publishers can create interest groups and allow buyers to target those groups for a fee, creating a new revenue stream. This requires partnering with a DSP.

For advertisers:

  • Remarketing: Advertisers can create interest groups on their website and use the Protected Audience API to find and retarget those audiences on other publisher sites, increasing the effectiveness of their campaigns.

For ad tech providers:

  • Custom audience support: Ad tech providers can support advertisers buying programmatically against custom audiences without exposing personal information. This can be achieved through interest group creation, ad inventory management, and event-level reporting.
  • Deal support: Ad tech providers (demand-side platforms [DSPs] and supply-side platforms [SSPs]) can receive Deal and Seat ID reporting for Protected Audience campaigns that correspond to an advertiser remarketing Deal.

Discover other use cases for Protected Audience API here

Learn more about how Protected Audience can help your business in the developer documentation.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
11247358569324992027
true
Search Help Center
true
true
true
false
false
false
false