Google Ads Developer Blog

Ads DevCast Episode 2: Audience Management

2026-04-02T08:10:00.000-07:00

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?

Start your upgrade today: Dive into the step-by-step tutorials and upgrade guides.
Join the community: Connect with us and other developers on our Discord server.
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.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

New Google Ad Manager API read-only scope

2026-03-27T13:55:00.000-07:00

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.

- Chris Seeley, Ad Manager API Team

Increase in Batch Job Service Request Size

2026-03-27T10:57:00.000-07:00

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.

Bob Hancock, Google Ads API Team

Upcoming Improvements to Offline Conversion Imports

2026-03-26T09:25:00.000-07:00

Starting in April, 2026 the Google Ads API will benefit from a series of infrastructure changes designed to improve the Offline Conversion Import experience. These upgrades will not result in any breaking changes to the Google Ads API, however there may be minor fluctuations in attribution rates as the changes are rolled out.

Here is a breakdown of the rollout and the improvements you can expect:

Improved attribution and fallback recovery (April, 2026): We will implement changes allowing us to attribute some expired GCLIDs and clicks that occurred before a conversion. Once deployed, you may receive fewer EXPIRED_EVENT and CONVERSION_PRECEDES_EVENT errors in conversion upload responses, and you may notice higher attribution rates.
Flexible import requests (April - May, 2026): We will improve the authorization structure for conversion import requests to make it easier for manager or client accounts to import conversions on behalf of a different trafficking account. Once released, users should expect a reduction in UNAUTHORIZED_CUSTOMER and INVALID_CUSTOMER_FOR_CLICK errors in conversion import responses. This may also result in an increase in attribution.

Make sure to review our guidance on how to maximize the performance of your Google Ads conversion data. And take a look at the Data Manager API, including our migration guide for Google Ads API users.

Reach out to the Google Ads API support channel if you have any questions. And 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.

- Ben Karl, on behalf of the Google Ads API Team

Announcing v23.2 of the Google Ads API

2026-03-25T14:59:00.000-07:00

Today, we’re announcing the v23.2 release of the Google Ads API. To use the new v23.2 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord or on our Ads Developers YouTube Live tomorrow (March 26th at 11a ET). This will also be recorded and posted on YouTube for those who can’t make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

Here are some of the key features in this release:

Added the VideoEnhancement resource with enhancement-specific video ad information, such as whether it's Google-generated or advertiser-provided. See the About video enhancements to learn more.
Added the AppTopCombinationView read-only resource to provide insights into top-performing asset combinations in App campaigns.
Added HotelSettingInfo.disable_hotel_setting to allow disabling the hotel feed in Demand Gen campaigns.
Added the biddable_indirect_install_first_in_app_conversion_micros metric to Campaign, Customer, and AdGroup resources.
Added several enhancements to ContentCreatorInsightsService and ReachPlanService. Learn more.

Where can I learn more?

The following resources can help you get started:

For technical support issues, reach out to https://support.google.com/google-ads/gethelp

- Anash P. Oommen, Google Ads API Team

Announcing new Display & Video 360 API Discord channels and a documentation update!

2026-03-23T10:04:00.000-07:00

Today we’re announcing two huge improvements for Display & Video 360 bulk tools.

First, we are launching support for Display & Video 360 API, Structured Data Files, and Bid Manager API products in the existing “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 Display & Video 360 community, answering questions and responding to feedback. We’ll also let you know what’s new with our products in the #announce-display-video-360 channel.

Second, we have made a significant update to the Display & Video 360 API and Structured Data Files documentation. The updated site is designed to make it easier to learn how to perform common tasks with Task guides, browse important conceptual information with Concept guides, and review reference material with updated navigation that highlights currently-supported versions and features of the API and Structured Data Files.

If you have feedback on these changes or the content of any of the guides, please click the Send Feedback button at the bottom of any page in the documentation.

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

- Trevor Mulchay, Display & Video 360 API Team

Introducing: Ads DevCast

2026-03-20T08:24:00.000-07:00

A new podcast for the ads technical community

We are thrilled to announce the launch of Ads DevCast, a new bi-weekly vodcast and podcast series brought to you by Google’s Advertising and Measurement Developer Relations team.

Hosted by Developer Relations Engineer Cory Liseno, this show is dedicated to deep dives into our latest technical updates, insights from the engineers building our tools, and expert discussions on products like Google Ads, Google Analytics, Display & Video 360, Meridian, and more.

While you might already be familiar with the Ads Decoded podcast — where Ginny Marvin does a fantastic job bridging the gap for marketing teams on campaign strategy — Ads DevCast is built specifically for builders and developers.

You can tune in on our Google Ads Developers YouTube channel or find the podcast on Google Ads Developers in YouTube Music.

Episode 1: MCPs, Agents, and Ads. Oh My!

In our premiere episode, we explore the "agentic shift" currently reshaping the advertising landscape. We’re seeing a world where agents, not just humans, are becoming primary consumers of our APIs. To help you stay ahead, we’ve released several tools designed to make your integrations smarter, faster, and more accessible.

Getting Smarter with MCP Servers

