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

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:

1. 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.
2. 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

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:

• Release Notes
• Upgrade from a previous version
• Guides
• Reference
• Diff between v23 and v22

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

 - Anash P. Oommen, Google Ads API Team

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

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

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

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

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

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

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:

• Release Notes
• Upgrade from a previous version
• Guides
• Reference
• Diff between v23 and v23.1
• Diff between v23 and v22

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

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

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

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

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:

• Release Notes
• Upgrade from a previous version
• Guides
• Reference
• Diff between v23 and v22

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

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 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:

• Upgrade to the newest version
• Release notes

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

1. Open APIs & Services in the Google Cloud Console.
2. Click Google Ads API in the table.
3. 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.
4. (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

Announcing the release of the Google Ads API Developer Assistant, a powerful extension for Gemini CLI designed to streamline your Google Ads API workflows. This tool allows you to interact with the Google Ads API using everyday language, making it easier than ever to get information, generate code, and even retrieve data directly in your terminal.
Whether you're new to the Google Ads API or a seasoned developer, this assistant can help you work more efficiently.

What Can It Do?

The Google Ads API Developer Assistant (v1.0) enhances the Gemini CLI with several key features:

1. Natural Language Q&A: Have questions about the Google Ads API? Just ask!
   • "What are the available campaign types?"
   • "Tell me about reporting for Performance Max campaigns."
   • "How do I filter by date in GAQL?"
2. Natural Language to Code Generation: Describe what data you need, and the assistant will generate the Google Ads Query Language (GAQL) and executable Python code using the google-ads-python client library as context so the code conforms to best practices.
   • "Show me campaigns with the most conversions in the last 30 days."
   • "Get all ad groups for customer '123-456-7890'."
   • "Find disapproved ads across all campaigns."
   • Generated code is automatically saved to the saved_code/ directory.
3. Direct API Execution: Run the generated Python scripts directly from the command line. The assistant will execute the read-only API calls and display the results, often formatted neatly as tables within your terminal.
4. CSV Export: Need to save your data? You can easily export the tabular results from API calls to a CSV file. Just ask:
   • "Save the results to a CSV file"
   • Files are saved in the saved_csv/ directory.

How Does It Work?

This extension leverages the Gemini CLI's ability to use context from GEMINI.md files and settings within .gemini/settings.json. By configuring the assistant with paths to your local google-ads-python library clone and example directories, it provides relevant and accurate code generation.

Getting Started

Here's what you need to get up and running:
Prerequisites:

• Familiarity with Google Ads API concepts and authentication.
• A Google Ads API developer token.
• A configured google-ads.yaml credentials file in your home directory.
• Python >= 3.10.
• The Gemini CLI installed.
• A local copy of the google-ads-python client library. (The setup script can clone this for you.)

Please refer to the README file in the GitHub repository for detailed setup instructions and examples.

Where to Find It

The Google Ads API Developer Assistant is available on GitHub.

Community & Support

We encourage you to try it out! Your feedback is valuable and can be provided in this survey. Join the discussion in the #ads-api-ai-tools channel of our Discord.

Please use the GitHub Issues tab in the repository to report bugs, suggest features, or ask for support. Check out CONTRIBUTING.md for contribution guidelines.

Happy Coding!
Bob Hancock, Google Ads API Team

The Data Manager API, a new solution for data ingestion across Google’s advertising platforms, is now generally available. This API is designed to streamline how advertisers, agencies, and data partners send and manage their first-party data, saving valuable time and resources while ensuring data is handled securely.

Simplification

The Data Manager API simplifies how you send data to audience lists and conversions used in your Google campaigns. Instead of building and maintaining multiple API integrations, you can now send data once and apply it to different Google ads solutions. For advertisers who prefer API connections, this provides a streamlined and scalable way to activate first-party data across multiple campaign types and platforms.

Our vision is universal activation and measurement i.e. bring your data and activate/measure across Google campaigns, GMP campaigns and Google Analytics. At launch use cases include:

Security and Privacy at the Core

The Data Manager API is also built with advanced, privacy-centric features. The API supports confidential matching for several use cases. This includes the option to encrypt data for audience and conversion events, allowing you to pass encrypted customer information (for example, an email address or phone number), which is processed in a trusted execution environment. This includes audience lists for Customer Match.

In the coming months, the Data Manager API will expand support to include additional use cases across Google Ads, Google Analytics, Display & Video 360, Search Ads 360, and Campaign Manager 360.

Get Started Today

Unlock a more efficient, scalable, and secure way to manage your data. The Data Manager API is available to all developers now. Head over to the developer documentation to get started. If you have any questions or need help, check out the Data Manager API support page for options.

- Melissa Ng, Data Manager API Product Manager

To streamline our technical support channels, we will be sunsetting the following developer support forums on Google Groups:

• Google Ads API
• Google Ads Scripts
• Campaign Manager 360 API

Effective January 28, 2026,

• Support agents will no longer respond to new forum posts. Send your questions using the recommended support channels mentioned below.
• If you reply to any existing forum threads with the support teams on or after this date, they will initiate a new email thread to continue your discussion.

We plan to disable the ability to create new forum posts at a later date in 2026, but the existing forum content will remain visible as a read-only archive for the time being, so you can still access past discussions and solutions.

Where can I get technical support for these products?

Our developer site and other documentation has been updated to the new preferred technical support channels. Moving forward, the best way to reach us for technical support for these products will be through our official support channels below:

• Google Ads API: https://developers.google.com/google-ads/api/support/contact
• Google Ads Scripts: https://developers.google.com/google-ads/scripts/docs/support/contact
• Campaign Manager 360 API: Contact the Campaign Manager 360 support team for assistance.

As always, when submitting a support request, please provide all relevant details to help us expedite the resolution of your issues. This typically includes:

• For Google Ads API: Always include the request-id found in the response logs, along with the complete request and response logs.
• For Google Ads Scripts: Include the script name, Customer ID, and any relevant execution logs or error messages from the Google Ads UI.
• For Campaign Manager 360 API: Provide relevant IDs (e.g., Profile ID, Account ID), the API method, and the full request and response logs if possible.
• All Products:
  • A clear description of the issue
  • What you expected to happen
  • Steps to reproduce the issue
  • Relevant code snippets
  • Any error messages received

Providing comprehensive information upfront will help our team diagnose and assist you more effectively. The support page will guide you on the necessary information.

If you’re looking for updates, events, or non-support focused conversation with Googlers or fellow members of the developer community on the products listed above, please join us on our “Google Advertising and Measurement Community” Discord server.

We appreciate your understanding as we make this transition to better focus our support resources.

- Aalap Shastri, Google Ads API Team

We are rolling out a new Explorer Access level access tier for Google Ads API over the next couple of weeks. This will allow new developers signing up for Google Ads API to gain immediate access to production accounts, no longer limited to test accounts. Here’s how it will work:

• Most new developers who sign for the Google Ads API will immediately be given Explorer Access level upon completing onboarding steps.
• Explorer Access level will give developers the ability to work with live serving accounts immediately.
• To limit abuse, developer tokens with Explorer Access will have some restrictions on functionality, such as creating new advertiser accounts and keyword planning.
• Explorer Access will allow 2880 operations/day.
• Developers can apply for Basic Access or Standard Access levels to increase the daily operation limits and remove the restrictions on functionality.

Existing developers are unaffected by this change. For example, those with Test Account Access, Basic Access and Standard Access levels will continue to have these access levels.

In the future, the Google Ads API team will continue to streamline the onboarding process with additional improvements, so stay tuned.

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.

 - Anash P. Oommen, Google Ads API Team