Google Ads API v22 has been released, requiring client library upgrades. Key features include Smart Bidding Exploration for Target ROAS, new asset generation for DemandGen campaigns, a beta AssetGenerationService using generative AI, and enhancements for Performance Max campaigns. New bidding goals for App campaigns for installs are also introduced. More resources are available in release notes and guides. A walkthrough event is set for October 16th.
Google Ads is discontinuing the call-only ad format, requiring API users to switch to Responsive Search Ads (RSAs) with call assets. This change aims to enhance campaign performance using machine learning. Starting January 2026, new call-only ads cannot be created through the API, while existing ones will remain until February 2027. Users should update their API integrations and migrate to RSAs to benefit from improved performance and ensure a smooth transition.
Marketing Auditor simplifies your audit process, letting you generate comprehensive, white-label reports in just a few clicks. Save over 10 hours per report while analyzing 200+ data points and delivering 50+ pages of actionable insights. Customize reports with professional themes or your own branding, and export them in editable formats like PowerPoint or Google Slides to showcase your expertise.
The Google Ads API Model Context Protocol (MCP) Server is now open source, improving access to Google Ads data for AI tools and developers. The MCP standard enables Large Language Models to connect with external data sources. This initial release is read-only for reporting and diagnostics. Users can report technical issues via the GitHub repo or contact Google Ads API support for assistance. For discussions, join the Google Advertising and Measurement Community Discord.
V21 of the Google Ads API had a field incorrectly named in the BudgetPerDayMinimumErrorDetails message, where minimum_budget_amount_micros was misspelled as minimum_bugdet_amount_micros. This error is fixed in V22 and will also be corrected in V21 starting October 15th, 2025. Users of supported client libraries must update their code to reflect the correct field name when upgrading. REST API users should ensure their code uses the correct name.
Google Mobile Ads mediation adapters are now available for iOS projects via Swift Package Manager (SPM), simplifying integration. Supported adapters include AppLovin, DT Exchange, IronSource, Liftoff Monetize, i-mobile, inMobi, Meta, Mintegral, Pangle, and Unity, each with specific minimum versions. More adapters will be added soon, and users can check the GitHub page for updates. For questions, reach out on the Google Advertising and Measurement Community Discord.
From November 17, 2025, Google Ads will change how customer conversion goals are set. New conversion actions will be account-default only if all existing goals in the same category are account-default, preventing unnecessary targeting and improving campaign performance. Users must manually set goals as account-default by setting CustomerConversionGoal.biddable to true. Support resources are available for guidance.
Google Ads has updated enhanced conversions for leads diagnostics, improving visibility into conversion import implementation. Changes include a new alert for importing limited user-provided data, a 'Good' status for tagless setups, updated alert priorities, complete visibility of all alerts, and the removal of the CLICK_NOT_FOUND error. These enhancements aim to help users quickly identify and resolve common issues to boost performance.
We’re excited to announce a refresh of the Google Ads scripts documentation. The updates include logically grouped guides for easier navigation, a dedicated reference tab for quick access to scripts objects, and a combined solutions and examples resource for sample code. These changes aim to enhance efficiency and align the documentation with the Google Ads API. More updates are expected, and feedback from the community is encouraged.
The google-ads-bom for the Google Ads API client library for Java is released in version 40.0.0, simplifying dependency management and enhancing integration stability. A BOM centralizes dependency version management, preventing conflicts with libraries like Guava and GAX. To use it, import the BOM in your build file and omit version specifications for the google-ads dependency. The BOM automatically manages versions for libraries like Guava, Protobuf, GAX, and gRPC.