One of the covered topics is Model Context Protocol (MCP), and how it allows your agents like Gemini CLI to securely access your data.

We’ve recently released open source, self-hosted MCP servers for the Google Ads API and Google Analytics API. These tools allow you to ask natural language questions directly to your agent, such as:

"What are my active campaigns?"
"Which properties had the highest traffic yesterday?"
"What are my top-selling products over the last month?"

The real magic happens when you combine this data with generative power. In the episode, we discuss how you can use the Analytics MCP to not only pull reports but then ask Gemini to generate a data-justified marketing plan based on those specific results.

Moving Faster with the Developer Assistant

Technical speed is another major focus. To reduce the time spent digging through documentation, we’ve launched the Google Ads API Developer Assistant. This Gemini CLI extension allows you to use natural language to generate, debug, and even test-run integration code.

In one real-world test, we used the assistant to solve a complex reporting issue regarding policy disapprovals. What would normally take days of back-and-forth with email support was resolved by the assistant in minutes, providing the exact GAQL query needed to get the job done.

Improving Accessibility

AI tooling is also changing who can interact with our technical systems. We’re seeing a shift from the "Ads Developer Community" to a broader "Ads Technical Community." Marketing power users are now leveraging MCP servers to perform real-time data operations without waiting for a full development lifecycle. This frees up engineering teams to focus on high-impact "blue sky" projects while giving marketers the agility they need.

We want to hear from you

This show is a pilot, and your feedback is important so we can tailor our content to what is most useful for you. Please take a moment to fill out our Episode 1 Survey and let us know what topics you want us to cover next.

Be sure to also join our Discord Community where you can join the conversation with Googlers and fellow developers.

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

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Upcoming changes to Lookalike user lists in the Google Ads API, starting April 30, 2026

2026-03-19T11:03:00.000-07:00

Google Ads is committed to providing a reliable and efficient environment for all advertisers. To ensure that our systems remain stable and that resources are allocated fairly, we are introducing a uniqueness check for Lookalike user lists that prevents the creation of duplicate lists. These changes primarily impact Demand Gen campaigns and will begin to be enforced starting on April 30, 2026.

A Lookalike user list is considered a duplicate if it shares all of the following attributes with an existing list:

Seed lists: The underlying source audiences used to build the Lookalike.
Expansion level: The degree of similarity to the seed lists.
Country targeting: The geographical reach of the Lookalike list.

If an advertiser attempts to create a duplicate list after April 30, 2026, the Google Ads API will return the error code DUPLICATE_LOOKALIKE for v24 and beyond. For earlier versions, the error will be RESOURCE_ALREADY_EXISTS.

What this means for you

For the majority of advertisers, these changes will go unnoticed, as most current usage falls well within these new boundaries. However, to ensure a smooth transition, we recommend the following:

Reuse audiences: Instead of creating a new, identical Lookalike list, verify if an existing one with the same configuration can be reused in your campaigns.
Update error handling: If you use the Google Ads API, ensure your integrations are prepared to handle the new error starting on April 30, 2026: v24 will return the DUPLICATE_LOOKALIKE error code and all previous versions will return RESOURCE_ALREADY_EXISTS.

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.

- Dora Sun - Google Ads API Team

Changes to Customer Match Support in the Google Ads API

2026-03-04T08:46:00.000-08:00

Starting on April 1, 2026, the Google Ads API will no longer accept new adopters of Customer Match. As with our recent announcement for the use of session attributes and IP address in click conversions in the Google Ads API, we’re recommending that new adopters of Customer Match integrate with the Data Manager API as their primary user data import API.

Developers who have not adopted Customer Match, or have not uploaded data to a Customer Match list between October 2025 and March 2026, will receive an error if they attempt to upload to a Customer Match list. Developers who have already adopted Customer Match can continue importing user data using the Google Ads API while they integrate with the Data Manager API.

Technical details

Developers will be allowlisted by their developer token.
Once this change is rolled out, users who are not on the allowlist will receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting to upload user data to a Customer Match list using either the OfflineUserDataJobService or UserDataService.
See the documentation for integrating with the Data Manager API for Customer Match imports for Google Ads.

Reach out to the Google Ads API support or Data Manager API support channels if you have any questions.

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.

- Ben Karl, on behalf of the Google Ads API Team

Minimum Budget Requirement for Demand Gen Campaigns

2026-02-27T07:52:00.000-08:00

Starting on April 1st, 2026, the Google Ads API will begin enforcing a minimum daily budget of 5 USD, or the equivalent in local currency, for all Demand Gen campaigns. This update ensures that campaigns have adequate budget to navigate the initial "cold start" phase, during which our models learn and optimize for performance.

This change is being implemented as an unversioned update across the Google Ads API, providing consistency across all buying doors.

Technical details and error handling

Depending on the version of the API you are using, you will encounter different behaviors when a budget below the 5 USD floor is specified for a Demand Gen campaign:

