Protected Audiences and non-RTB media

[anthony-yam-mediaocean]

Many advertisers engage in media transactions outside of real-time bidding (RTB), such as direct upfront deals with publishers.

Presently, advertising servers and Dynamic Creative Optimization (DCO) providers can utilize two types of data: 1) information from publishers and 2) insights about advertiser audiences to make decisions regarding creative optimization.

Considering the importance of safeguarding privacy, can the Protected Audience APIs be extended to support non-RTB media transactions and maintain critical use cases such as ad serving and DCO?

[anthony-yam-mediaocean]

Please see #1028 for a related proposal.

[michaelkleber]

Does the Shared Storage API's selectURL mechanism fit your use case? (And if not, why not?)

[anthony-yam-mediaocean]

As we discussed on a recent Protected Audience call, the Shared Storage API could be used to manage advertiser audience data. We would be duplicating effort and Shared Storage space to store this information when it's already being stored in Protected Audience Interest Groups.

Another challenge is that advertisers expect to be able to serve product-level ads on non-RTB buys, and Shared Storage cannot handle this use case with its 8 output URLs. In current designs, this use case can only be supported by Protected Audience's ad components.

This is why we're proposing a solution that provides secure access to Protected Audiences in non-RTB environments.