What changed: Google’s Ads Developer Blog announced Google Ads API Developer Assistant v4.0.0 on August 25, 2026. It moves the assistant from a standalone project setup to a unified plugin architecture for Antigravity and Claude Code. It can validate GAQL, inspect schemas, generate code and run reports, but the project says mutate code is not executed by the assistant and must be reviewed and run manually outside it.
That makes v4 relevant to API developers and marketing-operations teams—not a new Google Ads campaign feature. The release is a major, incompatible change for earlier layouts, so the right first step is to read the pre-installation guide, back up custom output and verify credentials, client libraries and API-version parity.
I checked the official blog and Google-maintained repository on August 30, 2026. DMT’s Google Ads API v25.1 guide covers a separate versioned API/Shopping migration; this page covers the named assistant and its safe operating boundary.
What v4 adds for Google Ads API teams
| Capability | Source-backed description | Safe first use |
|---|---|---|
| GAQL validation | Checks syntax, field compatibility, date segmentation and zero-impression rules before a query runs. | Validate a read-only query against a non-sensitive or approved customer ID and inspect the generated query. |
| Schema inspection | Inspects Protobuf fields, types and enum definitions for an active API version. | Compare the local schema/version with the client library installed in the project. |
| Code generation | Generates tested/idiomatic Python, Java, PHP, .NET and Ruby examples using client libraries. | Save generated code in a review branch; lint and review before any execution. |
| Diagnostics | Helps investigate offline-conversion uploads, manager hierarchies and Performance Max listing filters. | Use a bounded customer ID and redact output before sharing it. |
| Ad hoc reporting | Constructs, validates and runs GAQL against a live Google Ads account and can save results as CSV. | Start with a read-only report, confirm date range/segments and write to an approved directory. |
| Mutate operations | The repository says the assistant generates mutate code but does not execute it. | Keep code review, approval, testing and manual execution outside the assistant. |
When Claude Code is the host, keep the assistant’s API scope separate from broader browser, file and computer workflows. DMT’s Claude host-agent governance guide provides that adjacent context; it is not a substitute for Google Ads API authentication review.
The v4 migration boundary
Google calls v4.0.0 a major release that is not compatible with prior releases and tells users to read README_BEFORE_INSTALLATION.md before installing. If you are upgrading from v2 or v3, the repository’s guide says to back up custom code and saved output, remove the legacy .agents/settings.json if present, update or re-clone the repository, run the platform installer and reload the host.
| Before v4 | Repository migration instruction | Evidence to retain |
|---|---|---|
| v2 legacy output | Back up saved_code/ and saved_csv/. | File inventory and secure backup location. |
| v3 output | Back up saved/code/ and saved/csv/. | File inventory and owner. |
| Legacy config | Remove .agents/settings.json if it exists; v4 uses the plugin system and config/. | Review record showing the old file was not needed by another tool. |
| Credentials | The guide says home-directory credential files are preserved and do not need to be recreated. | Do not copy secrets into the repository; verify the approved credential path. |
| Host | Install the matching Antigravity or Claude Code plugin and reload/restart the host. | Host/version record and installation reviewer. |
Prerequisites before an API call
- Familiarity with Google Ads API concepts and authentication.
- A Google Ads API developer token and the approved customer/manager scope.
- A configured credential file: for example,
google-ads.yamlfor Python,google_ads_php.inifor PHP orgoogle_ads_config.rbfor Ruby. - An Antigravity or Claude Code environment.
- A local clone of the client library for the language you plan to use.
- Python 3.10 or newer if you intend to execute the default generated Python code.
Credentials and customer IDs are access boundaries, not ordinary prompt context. Use the minimum approved scope, do not paste secrets into chat or commit them, and redact account data before sharing a report. If your workflow also touches campaign strategy, DMT’s Google Ads automation guide provides the broader automation context; it does not replace API access review.
Version parity is part of the setup
The repository says the assistant uses local client-library sources as the primary source for Protobuf schemas, resource definitions and enum descriptors, while executing with the installed google-ads package. Its tools compare the installed package version with the local client-library version and warn when they differ. Resolve a mismatch before trusting a generated field or query. A successful import is not proof that the API version, schema and runtime agree.
A validate-first workflow for marketers and developers
- Confirm the official repository URL and read the pre-installation guide for the current release.
- Back up custom code and saved CSV/output paths outside the repository.
- Record the host, installed assistant version, client-library version and active Google Ads API version.
- Run a schema inspection or GAQL validation before querying account data.
- Run one bounded read-only report with a fixed customer ID, date range, segments and output directory.
- Review query text, returned fields, cost/volume implications and redaction before sharing.
- Generate code only in a review branch and run lint/tests; do not run mutate code from an unreviewed response.
- For a real account change, use the normal approval, test and manual-execution process outside the assistant.
The same evidence discipline applies to API-driven campaign settings. Keep DMT’s target-bidding change checklist and language-targeting migration guide as separate policy/setting references rather than asking a code assistant to infer an account change.
For a concrete campaign surface that an API team might inspect, see DMT’s Demand Gen and asset update. Use it as a campaign-context reference only; the Developer Assistant documentation remains the source for v4 capabilities and API safeguards.
What this release does not prove
- It does not prove that your developer token or manager account can access every requested customer.
- It does not make generated code correct for your business rules, current API version or consent/privacy obligations.
- It does not turn live reporting into a qualified CRM or revenue result.
- It does not authorize campaign, user, budget, bid or conversion mutations.
- It does not replace Google Ads API documentation, code review, secret management or change approval.
Frequently asked questions
Is v4 compatible with the old standalone setup?
Google describes v4.0.0 as a major release that is not compatible with prior releases. Read the repository’s pre-installation guide, back up custom output and remove legacy configuration only after confirming it is not used elsewhere.
Can the assistant change my Google Ads campaigns?
The repository says it can generate mutate code but will not execute it. A human must review and execute a change outside the assistant. Keep customer scope, approvals, testing and credentials under your normal account-governance process.
Does it run reports against live data?
Yes, the official blog and README describe ad hoc reporting that builds and validates GAQL, runs it against a Google Ads account and can save CSV output. Start with an approved read-only scope, fixed dates and redacted output; the article makes no claim about your account access or report quality.
Which host platforms are supported?
The August 25 announcement names Antigravity and Claude Code. The repository provides platform-specific installation paths for each. Check the current README before installing because commands, supported client libraries and host requirements can change.