Google Ads API v21 and above: You will receive a BUDGET_BELOW_DAILY_MINIMUM error when creating or updating a campaign with an insufficient budget. You can also refer to the details.budget_per_day_minimum_error_details field for further details about the minimum budget, such as the actual minimum threshold.
Google Ads API v20: The API will return a generic UNKNOWN error code. To identify this specific validation failure, you must check the details.unpublished_error_code field, which will contain the string CampaignBudgetError.BUDGET_BELOW_DAILY_MINIMUM.

The validation will trigger whenever a campaign's budget, start time, or end time is modified in a way that results in a daily budget below the floor. This applies to both daily budgets and flighted (custom) budgets.

Impact on existing campaigns

Existing Demand Gen campaigns that currently operate with a budget below the 5 USD threshold will continue to serve without interruption. However, any future modifications to these campaigns' budgets or durations will be subject to the new validation rules. To make a change to these campaigns, the budget must be increased to at least the minimum required floor.

Next steps

We recommend that developers update their reporting and management systems to handle these new error codes.

If you have any questions regarding this change, get Google Ads API support.

- Mattia Tommasone, Google Ads API Team

Introducing Google Ads API Developer Assistant v2.0

2026-02-26T09:24:00.000-08:00

This major update transforms the Assistant from a powerful code generation tool into a proactive troubleshooting and automation partner for Google Ads developers. Since our v1.6.0 release, we've listened to your feedback and focused on the most challenging parts of API development: diagnostics, consistency, and setup.

What’s new in v2.0?

1. Simpler Installation & Maintenance

Setting up a multi-language development environment shouldn't be a chore.

One-Command Setup: Use the new --install-deps flag with install.sh or install.ps1 to handle pip, composer, and bundler dependencies in one go.
Unified Directory Structure: All your generated code, CSV exports, and diagnostic reports are now organized under a single saved/ directory with sub-directories for each type of output.
One-Command Update: When a new version of the API and the client libraries are released you need to execute update.sh to work with the latest version. You can also use update.sh to add additional client libraries to your context.

2. Agentic conversion troubleshooting

Offline conversion tracking is one of the most powerful—yet complex—features of the Google Ads API. Debugging why a conversion wasn't attributed can be a time-consuming manual process.

In v2.0, we’ve introduced a dedicated Conversion Troubleshooting & Diagnostics suite.

New Script: api_examples/collect_conversions_troubleshooting_data.py
New Command: /conversions_support_data

The script executes standard reports for conversions troubleshooting and provides context for the Assistant to troubleshoot your issues.

The command is most useful after the Assistant has analyzed your conversion problem and attempted to solve it. If it cannot, and you need to contact support, this command will analyze your customer settings, conversion actions, and upload summaries to generate a structured diagnostic report based on the analysis already performed. It even identifies "unhealthy" states and high failure rates automatically, saving you hours of log diving. It saves the results to a text file that you can include with a support request should you need to file one.

3. Built for the latest API (v23)

Version 2.0 fully supports Google Ads API v23. All our interactive examples have been updated, and the Assistant's internal context is now optimized for the latest resources and fields, ensuring the code you generate is production-ready.

4. Seamless Automation with Session Hooks

We’ve added SessionStart and SessionEnd hooks to make your workflow truly frictionless.

Automatic Configuration: The Assistant can now automatically locate your configuration file in your $HOME directory at the start of a session. It copies it to the sub-directory config in your project directory. Python is Gemini’s preferred language to query the API. So, if you are using another language, it reads your configuration file and creates a temporary google-ads.yaml in config for its queries, but continues to respond in the code of your preferred language.
Auto-Cleanup: Temporary configurations are securely wiped when you exit, keeping your workspace clean and your credentials safe.

5. Smarter GAQL validation

Building complex GAQL queries is easier than ever. We've updated GEMINI.md and conversions/GEMINI.md with rigorous validation rules for the latest API edge cases, including improved handling of date segments and finite range requirements. The Assistant now catches logic errors before you execute the query.

6. Skills

Think of a Skill as a mini-plugin or a "behavior blueprint." While the general context (like your GEMINI.md file) provides background info, a Skill is only "loaded" into the AI's brain when it specifically needs to perform a complex, procedural task like obtaining the current version of this extension. You don’t execute the Skill directly. Gemini decides when it needs it.

Although still an experimental feature, we have included one with this release to compliment our use of hooks for session initialization and cleanup.

Why Should You Upgrade?

The leap from v1.6.0 to v2.0.0 is about more than just new features; it’s about reliability. By integrating deep API knowledge with automated diagnostic tools, v2.0 reduces the "trial and error" loop that often slows down API integration.

Whether you're debugging conversion uploads or building complex reporting pipelines, v2.0 gives you the tools to work faster and with more confidence.

Getting Started

First installation

git clone https://github.com/googleads/google-ads-api-developer-assistant.git
In the project directory, run install.sh or install.ps1 to install the extension and client libraries.

Upgrading from a previous version

Copy any custom code from saved_code/ and saved_csv/ to a secure location.
Delete your local clone of the Google Ads API Developer Assistant by deleting your project directory and all sub-directories and files.
git clone https://github.com/googleads/google-ads-api-developer-assistant.git
In the project directory, run install.sh or install.ps1 to install the extension and client libraries.

