Yes, Google Ads API has moved to twice-monthly releases, starting with version v26. This means that instead of a single major version update every few months, Google now releases a new version of the API on the first and third Monday of each month. This change, announced in early 2025, is designed to deliver new features and fixes to advertisers and developers more quickly, while also requiring them to stay more vigilant about version upgrades.
What the Change Means for Developers
For developers who build and maintain integrations with the Google Ads API, this shift is significant. Previously, you might have upgraded your codebase once or twice a year, when a new major version (like v17, v18, etc.) was released. Now, with v26 and beyond, you’ll need to plan for a new API version every two weeks. Each release can include new features, deprecations, or changes to existing resources and methods. This means your client library and code will need to be updated more frequently to avoid breakage and to take advantage of new capabilities.
The key practical implication is that you should no longer think of an API version as a long-term commitment. Instead, treat each release as a short-lived snapshot. Google has stated that versions will be supported for a limited time, and you’ll need to upgrade to the latest version to continue receiving updates and support. This is a move towards a more agile, continuous delivery model, similar to how many SaaS companies now ship features.
Why Google Made This Change
The primary motivation behind the twice-monthly release cadence is speed. Google wants to get new features, performance improvements, and bug fixes into the hands of advertisers faster. In the past, a developer might have to wait months for a new API version to access a feature that could improve their campaign performance. With bi-weekly releases, that wait is dramatically shortened.
Another reason is to align the API with the rapid pace of change in the digital advertising ecosystem. New ad formats, bidding strategies, and measurement tools are constantly emerging. A faster release cycle allows Google to respond to these market changes and regulatory requirements more quickly. It also allows them to iterate on API design based on developer feedback, since they can release improvements and adjustments more frequently.
How the Release Schedule Works
The new release schedule is straightforward: a new version of the Google Ads API is released on the first and third Monday of every month. For example, in 2025, v26 was released on the first Monday of the month, and subsequent versions (v27, v28, etc.) will follow every two weeks. Each version is a distinct API endpoint, and you must explicitly specify the version in your requests (e.g., /v26/, /v27/).
Here’s what you need to know about the lifecycle of each version:
- Release: The new version is made available on the scheduled Monday.
- Deprecation: After a certain period (typically around one year, but you should check the official deprecation schedule), the version will be marked as deprecated. You’ll see warnings in the API response headers.
- Sunset: Once deprecated, the version will eventually be sunset and will no longer accept requests. You must migrate to a newer version before this date.
Google provides a deprecation schedule in their documentation, listing the exact sunset dates for each version. It’s crucial to monitor this schedule and plan your upgrades accordingly.
How to Choose the Right Version
For most developers, the answer is simple: always use the latest stable version. Since each version is only supported for a limited time, sticking with an older version will eventually lead to service disruption. Google’s client libraries (for Java, Python, PHP, .NET, Ruby, Perl, and Node.js) are updated to support the latest version, so you can easily upgrade by updating your library.
However, there are times when you might want to stay on a slightly older version for a short period. For example, if you’ve discovered a bug in the latest version, or if you need more time to test your code against the new changes. In that case, you can use the previous version, but you must have a migration plan in place. The general rule is to upgrade as soon as possible, ideally within a few weeks of a new release.
Common Problems and How to Avoid Them
The most common problem developers face with the new release cadence is falling behind on upgrades. Because versions are only supported for about a year, you cannot afford to ignore new releases for long. Here are some other common issues:
- Breaking changes: Each new version may contain breaking changes to existing resources or methods. Always read the release notes for each version to understand what has changed.
- Client library version mismatch: If you upgrade the API version in your code but forget to update the client library, you’ll encounter errors. Always keep your client library up to date.
- Testing fatigue: With releases every two weeks, you’ll need to run your test suite more frequently. Automate your testing as much as possible to catch issues early.
- Deprecation warnings: Pay attention to the deprecation headers in API responses. They will tell you when your current version is scheduled to be sunset.
To avoid these problems, set up a regular schedule to review the release notes and plan your upgrades. Consider using a versioned CI/CD pipeline that can quickly test and deploy your changes.
Comparison to Other APIs
Google’s move to twice-monthly releases is not unique in the industry, but it is more aggressive than many other major APIs. For example, the Facebook Marketing API and the Microsoft Advertising API typically have less frequent, larger version updates. This puts Google Ads API at the forefront of agile API development.
This faster cadence has both pros and cons compared to slower release cycles:
- Pros: Faster access to new features, quicker bug fixes, and a more responsive API that adapts to market changes.
- Cons: Higher maintenance burden on developers, more frequent testing and upgrades, and a greater risk of breaking changes affecting your integration.
For large enterprises with complex integrations, this can be a significant operational challenge. For smaller teams or agencies using third-party tools, the impact is often mitigated because the tools themselves are updated by their providers.
Costs and Safety Considerations
There is no direct cost associated with using the Google Ads API itself; you pay for your advertising spend, not for API access. However, there is an indirect cost: the development time required to keep up with the release cadence. This is a real cost that should be factored into your budget.
From a safety perspective, the main risk is service disruption. If you fail to upgrade before a version is sunset, your API calls will start failing, which could halt your advertising campaigns. To mitigate this, set up alerts for deprecation warnings and schedule regular maintenance windows. There are no security implications specific to the release cadence, but as with any API, you should follow best practices for authentication and data handling.
Alternatives and Future Outlook
If you find the twice-monthly release cadence too demanding, you have a few alternatives. You can use a third-party management platform (like Google Ads Editor, or a bid management tool) that abstracts away the API versioning for you. These tools handle the upgrades internally, so you don’t have to worry about the API version.
Another alternative is to use the Google Ads UI directly for smaller tasks, but for automation and scale, the API is still the best option. Looking ahead, it’s likely that Google will continue this release cadence for the foreseeable future. They may also introduce longer support windows for certain LTS (Long-Term Support) versions, but as of now, no such plan has been announced. The key takeaway is to embrace the change and build your development processes around the new rhythm.
Frequently Asked Questions
What happens if I don’t upgrade to the latest version?
If you stay on an older version, you will eventually reach its sunset date, after which the version will no longer be available. Your API requests will fail, and your integration will stop working. You should always upgrade before the sunset date to avoid disruption.
How long is each version supported?
Google has not committed to a fixed support period, but based on the current schedule, versions are typically supported for around one year. You should check the official deprecation schedule for the exact sunset dates of each version.
Can I skip versions and upgrade directly to the latest?
Yes, you can skip intermediate versions. You don’t need to install every single release. You can upgrade directly from your current version to the latest one, but be aware that you’ll need to account for all the changes that were introduced in the versions you skipped.
Will the client libraries be updated automatically?
Yes, Google’s official client libraries are updated to support each new version. You can simply update your library to the latest version to get support for the new API version. However, you’ll still need to review the release notes for any breaking changes that might affect your code.
Is there a way to test the new version before upgrading?
Yes, you can use the Google Ads API sandbox environment to test your code against a new version before you upgrade your production environment. This is highly recommended to ensure your integration is compatible.
Related
Formula used
in t | Finish time | min | 50 | 0 in d | Distance | km | 10 | 0 | 100000 out pace | Average pace | min/km | t / d | 2 out speed | Average speed | km/h | d / (t / 60) | 2
Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.
More cards in this drawer
- Data Center Security: Encryption, Backups, Access
- Best Mini PCs for Gaming: Top Picks
- Phone Buttons: Clever Ways to Use Them
- Resonance Solstice Codes: What They Are
- Blue Protocol Star Resonance: Best Graphics Settings for Smooth FPS
- Jack Daniel’s Ransomware: Data Stolen?