Today we’re announcing the April 2026 update to the Display & Video 360 API. This update includes the following:

While Demand Gen campaign support is in beta, it is only available to allowlisted customers. See our guide for detailed instructions on how to create a Demand Gen ad campaign. If your partner is allowlisted:

  • Demand Gen line items, ad groups, and the relevant targeting will be included in relevant get and list requests.
  • Demand Gen line items, ad groups, ads, and the relevant targeting can be created, deleted, and updated.

We aim to launch full Demand Gen support for the Display & Video 360 API in general availability later this year. This will be announced with a future release.

For a complete list of new features in this update, see the Display & Video 360 API release notes. Before using these new features, make sure to update your client library to the latest version.

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

The Content API for Shopping will sunset on August 18, 2026, to be replaced by the Merchant API. This migration provides a shift toward more robust, scalable, and feature-rich integrations. For Google Ads scripts users, the Google Ads scripts editor will begin rolling out Merchant API support on April 22, 2026. While the Content API for Shopping will remain available until its sunset, here’s what to expect from the Merchant API.

Understanding the Merchant API

The Merchant API offers important changes and improvements over the Content API for Shopping:

  • Modular Design: The Merchant API is broken down into sub-APIs. This allows for:
    • Faster access to new features and updates.
    • Easier versioning and maintenance.
    • Reduced disruption, as changes in one sub-API are less likely to impact others.
  • New Features & Capabilities:
  • Omnichannel Support: Designed with Omnichannel in mind, though it provides backward compatibility for legacy separate online/local offer structures using the legacy_local flag.

Take a look at the Merchant API migration guide for more detail on the changes between APIs.

How to get started

The Merchant API will be available as an Advanced API in the Google Ads scripts editor, just as the Content API is.

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

We're excited to announce the addition of new channels for the Data Manager API on our “Google Advertising and Measurement Community” Discord server. To join, just click this invite link and follow the onboarding guide.

Our team will be on this server regularly to interact with the Data Manager API community, answering questions and gathering feedback in the #data-manager-api channel. We’ll also keep you up to date on the latest Data Manager API news in the #announce-data-manager-api channel.

If you have any questions or want to discuss this post, please reach out to us on the “Google Advertising and Measurement Community” Discord server. We look forward to seeing you there and hearing your thoughts on how we can continue to improve the Data Manager API!

We're excited to announce the launch of the new Google Advertising and Measurement Developers Hub!

Come see the new site!

Whether you're looking to automate campaigns, analyze performance, manage tags, or monetize your apps, the new hub is designed to make it easier to find the right tools and information.

We've launched a new technical-user focused site to make it easier than ever for you to find the tools, resources, and support you need to build and innovate with Google's advertising and measurement products.

What's New?

We have created a one-stop shop where you can easily find the resources you need, connect with our team and the community, and get support. Here are some key features:

  • At-a-glance homepage: A clear starting point highlighting how we can help, with quick links to our blog, Discord, and information about our team.
  • Meet the team: Learn more about the Developer Relations team dedicated to supporting your success.
  • Products: A comprehensive directory of the developer products we cover, from the Google Ads API and Google Analytics APIs to Publisher Tools like AdMob and Ad Manager, linking directly to their official documentation. You can browse by categories like Advertising Platforms, Tagging, Measurement & Analytics, and Publisher Tools.
  • Connect with us: A streamlined page to help you find the best way to engage:
    • Join our vibrant Discord community.
    • Find links to product or technical support.
    • Download open source projects on GitHub.
  • Media and podcast: A new home for our multimedia content, including the Ads DevCast playlist embedded directly on the page.

We're excited to make this the place for you to learn, build, and connect.

Please explore the new site and use the Send Feedback button located at the bottom of each page to share your thoughts!

If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Happy Building!

Many to 1, Audience Management in Data Manager API

In today's fast-paced digital landscape, managing multiple data pipelines can feel overwhelming. If you're a developer navigating the complexities of audience management and conversion tracking, you might be wondering: how can I streamline my processes and reduce costs?

This week’s episode of Ads DevCast explores the new Data Manager API, which will transform the way you connect data across various Google ad platforms, making your workflows more efficient and cost-effective. This product solves many of the complexities developers and agencies have had to juggle across multiple APIs—each with its own schema, maintenance requirements, and learning curve.

Click here to watch the episode: https://youtu.be/Z4mAR98cizQ

About our Guest

In this episode we sit down with Melissa Ng, Product Manager for Data Manager API, to discuss how Google is streamlining these processes and what it means for your development workflow.

Melissa is a seasoned Product Manager, specializing in ads measurement at Google for the past four years. Her deep understanding of customer needs and data management challenges drives her passion for creating innovative solutions like the Data Manager API.

What are we solving for?