Bob Hancock, Google Ads API Team

Additional changes for supporting European Union Political Ads Regulation in Google Ads API and Google Ads scripts

2026-02-26T09:14:00.000-08:00

What’s changing?

In 2025, Google rolled out changes to support the EU Political Ads Regulation in the Google Ads API and Google Ads scripts. On April 1, 2026, we will change account-level API restrictions. If you use either of these products to create or manage campaigns, you may need to update your application before April 1, 2026 to handle these enforcements.

API validation and enforcement changes

On April 1, 2026, Google Ads API and Google Ads scripts will implement the following changes in versions v20, v21, v22 and v23 of the API.

If a Google Ads account has one or more undeclared campaigns, all mutate calls related to campaign management will fail with a MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error.
You can determine if a campaign is undeclared by examining the Campaign’s missing_eu_political_advertising_declaration field.
All other calls – such as reporting, account management or keyword planner – will continue to work unaffected. See the full list of methods.
To declare currently undeclared campaigns, retrieve the list of eligible campaigns, and set their contains_eu_political_advertising declaration using the CampaignService.MutateCampaigns method, GoogleAdsService.Mutate method, or using the BatchJobService. These methods won’t fail with a MutateError.EU_POLITICAL_ADVERTISING_DECLARATION_REQUIRED error as long as you only update the campaign's contains_eu_political_advertising field. You can retrieve the list of undeclared campaigns by running the following GAQL query using either the Search or SearchStream methods of the GoogleAdsService.

    select campaign.id
      from
        campaign
      where 
        campaign.missing_eu_political_advertising_declaration = true

How will this affect my campaign serving?

Any campaign that has declared EU political ads by setting contains_eu_political_advertising to true will stop serving ads in the EU. Refer to the Help Center to learn more.

What do I need to do?

If your application uses either the Google Ads API or Google Ads scripts to create or manage campaigns, make sure to update your application to handle these enforcements before April 1, 2026.

How do I get help?

Reach out to the Google Ads API support or Google Ads scripts support channels if you have more questions about this change.

- Anash P. Oommen, Google Ads API Team

Announcing v23.1 of the Google Ads API

2026-02-25T15:21:00.000-08:00

Today, we’re announcing the v23.1 release of the Google Ads API. To use the new v23.1 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

We are also releasing minor versions v20.2, v21.1 and v22.1 of the Google Ads API to add additional support for the EU Political Ads Regulation.

Here are some of the key features in this release:

Added additional fields to support the EU Political Ads Regulation in the Google Ads API. The Campaign.missing_eu_political_advertising_declaration field supports querying and filtering campaigns that are missing declarations about whether they contain political advertising targeted towards the EU. The Customer.contains_eu_political_advertising field retrieves the account level declaration status of whether they contain political advertising targeted towards the EU.
Added the YouTubeVideoUploadService to support uploading and managing videos on YouTube, and the YouTubeVideoUpload resource to support fetching upload status and metadata.
Added support for text guidelines to the Campaign resource, which can be used with Performance Max and Search campaigns to programmatically control AI-generated text assets.
Added new metrics that report how many users saw your ad at least two, three, four, five or ten times: unique_users_two_plus, unique_users_three_plus, unique_users_four_plus, unique_users_five_plus, and unique_users_ten_plus.
Added ConversionActionCategory.YOUTUBE_FOLLOW_ON_VIEWS to support tracking users who watch an ad and later watch a video from the same channel.

Where can I learn more?

The following resources can help you get started:

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord or on our Ads Developers YouTube Live tomorrow (February 26th at 10a ET). This will also be recorded and posted on YouTube for those who can’t make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

For technical support issues, reach out to https://support.google.com/google-ads/gethelp

- Anash P. Oommen, on behalf of the Google Ads API Team

Announcing Android Google Mobile Ads SDK 25.0.0

2026-02-19T09:07:00.000-08:00

Version 25.0.0 of the Android Google Mobile Ads SDK is now available. We recommend upgrading as soon as possible to take advantage of the latest features, performance improvements, and API updates. This is a major version update that includes several breaking changes, new functionality for optimizing banner ad sizes, and important dependency updates.

New Large Anchored Adaptive Banner Size APIs

Unlock better performance with new banner ad sizes:

To better align with modern mobile devices, we are introducing the Large Adaptive Anchor API (e.g. AdSize.getLargeAnchoredAdaptiveBannerAdSize()). This update focuses solely on the sizing logic within adaptive anchor banners. While individual results may vary, larger ads are designed to increase engagement and revenue potential for publishers. The previous anchored adaptive APIs (e.g. AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize()) are now deprecated in favor of the new large anchored adaptive banner approach.

Old usage (Kotlin):

adView.setAdSize(AdSize.getCurrentOrientationAnchoredAdaptiveBannerAdSize(this, 360))

New usage (Kotlin):

adView.setAdSize(AdSize.getLargeAnchoredAdaptiveBannerAdSize(this, 360))

Breaking Changes and Removals

Version 25.0.0 is a major version with breaking changes that primarily impact mediation adapters and custom events.

API Removals:

