In this article
- Does Ad Manager support the Privacy Sandbox APIs on video inventory?
- Does Ad Manager support native ads for Privacy Sandbox APIs?
- What reporting is available to publishers in Ad Manager about Protected Audience auctions won by non-Google sellers?
- What is Ad Manager's plan regarding any added latency from the Protected Audience API?
- Do publishers need any additional contracting to use Privacy Sandbox APIs with Ad Manager?
- How can publishers manage creative quality for ads served via the Protected Audience API?
- Do publishers need to use programmatic demand from Ad Manager in order for Ad Manager to run a Protected Audience auction?
- When a sponsorship wins the protected audience auction, how does Google Ad Manager guarantee that a subsequent protected audience auction doesn’t override this?
Does Ad Manager support the Privacy Sandbox APIs on video inventory?
For Topics, Ad Manager currently supports all inventory using the Google Publisher Tag (GPT), including non-in-stream video. Ad Manager is working towards supporting in-stream video, via the IMA SDK, later this year.
For Attribution Reporting, Ad Manager currently supports in-stream video and VAST based non-in-stream video.
For Protected Audience, Ad Manager is working towards supporting video formats – both in-stream and non-in-stream – later this year.
Does Ad Manager support native ads for Privacy Sandbox APIs?
Ad Manager supports native ad formats for Topics API testing. We are currently assessing support for Protected Audience and are exploring possible designs. We're also actively working to support the Attribution Reporting API for native ads.
What reporting is available to publishers in Ad Manager about Protected Audience auctions won by non-Google sellers?
Ad Manager does not provide reporting about Protected Audience auctions won by non-Google sellers. We are working on providing such reporting later this year.
What is Ad Manager's plan regarding any added latency from the Protected Audience API?
We take a holistic approach, looking at overall publisher revenue. Our end goal is to help publishers see a net positive revenue from Protected Audience API, where the additional publisher revenue gain from Protected Audience demand outweighs any costs incurred due to the additional Protected Audience auction latency.
We're doing a number of things to help achieve this goal, including:
- Parallelizing as much of the on-device computation with the server side ad request to Google Ad Manager as possible (by providing signals asynchronous to the API)
- Setting intelligent timeouts for Protected Audience auctions, leveraging several timeouts offered by the API
- Developing a machine learning model to predict when the Protected Audience auction will yield a winner, and only running Protected Audience auctions when Ad Manager is reasonably confident it will yield incremental revenue.
- Please note that the publisher can choose to override use of this machine learning model when working with non-Google sellers via the "Allow testing on up to 100% of my inventory with non-Google sellers, regardless of performance impact" control.
We've also been working with the ecosystem at large, including Google Chrome, to optimize Protected Audience API integrations.
Our initial testing does indicate that publishers see a net revenue benefit from Protected Audience API on traffic without third-party cookies, indicating the additional demand from Protected Audience API outweighs any costs due to latency.
Do publishers need any additional contracting to use Privacy Sandbox APIs with Ad Manager?
No, Ad Manager does not require any additional contracting for publishers Privacy Sandbox APIs with Ad Manager.
How can publishers manage creative quality for ads served via the Protected Audience API?
Publishers can continue to use Protections to block ads from Ad Manager's open auction - including ads served via the Protected Audience API. Moreover, ads served via the Protected Audience API are shown in the Ad review center, where publishers can block specific creatives.
Do publishers need to use programmatic demand from Ad Manager in order for Ad Manager to run a Protected Audience auction?
No. Ad Manager does not require that publishers use programmatic demand from Ad Manager. Publishers can work with other demand sources, such as other SSPs, integrated as component sellers in Protected Audience auctions run by Ad Manager.
Due to current infrastructure limitations, however, Ad Manager is currently only able to run Protected Audience auctions for ad requests that are targeted by an active Ad Exchange line item, yield group, or AdSense line item, or are for an ad unit enabled for AdSense.
We're working to address this infrastructure limitation in 2024. In the interim, publishers who would like Ad Manager to run Protected Audience auctions on their inventory should ensure that the inventory is targeted by an active Ad Exchange line item, yield group, or AdSense line item, or is for an ad unit enabled for AdSense.
If they desire, Ad Manager publishers then also can use Protections to block any unwanted demand from Ad Manager, including using inventory exclusions to block all Open Auction demand, and use AdSense blocking controls to block any unwanted AdSense demand.
When a sponsorship wins the protected audience auction, how does Google Ad Manager guarantee that a subsequent protected audience auction doesn't override this?
If a sponsorship ad is selected to serve, then it'll serve. Ad Manager won't even run a Protected Audience auction at all. This is similar to how it works today, where if a sponsorship is selected to serve Ad Manager does not solicit programmatic bids or run a programmatic auction.