Every advertising product has its own unique requirements that aren't necessarily interoperable. This fragmentation creates confusion, slows down onboarding, and drives up engineering costs. It also makes it difficult to build the kind of cohesive "Data Strength" needed to fuel modern advertising and maximize conversions.

In a joint case study, one of our advertisers reported spending over $1 million annually on maintenance alone. We needed to provide a unified ingestion point for conversions and audiences, effectively reducing confusion and simplifying data management.

Enter the Data Manager API

The Data Manager API is Google's answer to this complexity. It allows data partners, agencies, and advertisers to send first-party data to multiple Google advertising products—such as Google Ads, Display & Video 360, Campaign Manager 360, Google Analytics, and others—in a single call.

"This means that when you’re sending in a field for, say, 'transaction id', that field means the same thing in all of the downstream use cases across all of the Google advertising products," explains Melissa in the episode.

While the primary motivation behind developing the Data Manager API was to address complexities associated with maintaining multiple APIs, there are other benefits as well:

  • Ease of Use and Efficiency at Scale: You can achieve significant savings in resources. Treasure Data, one of our early API integration partners, reported a 2x faster advertiser onboarding process and an 80% reduction in engineering efforts.
  • Privacy by Default: End-user privacy is non-negotiable. The Data Manager API features confidential matching right out of the box for audience solutions like Customer Match. This utilizes a Trusted Execution Environment (TEE) to ensure that no one—not even Google—can view the processed data. (Read more)
  • Future-Proofing Your Stack: The Data Manager API is the future of audience and conversion management. Any new features for audience or conversion management will be implemented in the Data Manager API going forward. (See our timelines)
  • Enhanced Diagnostics: For the first time, API stats and diagnostics will soon be available directly in the Ads UI, providing visibility into the health of your connections and downstream asynchronous errors, saving you countless hours of troubleshooting.

Tune In and Take Action

If you are managing audiences or conversions programmatically, this episode is a must-listen. It is packed with insights, roadmap updates, and advice on how to seamlessly migrate your existing systems.

Listen to the full episode of the Ads DevCast here!

Ready to get started with the Data Manager API?

  1. Start your upgrade today: Dive into the step-by-step tutorials and upgrade guides.
  2. Join the community: Connect with us and other developers on our Discord server.
  3. Share your feedback: We want to hear from you! Let us know what features you want to see next by filling out our Episode Survey. Reminder, this show is a pilot, and your feedback is important so we can tailor our content to what is most useful for you.

Thanks for tuning in! We'll see you in two weeks for Episode 3.

The Ad Manager API now supports a read-only OAuth scope. This new scope, https://www.googleapis.com/auth/admanager.readonly, allows developers to request read-only access to their users' Ad Manager data.

This new scope is only available for the Ad Manager API. It is not supported by the legacy Ad Manager SOAP API, which will continue to require the full-access scope.

The read-only scope allows reading data and running reports, but does not grant permission to write or modify data. This provides an enhanced security layer for developers and users of read-only integrations, such as reporting dashboards or alerting tools.

No action is required for existing integrations. If your application does not require write access, we recommend migrating to the new read-only scope. For a refresher on how to configure OAuth, see Using Oauth 2.0 for Web Server Authentication.

As always, Ad Manager access controls, including User roles and Restrictions imposed by teams, are applied to all API requests regardless of the OAuth scope used.

If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server.

Increased Request Limits for BatchJobService Enhance Large Asset Uploads

We're pleased to announce significant increases to the request size limits for the BatchJobService.AddBatchJobOperations method in the Google Ads API. These changes are designed to streamline workflows, particularly for developers uploading multiple large assets like images, by reducing the need to split uploads into numerous smaller requests.

The following limits have been increased:

Request Size Cap on AddBatchJobOperations: Increased from 10,484,488 bytes (approximately 10.48 MB) to 41,937,920 bytes (approximately 41.94 MB).

Single Mutate Operation Size: While the overall request can be larger, the size of a single mutate operation within the batch is capped at 10,484,488 bytes (approximately 10.48 MB).

What This Means for Developers:

This update allows you to include more operations, especially those containing sizable data like image assets, within a single AddBatchJobOperations request. This can simplify your client-side logic and potentially improve throughput by reducing the number of round trips required to add all operations to a batch job.

For example, when uploading multiple images, each of which can be up to 5,242,880 bytes (approximately 5.24 MB), you can now batch more of these into a single request, up to the new 41,937,920 bytes (approximately 41.94 MB) total request limit.

Important Notes:

  • While the request size limit has increased, other limitations such as the maximum number of operations per request (10,000) and per job (1 million) still apply. Please refer to the Best Practices and Limitations guide for full details.

We believe this enhancement to the BatchJobService will offer greater flexibility and efficiency for managing bulk operations in the Google Ads API.

As always, please reach out to us via the forum or our other support channels if you have any questions or feedback.

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.