The VersionInfo class in the com.google.android.gms.ads.mediation package has been removed. Use com.google.android.gms.ads.VersionInfo instead.
The deprecated getConfiguration() method in the RtbSignalData class has been removed. Developers should migrate to using getConfigurations() instead.
The deprecated onFailure(String) and onAdFailedToShow(String) methods have been removed from the following callback classes:
- SignalCallbacks
- MediationAdLoadCallback
- MediationInterstitialAdCallback
- MediationRewardedAdCallbackThe replacement methods are onFailure(AdError) and onAdFailedToShow(AdError).
- The NativeAdViewHolder class has been removed from the com.google.android.gms.ads.nativead package.

For the full list of changes, please refer to the release notes. We strongly encourage you to review our migration guide to ensure your mobile apps are ready to upgrade.

SDK Deprecation Reminder

Per the deprecation schedule, the release of version 25.0.0 means that:

Android Google Mobile Ads SDK versions 23.0.0 - 23.6.0 are officially deprecated.
Android versions 22.0.0 - 22.6.0 will sunset on June 30, 2026.

We strongly recommend updating to a supported SDK version to avoid any disruption in ad serving and to benefit from the latest SDK features and fixes.

To comment on this blog post or engage with fellow developers, join the Google Mobile Ads SDK Discord channel and share your thoughts.

- Jason Chiu, Mobile Ads Developer Relations

Announcing user list management and enhanced audience ingestion for the Data Manager API

2026-02-17T14:00:00.000-08:00

We're excited to announce the release of v1.5 of the Data Manager API, delivering a more comprehensive platform for data management. This update introduces powerful new capabilities for managing user lists alongside expanded options for audience member ingestion.

End to end user list management

The UserListService now allows you to oversee the lifecycle of your user lists entirely through the Data Manager API. It provides core resource management operations such as create, retrieve, update, and delete methods for UserLists, enabling full control over your audience management workflows.

Partner links

The introduction of the PartnerLinkService provides a secure way to manage connections between advertiser and data partner accounts across Google Ads and Display & Video 360.

Expanded audience member identifiers

The Data Manager API now supports additional user identifiers for audience ingestion. You can now upload User IDs, which can be used for Customer Match in Google Ads.

We’ve also integrated status reporting specific to User ID when you retrieve diagnostics for your ingestion requests. These updates make it easier to monitor User ID ingestion and quickly identify any issues.

Get started

Check out these Customer Match guides for a step-by-step walkthrough on how to create, populate, and verify audiences using the Data Manager API:
- Google Ads API Customer Match
- Display & Video 360 API Customer Match
Use the following guides to upgrade your existing Customer Match workflows to gain access to future improvements and features:
- Upgrade from the Google Ads API
- Upgrade from the Display & Video 360 API
Learn how to manage connections with data partners using the Partner links guides.

If you have questions or need help, contact us through the support page.

If you’re interested in becoming a data partner, please fill out the Partner Interest Form.

- Lindsey Volta, on behalf of the Data Manager API Team

Announcing iOS Google Mobile Ads SDK Version 13.0.0

2026-02-06T15:22:00.000-08:00

Version 13.0.0 of the Google Mobile Ads SDK for iOS is now available. We recommend upgrading as soon as possible to take advantage of the latest features, performance improvements, and API updates.

Updates in Version 13.0.0

Increased minimum deployment target: The minimum supported iOS deployment target has been raised to iOS 13.
Unlock better performance with new banner ad sizes: To better align with modern mobile devices, we are introducing the Large Adaptive Anchor API (e.g. largeAnchoredAdaptiveBanner). This update focuses solely on the sizing logic within adaptive anchor banners. While individual results may vary, larger ads are designed to increase engagement and revenue potential for publishers. The previous anchored adaptive APIs (e.g. currentOrientationAnchoredAdaptiveBanner) are now deprecated in favor of the new large anchored adaptive banner approach. For more API details, see the migration guide.
Old usage (Swift):
```
bannerView.adSize =
    currentOrientationAnchoredAdaptiveBanner(width: 375)
```
New usage (Swift):
```
bannerView.adSize = largeAnchoredAdaptiveBanner(width: 375)
```
Swift 6 concurrency support: This release continues to enhance support for Swift 6 strict concurrency, such as updating our delegate methods to only be accessed on the main thread.
Stricter type enforcement: The SDK will now raise an exception if any object that is not a String type is detected in the neighboringContentURLStrings array, ensuring better type safety.

For the full list of changes, please refer to the release notes. We strongly encourage you to review our migration guide to ensure your mobile apps are ready to upgrade.

SDK Deprecation Reminder

Per the deprecation schedule, the release of version 13.0.0 means that:

iOS Google Mobile Ads SDK versions 11.x.x are now officially deprecated.
Version 10.x.x will sunset on June 30, 2026.

We strongly recommend updating to a supported SDK version to avoid any disruption in ad serving and to benefit from the latest SDK features and fixes.

To comment on this blog post or engage with fellow developers, join the Google Mobile Ads SDK Discord channel and share your thoughts.

- Justin Malandruccolo, Mobile Ads Developer Relations

