The documentation for Protected Audience employs "dsp.example" in its illustrative examples, yet it also alludes to other entities such as advertisers as owners of interest groups.

However, in practical terms, can any buy-side entity besides a DSP feasibly act as an interest group owner?

For example, without building or buying DSP/bidding technology:

• An advertiser
  • It would be impractical for every advertiser to build and operate its own bidding technology.
• A buy-side ad server
  • A buy-side ad server is meant to operate independently of media and support multiple DSPs simultaneously. Adding bidding technology would effectively transform the ad server into a DSP.
• A buy-side DCO provider
  • A DCO provider’s role is to optimize creative content, not to engage in media buying.

It appears that the Protected Audience API is tailored solely to support DSPs on the buy side, with no API support extended to advertiser ad servers or DCO providers. Within a worklet, DSPs have access to real-time platform DSP and seller data for purchasing and ad selection decisions, whereas other vital ad tech components on the buy side do not. As DSPs have, ad servers and DCO providers would be willing to attest to using the Protected Audience APIs in ways that protect user privacy.

Can the Protected Audiences team or others share any practical examples where the DSP is not the Interest Group owner?