Google Ads API v25.1 is a minor, no-breaking-change release for v25, but it still deserves an integration review. Google published it on August 19, 2026, with new lift, benchmark, sentiment, loyalty, conversion-value, and reach-planning capabilities. The urgent implementation check is separate: from August 31, Shopping campaigns will enable Local Inventory Ads by default, so code that tries to force enable_local=false must be replaced or tested against the new behavior.
This guide explains what marketing and engineering teams should update, what belongs to the larger Google Ads API v25 migration, and how to protect an online-only Shopping setup. It is an implementation checklist, not a claim that the release will improve every account’s performance.
The short version
- v25.1 is a minor release. Google describes it as a drop-in upgrade for v25 and says the minor version has no breaking changes. Update the client library and code if you need the new services or fields.
- v25 is still the major migration boundary. Teams moving from an older major version must audit removed lifecycle-goal resources, changed types, renamed fields, and other v25 release-note changes.
- Some features are restricted. Conversion Lift and Brand Lift capabilities are allowlisted; the API surface alone does not grant account access.
- Shopping needs a deadline check. Google says Local Inventory Ads become enabled by default for Shopping campaigns on August 31, 2026. The old
enable_local=falseassumption is not a safe control for v25.1 and later.
If your team only consumes ordinary campaign and reporting resources, v25.1 may be a straightforward library update. If your integration manages lifecycle goals, Shopping inventory, lift measurement, creator insights, or custom reporting, read the release notes and run a targeted compatibility review before deploying.
What Google Ads API v25.1 adds
Google’s v25.1 announcement groups the release around measurement, insights, planning, and new reporting dimensions. The practical value depends on account access, the client library you use, and whether your team has a real decision to support with the data.
| Area | What changed | Possible marketing use | Important limit |
|---|---|---|---|
| Conversion Lift and Brand Lift | New lift measurement resources, metrics, dimensions, and winner scores. | Evaluate incremental impact and brand response where a lift study is appropriate. | Lift features are allowlisted; contact the account representative. |
| Benchmarks | Filter benchmark categories, discover available sources, and read aggregate cost, views, and share-of-voice metrics. | Give planning and reporting teams a more relevant peer context. | Benchmark scope and available categories must be checked for the customer. |
| Brand Sentiment Insights | Existing ContentCreatorInsightsService now supports new brand-sentiment messages and data. | Use structured sentiment signals in creator or brand analysis. | Do not treat a new resource as proof of causal brand impact. |
| Loyalty and conversion value | Loyalty-membership segmentation and a conversion-value-rule dimension, plus original conversion value. | Separate customer-value reporting and compare unadjusted with adjusted values. | Define the business meaning of each value before changing optimization logic. |
| Reach planning | Parental-status targeting is available in reach planning. | Make planning scenarios more specific where the dimension is relevant. | Planning availability is not the same as campaign delivery or performance evidence. |
There are also fields that help teams observe migration, including campaign timestamps related to upcoming AI Max and broad-match migrations. They are useful for operational visibility; they do not mean an account has completed a migration or that a campaign will automatically improve.
v25.1 is minor; v25 is the migration boundary
The official release notes date v25 to July 22, 2026 and v25.1 to August 19, 2026. That distinction matters. A team can read “no breaking changes” in the v25.1 note and still miss work required when its integration moved from v24.x to v25.
One material v25 change is the removal of legacy CustomerLifecycleGoal and CampaignLifecycleGoal resources, services, settings, and enums. Google points developers toward the unified goal schema, including new-customer-acquisition settings. The release notes also describe changed fields, renamed enums, required request values, removed fields, and a changed customer_metrics response type. Which items matter depends on the services your code calls.
That makes “drop-in” a version-specific statement, not a blanket migration promise. Record the running API version first, then compare your calls and generated client types with the v25 and v25.1 release notes.
The August 31 Shopping deadline is the urgent code check
Google’s Local Inventory Ads announcement says that Shopping campaigns will enable Local Inventory Ads by default starting August 31, 2026. The change is designed to align Shopping campaigns with Performance Max for Retail, but it creates a concrete check for teams that previously relied on the Shopping setting’s enable_local value.
| Code or version context | What Google says | What to do |
|---|---|---|
| v25.1 and later, Shopping campaign | Trying to set Campaign.ShoppingSetting.enable_local=false returns ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. | Remove the old mutation and implement the intended inventory scope explicitly. |
| Before v25.1, Shopping campaign | Requests that mutate the field are treated as true. | Do not assume the old false value prevented local inventory; test the effective campaign behavior. |
| Online-only intent | Google points to a CampaignCriterionService listing scope with product_channel=ONLINE, or the UI Inventory filter. | Use the documented scope/filter and verify the resulting product and campaign coverage. |
| Performance Max or Demand Gen | The enable_local field continues to function for these campaign types. | Keep the check scoped to the campaign types affected by the announcement. |
This is not a claim that every advertiser must suppress local inventory. The decision belongs to the feed, fulfillment, and campaign strategy. The important point is to replace an implicit or ineffective boolean with an intentional scope and a read-back test.
A safe Google Ads API upgrade sequence
- Inventory production. Record the API version visible in logs or Google Cloud monitoring, the language and client-library version, and the services used by each job. Do not infer the running version from a repository branch name.
- Read both release boundaries. Use the v25 and v25.1 release notes. Treat the v25.1 note as a minor upgrade only after the integration is already compatible with v25.
- Search the code and generated types. Start with the affected names below, then extend the search to any resources your integration calls.
CustomerLifecycleGoal
CampaignLifecycleGoal
enable_local
customer_metrics
original_conversion_value
aca_migration_date_time
broad_match_migration_date_time- Compile and test the real workflows. Exercise goal management, reporting, Shopping campaign updates, feed/listing scopes, and any lift or benchmark calls in a non-production customer. Test error handling as well as successful responses.
- Check capability and access. Confirm allowlisting for lift features, discover available benchmark categories, and document which customer accounts actually expose each resource. A method appearing in the client library is not account approval.
- Stage the Shopping decision. If the business wants online-only inventory, implement the documented listing scope or Inventory filter and compare product coverage before and after. If local inventory is desired, verify that local feed and fulfillment data are ready for the default.
- Roll out with read-back. Deploy in a narrow cell, record API errors and effective campaign settings, and expand only when reporting, feed coverage, and campaign behavior match the intended design.
What marketers should monitor after the update
Give the engineering and marketing teams a shared checklist. Marketing should know which measurement questions the new fields answer, while engineering should know which operational decisions the account depends on.
- Measurement: whether lift studies are available and whether their design answers an incremental question, rather than merely adding another dashboard metric.
- Benchmarks: which categories and sources are returned, how the comparison set is defined, and whether aggregate metrics are being mistaken for a forecast.
- Value: how original conversion value differs from values adjusted by rules or lifecycle logic, and which value the reporting or bidding workflow uses.
- Shopping: local versus online inventory coverage, product eligibility, and errors from any remaining
enable_local=falsemutation. - Migration: v25 lifecycle-goal compatibility and campaign timestamps that indicate upcoming AI Max or broad-match migration work.
For wider context, see DMT’s guides to AI for Google Ads, target CPA and ROAS changes, language targeting, Merchant API migration, and ChatGPT product feeds. Those articles cover adjacent marketer and feed decisions; this release checklist is the API-specific owner.
What this release does not prove
- It does not prove that v25.1 will increase conversions, return on ad spend, or brand lift for a particular account.
- It does not make allowlisted lift features available to every customer.
- It does not turn benchmark aggregates into a target or guarantee a competitive position.
- It does not mean a v25.1 library update completes the v25 major migration.
- It does not let a Shopping integration rely on
enable_local=falseas an online-only control after the documented behavior change.
The decision for your team
If you already run v25 and do not need the new resources, schedule v25.1 through your normal dependency and regression process. If you are still migrating from an older major version, treat v25.1 as the final step after the v25 audit, not as a shortcut around it. And if you manage Shopping campaigns, make the Local Inventory Ads decision explicit before August 31: enable and validate local offers, or use Google’s documented online-only listing scope or Inventory filter.
The best next action is small and verifiable: identify the production API version, search for the affected fields and services, test one representative Shopping workflow, and record the effective result. That gives marketing and engineering a shared answer before the deadline instead of relying on a release headline.
Sources: Google Ads API v25.1 announcement, Google Ads API release notes, and Google’s Local Inventory Ads default notice. Check the live documentation and your account’s effective behavior before production deployment.