An update on Google Ads API developer token access applications

2026-02-06T13:15:00.000-08:00

With the recent release of Explorer Access for the Google Ads API, Google Ads API MCP server and the Google Ads API Developer Assistant, we are seeing significant interest in the developer community for Google Ads API access, and are receiving an increase in developer token access applications. As a result, there is also an increased delay on reviews for these applications.

We have heard from the developer community that the applications for developer token access levels are taking longer than usual. We are aware of this issue, and have added additional reviewers to process the applications and clear the backlog. We have fast-tracked some applications, so some of you should already start seeing your applications getting approved.

If you have Explorer Access, continue to use it if it meets your needs, as it provides the same campaign management and reporting features as Basic and Standard levels.

Upgrade to Basic Access only if:

You consistently exceed your daily quota.
You are planning for growth and expect you will exceed quotas.
You are blocked by features unavailable in your current Access Level (Test or Explorer).

How can I support the progress of my application?

If you have an ongoing Basic Access application, regardless of whether you currently have Test Account Access or Explorer Access, you can take the following actions to help us move your application forward with fewer requests for additional information:

Ensure that the accounts you plan to manage are listed as children under the Google Ads Manager account from which you signed up for the developer token, when possible.
Complete advertiser verification for one or more accounts under the Google Ads Manager account from which you signed up for the developer token. If you already have verified accounts under a different Manager account, you may link those accounts under the API Manager account instead.
If you are using other Google APIs and have completed the OAuth App verification process for your Google Cloud project in the past, then update your Basic Access application to include the Google Cloud project number. If you have a new Google Cloud project, consider completing the OAuth App verification process and sharing the project number with the review team.
Update your Basic Access application with clear, specific details of your use case, including why your current level of access doesn’t meet your needs. Your explanation should be a few sentences long, that helps us understand both your business, and your API use case. We will reject applications that are unclear.

For technical support issues, reach out to https://support.google.com/google-ads/gethelp

- Anash P. Oommen, on behalf of the Google Ads API Team

Announcing the Google Mobile Ads Next-Gen SDK for Android

2026-01-29T15:41:00.000-08:00

We are announcing the Google Mobile Ads (GMA) Next-Gen SDK for Android, a significant rewrite of the Google Mobile Ads SDK that prioritizes speed, stability, and an improved developer experience. See the developer guides to get started today (AdMob | Ad Manager).

Currently available in Open Beta, the GMA Next-Gen SDK is scheduled for General Availability (GA) in July 2026. We encourage you to explore the new SDK and its potential benefits for your applications.

Advantages of the GMA Next-Gen SDK

Improved Performance: Benefit from notable reductions in ad request latency. The new Google Mobile Ads SDK offers up to 27% faster ad request latency for banner ads than our previous version¹. The new SDK also features background initialization to minimize impact on application startup times.
Reduced Application Size: The new Google Mobile Ads SDK file size is up to 17% smaller than our previous version².
Modern Language Support: Developed in Kotlin, the SDK provides idiomatic APIs for developers working in both Kotlin and Java.
Faster Release Cycles: The GMA Next-Gen SDK benefits from a more frequent and regular release schedule, providing quicker access to new features and bug fixes.
Comprehensive Feature Support: Continues to use all existing Google Mobile Ads formats and features within your applications.

Early adoption successes

Publishers participating in the beta program have reported positive outcomes compared to the previous SDK:

50% increase in Average Revenue Per User (ARPU).
91.5% uplift in Average Revenue Per Daily Active User (ARPDAU).
1/3 reduction in ANR rate and a 50% reduction in slow cold starts.
16% increase in fill rate.

Further details on these outcomes can be found in the GMA Next-Gen SDK success stories.

Live events

The following upcoming live events are encouraged for those interested in the GMA Next-Gen SDK:

Introductory webinar: An overview focused on the advantages of the GMA Next-Gen SDK and best practices for implementation.
- EMEA/APAC session: Live webinar broadcasted on February 19th. (Register)
- AMER session: Live viewing of recording on February 24th. (Register)
- February 26th - Discord technical overview session: A technical introduction of the GMA Next-Gen SDK specifically for developers. Register (Accept Invite)
- March 4th - Discord banner migration live coding session: A practical demonstration of migrating banner ads from the previous SDK to the GMA Next-Gen SDK. Register (Accept Invite)
- March 11th - Migration hackathon: AI-Based migration to the GMA Next-Gen SDK with a dedicated MCP server and vibe coding. If interested, please reach out to your Google account manager.

Implementation resources

Get started with these Next-Gen SDK resources:

Integration guide: The latest version and setup instructions are available in our GMA Next-Gen SDK Get Started guide (AdMob | Ad Manager).
Migration guide: Instructions to migrate to the GMA-Next Gen SDK (AdMob | Ad Manager).
Developer samples: Example applications demonstrating SDK usage are available in our GitHub repository.
Introduction video: For an overview of the SDK's benefits, please watch our introductory video.

We invite you to integrate the Google Mobile Ads Next-Gen SDK and discover the performance and stability enhancements it can bring to your Android applications.

