Google this week published the version 2.0 of its Google Ads API Developer Assistant on February 26, 2026, marking a substantial shift in how the tool approaches the most friction-prone parts of API integration. Where the previous releases focused heavily on code generation, v2.0 extends the assistant's role into automated diagnostics, session lifecycle management, and structured troubleshooting support for conversion tracking - one of the most technically demanding areas of the Google Ads API.

The announcement was made by Bob Hancock of the Google Ads API Team through the official Google Ads Developer Blog. According to the post, the update "transforms the Assistant from a powerful code generation tool into a proactive troubleshooting and automation partner for Google Ads developers."

The jump from v1.6.0 to v2.0.0 is framed around three recurring developer complaints: the complexity of setting up multi-language environments, the difficulty of diagnosing offline conversion tracking failures, and the need for tighter alignment with the latest API version. Each of those pain points receives a dedicated treatment in this release.

Simplified installation and project structure

Installation has been streamlined with a new --install-deps flag for both install.sh and install.ps1 scripts. That single command handles pip, Composer, and Bundler dependencies in one pass, eliminating the need to manage package managers separately across different environments. For developers working across Python, PHP, and Ruby simultaneously, this is a practical time-saver.

The directory structure has also been consolidated. All generated code, CSV exports, and diagnostic reports now land under a single saved/ directory, subdivided by output type. Previously, outputs were dispersed, making it harder to locate specific files during debugging or when preparing support requests. A parallel update.sh command handles version upgrades for both the API and its client libraries, and can also add additional client libraries to the working context.

Agentic conversion troubleshooting

The most significant new feature is a dedicated Conversion Troubleshooting and Diagnostics suite. According to the announcement, offline conversion tracking is described as "one of the most powerful - yet complex - features of the Google Ads API," and diagnosing attribution failures has historically required substantial manual investigation.

V2.0 addresses this with two new components. The first is a Python script - api_examples/collect_conversions_troubleshooting_data.py - that executes a set of standard reports relevant to conversion issues and provides contextual data for the Assistant to work with. The second is a new command, /conversions_support_data, intended for use after the Assistant has already attempted to solve a problem and failed.

What makes this command notable is its output. When invoked, it analyses customer settings, conversion actions, and upload summaries, then generates a structured diagnostic report. According to the announcement, "it even identifies 'unhealthy' states and high failure rates automatically, saving you hours of log diving." The report saves to a text file that can be attached directly to a formal support request, shortening the back-and-forth that typically accompanies complex conversion debugging cases.

This agentic approach to diagnostics reflects a broader trend in Google's developer tooling. Google released an open-source MCP server for its Ads API in October 2025, enabling natural language queries against advertising data. The Developer Assistant now occupies a complementary but distinct position - focused not on querying data conversationally, but on guiding developers through structured debugging workflows with machine-generated output.

Full Google Ads API v23 support

Version 2.0 fully supports Google Ads API v23, which launched on January 28, 2026. All interactive examples have been updated, and the Assistant's internal context has been reconfigured to reflect the latest resources and fields in that version. According to the announcement, this ensures "the code you generate is production-ready."

Google Ads API v23 introduced channel-level reporting for Performance Max campaigns, enabling developers to break down performance across Search, YouTube, Display, Gmail, Maps, and Discover for the first time through programmatic interfaces. The Developer Assistant's alignment with v23 means that developers generating GAQL queries or campaign management code through the tool will receive output calibrated for those new capabilities. For teams that have already upgraded their client libraries to access v23 features, this alignment removes a potential version mismatch that could produce outdated or incompatible code.

The Google Ads API moved to a monthly release cadence starting in January 2026, as announced in September 2025, increasing major releases from three to four per year and extending version support windows to one full year post-launch. Keeping the Developer Assistant current with each major version is therefore more operationally demanding than it was under the previous quarterly schedule.

Session hooks and automatic configuration

Two new lifecycle hooks - SessionStart and SessionEnd - enable automation at the boundaries of each working session. On startup, the Assistant can now automatically locate a developer's configuration file in the $HOME directory and copy it into a config/ subdirectory within the project. This removes the manual step of pointing the tool to credentials before beginning work.

A detail worth noting for multilingual developers: Python is described as Gemini's preferred language for querying the API. When a developer is working in another language, the Assistant reads the existing configuration file and generates a temporary google-ads.yaml in the config/ subdirectory to handle its own queries, while continuing to produce output in the developer's chosen language. On session exit, temporary configurations are deleted automatically. Credentials do not persist between sessions unless the developer explicitly manages that through their own configuration files.

Smarter GAQL validation

