आपने जिस पेज का अनुरोध किया है वह फ़िलहाल आपकी भाषा में उपलब्ध नहीं है. पेज के निचले हिस्से से कोई दूसरी भाषा चुनी जा सकती है. इसके अलावा, किसी भी वेबपेज का अपनी पसंदीदा भाषा में झटपट अनुवाद भी किया जा सकता है. इसके लिए, आपको Google Chrome की पहले से मौजूद अनुवाद करने की सुविधा का इस्तेमाल करना होगा.

Frequently asked questions related to Ad Manager and Privacy Sandbox for the Web

In this article

What does Chrome's update from third-party cookie
deprecation to user choice mean for Ad Manager & AdSense publishers?

Our core guidance for publishers remains consistent: prioritize building strong relationships with your audience using first-party data and implementing privacy-preserving technologies.

Ad Manager & AdSense will keep investing in building and optimizing our suite of privacy-preserving solutions to support our partners to drive durable ads monetization. As Chrome develops its approach, Ad Manager and AdSense will closely monitor these changes and adjust our product plans accordingly.

Does Google 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, and in-stream video inventory via the IMA SDK.

For Attribution Reporting, Ad Manager currently supports in-stream video and VAST based non-in-stream video.

For Protected Audience, Ad Manager will begin functional testing of serving instream video ads using Protected Audience API through the IMA SDK. Ad Manager will explore supporting non-instream video traffic at a later date.

Does Google 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 is Google 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:

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 Google 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 Google 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.

What reporting is available to publishers in Google Ad Manager about Protected Audience auctions won by non-Google sellers?

Starting in August 2024, Ad Manager introduced the ability for publishers to report on Protected Audience API impressions won by non-Google sellers. Learn more about the new reporting dimension, Protected Audience seller (non-Google).

Was this helpful?

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