If you have any questions or need additional help, please join the GMA Next-Gen SDK channel to share your thoughts and get in contact with the team.

- Justin Malandruccolo, Mobile Ads Developer Relations

¹ Google Internal Data, Latency Measurement for Banner Ads, Google Mobile Ads SDK vs. New Google Mobile Ads SDK, August 21, 2025 to September 3, 2025.

² Google Internal Data, Increase to app file size when adding the SDK, Google Mobile Ads SDK vs. new Google Mobile Ads SDK, September 29, 2025.

Introducing Channel-Level Reporting for Performance Max campaigns

2026-01-29T08:25:00.000-08:00

Following yesterday's launch of Google Ads API v23, we are excited to share more details about one of the most highly requested features: Channel-level reporting for Performance Max campaigns.

This update provides developers and advertisers with unprecedented transparency into where their Performance Max ads are serving, allowing for deeper optimization and more granular performance insights.

Greater transparency with channel breakdowns

Starting with v23, you can now retrieve performance data broken down by channel—such as Google Search, Search Partners, GMail, YouTube, Display, Discover, and Maps. This functionality is available at the campaign, asset group and asset level, allowing you to see how specific creative assets are performing across different environments.

In previous versions of the API, using the ad_network_type segment for Performance Max campaigns typically returned a MIXED enum value. With the release of v23, the API will now return the specific channel breakdowns.

Note for developers: This is a significant change in behavior. When you upgrade your queries to v23, you will begin to see more detailed results than in previous versions. Please ensure your reporting systems are prepared to handle these specific enum values instead of the generic MIXED result.

Additional segments to consider

While the channel breakdown is new to v23, it works in tandem with powerful segmentation fields introduced in v22: ad_using_product_data and ad_using_video.

ad_using_product_data: Use this segment to distinguish performance between ads that utilize your Merchant Center product feed versus those that do not.
ad_using_video: This segment allows you to isolate performance data for ad impressions that included a video component.

By combining these segments with the new v23 channel reporting, you can now gain highly specific insights, such as understanding the conversion value of video-based ads specifically on the YouTube channel versus the Display Network. Or if you’re a retailer, use the ad_using_product_data segment to see data for Shopping ads for Search, Dynamic Remarketing ads for Display and video ads that showcase your products on YouTube.

Implementation details

To get started with these new reporting capabilities, you should update your client libraries to v23. You can find detailed technical documentation and example queries in our PMax reporting guides.

Important notes:

Performance reports will only return channel-level data for dates on or after June 1, 2025.
While channel reporting is available at the campaign, asset group, and asset levels via the API, reporting at the asset group level is exclusive to the API and will not be available in the Google Ads web interface.

If you have any questions or want to discuss this post, please reach out to Google Ads API support or start a discussion on our “Google Advertising and Measurement Community” Discord server.

- Sarah Pollack, Google Ads API Team

Announcing v23 of the Google Ads API

2026-01-28T15:21:00.000-08:00

Today, we’re announcing the v23 release of the Google Ads API. This marks the first release of 2026 and the beginning of our move to a faster release cadence.

To use some of the v23 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

Here are some of the key features in this release:

Enabled ad network type breakdown for Performance Max campaigns.
InvoiceService.ListInvoices can now return more granular details in Invoice including campaign-level cost breakdown, itemized regulatory costs, and adjustment information. To get these details, set include_granular_level_invoice_details in ListInvoicesRequest.
You can now specify start and end times for certain campaign types. The new fields Campaign.start_date_time and Campaign.end_date_time replace Campaign.start_date and Campaign.end_date, respectively.
Store location details are now available in PerStoreView. You can retrieve the store location column shown in the Stores report via the API.
Added a new LIFE_EVENT_USER_INTEREST dimension. This allows users to build audiences using Life Events with AudienceInsightsService and ContentCreatorInsightsService.
The ReachPlanService.GenerateConversionRates response now includes surfaces, allowing for different conversion rate suggestions based on surface controls (for example, Gmail, Shorts). This is only supported for Demand Gen campaigns.
Added a new AudienceInsightsService.GenerateAudienceDefinition method that lets you to translate a free text description of a target audience into matching audience attributes using generative AI.
ShoppingPerformanceView now supports new competitive metrics and conversion metrics segmented by conversion date.

Where can I learn more?

The following resources can help you get started:

Come join us for a walkthrough of this release in our "Google Ads API Release Highlights" event on Discord on January 29th at 11am ET. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel there.

For technical support issues, reach out to https://support.google.com/google-ads/gethelp

- Anash P. Oommen, Google Ads API Team

Campaign Manager 360 API v4 Sunset Reminder

2026-01-26T07:59:00.000-08:00

Campaign Manager 360 API v4 will be sunset on February 26, 2026. Starting on this date, all v4 API requests will begin to fail. If you’re still using this version, we strongly encourage you to migrate to v5 as soon as possible to avoid service interruptions.

See the migration guide for details on how to upgrade. In most cases, you will just need to upgrade to the latest version of your preferred client library. We also recommend reviewing the release notes for important changes that may affect your implementation.