GAQL - Google Ads Query Language - is the query interface for the Google Ads API, and building complex queries across multiple resource types, date segments, and conditional filters is an area where errors are common and sometimes subtle. V2.0 updates both GEMINI.md and conversions/GEMINI.md with more rigorous validation rules targeting the latest API edge cases. The announcement specifically calls out "improved handling of date segments and finite range requirements," which have historically tripped up developers writing queries that cross reporting period boundaries.

The practical effect is that the Assistant now catches logic errors before a query is executed rather than returning empty results or API errors at runtime. For developers iterating rapidly across large accounts, catching bad queries at generation time rather than at execution time is a meaningful workflow improvement.

Skills: an experimental extension mechanism

V2.0 also introduces a new concept called Skills - described in the announcement as "a mini-plugin or a 'behavior blueprint.'" Unlike general context files such as GEMINI.md, which provide persistent background information, a Skill is loaded into the AI only when it needs to perform a specific complex or procedural task. The developer does not invoke Skills directly; Gemini decides when to apply one based on the task at hand.

According to the announcement, Skills remain "an experimental feature," and v2.0 ships with one Skill included - designed to complement the session hooks for initialization and cleanup. The architecture suggests an intent to expand this system in future versions, allowing more complex behaviors to be modularized and selectively activated.

Context for the marketing community

The Google Ads API Developer Assistant was identified as one of three catalysts behind a surge in developer token applications that caused a processing backlog at Google in early February 2026. The other two were the MCP server and the new Explorer Access tier. That surge indicates the tool has drawn substantial interest since its earlier releases, even before this v2.0 update.

For marketing technology vendors and agencies building programmatic advertising tools, the conversion troubleshooting features carry particular weight. Offline conversion tracking - the process of uploading CRM or point-of-sale data back to Google Ads to attribute ad-driven actions that happened outside digital channels - is a critical component of attribution for many B2B and retail advertisers. When uploads fail silently or conversions are not attributed as expected, diagnosing the cause requires working through customer settings, conversion action configurations, and upload job summaries in sequence. The new diagnostics suite compresses that process and outputs a structured report usable for both internal debugging and formal support escalation.

The session automation features, while less dramatic, address the repetitive configuration overhead that accumulates across multi-language, multi-account development environments. Agencies managing dozens of client accounts through the API will benefit from consistent credential handling at session boundaries, reducing the risk of accidental credential persistence in development environments.

Google's approach with v2.0 also continues the pattern visible in its documentation overhaul from August 2025 and the launch of the developer Discord community in July 2025 - incremental but sustained investment in developer experience rather than product-level announcements. Each of those initiatives responded to developer feedback. The v2.0 release, with its explicit reference to acting on feedback from the v1.6.0 release, follows the same logic.

For developers currently on v1.6.0 or earlier, the upgrade process requires removing the existing local clone entirely, cloning fresh from https://github.com/googleads/google-ads-api-developer-assistant.git, and running install.sh or install.ps1. Any custom code stored in the previous saved_code/ or saved_csv/ directories should be moved to a secure location before deletion. The new unified saved/ directory structure replaces both of those locations.

Timeline

Summary

Who: Google's Ads API Team, specifically Bob Hancock, announced the update. The primary audience is developers building tools on top of the Google Ads API, including marketing technology vendors, agencies, and independent developers.

What: Version 2.0 of the Google Ads API Developer Assistant was released, introducing an agentic conversion troubleshooting suite with a new diagnostic script and /conversions_support_data command, session lifecycle hooks (SessionStart/SessionEnd) with automatic credential management, a unified saved/ directory structure, a single-command --install-deps flag for multi-language setup, full Google Ads API v23 support, improved GAQL validation targeting edge cases around date segments and finite ranges, and an experimental Skills mechanism for modular behavior loading.

When: The announcement was published on February 26, 2026 through the official Google Ads Developer Blog.

Where: The tool is distributed through GitHub at https://github.com/googleads/google-ads-api-developer-assistant.git. The announcement appeared on the Google Ads Developer Blog. The tool itself runs locally in a developer's environment, interfacing with the Google Ads API and powered by Gemini.

Why: The update addresses developer feedback collected since the v1.6.0 release, focusing specifically on the three most difficult aspects of Google Ads API integration: environment setup across multiple languages, conversion tracking diagnostics, and maintaining alignment with the latest API version. The conversion troubleshooting features are particularly relevant because offline conversion attribution is a technically complex process where failures are difficult to trace manually. The v2.0 release reduces the time cost of that diagnostic work and improves the quality of information available when escalating issues to Google support.

Share this article
The link has been copied!