If you have questions, please contact Campaign Manager 360 API support.

- Lindsey Volta, on behalf of the Campaign Manager 360 API Team

Campaign and Insertion Order targeting will sunset in Display & Video 360 API and Structured Data Files on February 23, 2026

2026-01-21T10:14:00.000-08:00

In November, we announced the upcoming sunset of Campaign and Insertion Order targeting in the Display & Video 360 API and Structured Data Files. This sunset will take place on February 23, 2026 to align with the removal of this targeting in the Display & Video 360 UI.

Starting February 23, 2026, you will see the following behavior when using the Display & Video 360 API and Structured Data Files:

API requests to methods that retrieve or manage AssignedTargetingOption resources directly under Campaign or InsertionOrder resources will return a 404 error.
API requests to advertisers.lineItems.generateDefault will return a 404 error.
All targeting columns in Campaign and Insertion Order SDFs will be empty upon file download and must be empty upon file upload. Campaign or Insertion Order file entries with populated targeting columns will fail on upload. See our documentation for a full list of impacted columns.

Full details on these changes can be found on our Display & Video 360 API deprecation announcements.

If you need help with these new features, please contact us using our Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Changes to IP Address and Session Attribute Support in the Google Ads API

2026-01-07T08:31:00.000-08:00

Starting on February 2, 2026, the Google Ads API will no longer accept new adopters of session attributes or IP address data as part of conversion imports. To ensure a more robust and scalable experience for handling complex data, we recommend that Google Ads API developers transition to the Data Manager API - where session attributes and IP address are accepted - as their primary conversion and user data import API.

Developers who have already adopted session attributes or IP addresses in their click conversion imports can continue importing that data using the Google Ads API until they’ve moved their conversion imports over to the Data Manager API.

Technical details

Developers will be allowlisted by their developer token.
Once this change is rolled out, you may notice the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in the partial_failure responses of your conversion import requests. This error indicates that the associated conversion was rejected due to the presence of session attributes and/or IP address.
Resolve this error with these steps:
- Temporarily remove session attributes and IP address from conversion import requests and continue importing conversions to the Google Ads API.
- Update your code to use the Data Manager API with session attributes and IP address.
- Discontinue conversion imports to the Google Ads API once you’re successfully making imports to the Data Manager API.

Reach out to the Google Ads API support or Data Manager API support channels if you have any questions.

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.

- Ben Karl, on behalf of the Google Ads API Team

Google Ads API v19 sunset reminder

2025-12-15T10:28:00.000-08:00

Google Ads API v19 will sunset on February 11, 2026. Starting on this date, all v19 API requests will begin to fail. Migrate to a newer version prior to February 11, 2026 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

You can view a list of methods and services your project has recently called using the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.
Click Google Ads API in the table.
On the Metrics subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v19.services.GoogleAdsService.Mutate.
(Optional) Choose the timeframe you want to view for your requests.

If you have questions while you're upgrading, reach out to us at googleadsapi-support@google.com. You can also discuss this post in our Google Advertising and Measurement Community Discord server.

- Ben Karl, on behalf of the Google Ads API Team

Update your PAL integration for new limited ads behavior

2025-12-10T14:19:00.000-08:00

The Programmatic Access Library (PAL) is updating user privacy and data usage settings, and requires implementation updates as these changes go live. This update introduces the following changes:

PAL reads Transparency & Consent Framework (TCF) data from the device to determine user consent for local storage.
Adds an optional forceLimitedAds property to manually enable limited ads.
Removes the functionality of the existing allowStorage property.

The following diagram shows the new behavior:

PAL is changing to this behavior in the following releases:

HTML5 v1.90.0, behavior change targeting March 10th, 2026
Android v23.0.0
iOS v3.0.0
tvOS v3.0.0

Starting in these versions, PAL uses Transparency & Consent Framework (TCF) data from the device to determine user consent for local storage. If the automatic TCF based determination is insufficient, your app can directly set the forceLimitedAds property. Setting the forceLimitedAds property to a true value enables limited ads.

To keep the current behavior in your app, you might need to update your implementation. For details about the code changes, see the Limited ads and first party identifier settings guide for HTML5, Android, iOS, or tvOS.

Follow the PAL HTML5 migration plan

To prevent runtime errors, the HTML5 PAL SDK keeps the allowStorage property. The allowStorage property will be supported until March 10th, 2026. The PAL HTML5 SDK observes the following behavior:

What is changing?

On March 10th, 2026, PAL SDK ignores the allowStorage property, and its value no longer influences limited ads behavior.

To avoid breaking changes, do the following before March 10th, 2026:

Always set the allowStorage property to a true value.
Optionally, you can force limited ads regardless of the TCF determination by setting the forceLimitedAds property to a true value.

For more details about the code changes you need to make for PAL HTML5, see Limited ads and first party identifier settings.

Give us your feedback

We intend these changes to provide transparency on user consent and privacy preferences. If you have questions about this update, please reach out to us via the Google Advertising and Measurement Community Discord Server in the #developers channel under Google Ad Manager.

- Jackson Sui, Interactive Media Ads Developer Relations