Google Ads API v26: Search Lift, PMax and Faster Releases

Google is making new advertising capabilities available to software, dashboards and AI-assisted workflows more quickly. Released on October 14, 2026, Google Ads API v26 introduces 15 Search Lift metrics, API-based creation of eligible Local Services Performance Max campaigns, updated enhanced conversions settings, and additional compliance and video-disclosure fields. The changes matter most to advertisers whose reporting, CRM connections or campaign operations depend on the API.

The immediate question is not whether every advertiser should adopt v26. It is whether the systems behind their marketing are ready for its measurement and compatibility changes. Google is moving to two releases per month, but only major versions are expected to introduce breaking changes. That distinction matters for teams managing automated campaigns and measurement at scale.

The changes in Google Ads API v26 at a glance

Google’s official v26 announcement highlights faster access to features for automated workflows. The impact varies by account type.

Area	What changed	Why it matters
Search Lift	A read-only keyword-bundle resource, new segments and 15 metrics	Teams can bring eligible lift results into their reporting stack.
Local Services Performance Max	Eligible campaigns can now be created through the API	Agencies and software providers can automate setup with stricter validation.
Enhanced conversions	Account configuration and effective status use new fields	Conversion-tracking integrations may need code changes.
Compliance and video	Conditional EU political-ad declarations and YouTube disclosure metadata	Automated workflows need additional targeting and creative checks.
Release cadence	Two API releases per month, starting with v26	Teams must review changes more frequently, without assuming every release breaks code.

Search Lift improves measurement access. Local Services PMax changes campaign creation. Enhanced conversions brings integration compatibility work. They solve different problems.

Search Lift reporting becomes easier to connect to business results

Search Lift estimates the change in organic search queries associated with ad exposure by comparing exposed users with a control group. Unlike attributed conversions, it measures incremental search interest, not leads or revenue.

Google Ads API v26 adds the read-only SearchLiftKeywordBundle resource, two Search Lift segments and 15 metrics, including relative search lift, normalized incremental searches, impressions and cost. The campaign’s lift_measurement_config links to the associated measurement configuration. According to Google’s Search Lift reporting documentation, querying accounts must be on an allowlist managed by Global Product Solutions (GPS). The resource exposes results from eligible studies; it does not let every advertiser start a new study through the API.

For example, a B2B SaaS company running YouTube awareness campaigns might compare incremental searches for its brand or product category between exposed and control audiences. Where an eligible study exists, a dashboard could place those Search Lift results alongside campaign spend, branded search trends and downstream CRM opportunities. A rise in search interest would support an awareness hypothesis, not prove incremental pipeline or closed-won revenue.

Our analysis of Google Ads Data Strength Uplift makes the same distinction: easier access to a measurement signal is not itself proof of incremental business growth.

Local Services Performance Max gains API-based campaign creation

This capability is restricted to eligible Local Services Performance Max campaigns. It is not a new campaign type available to every PMax or B2B SaaS advertiser. Approved tools can create these campaigns through v26, including a local_services_enabled flag set to true at creation; that flag cannot be changed later. The API requires country_code and listing_id for the corresponding Google Business Profile listing, and checks listings, supported service categories, agreements and campaign settings. See Google’s v26 release notes for the creation requirements.

The update also links Local Services leads to campaigns and adds coupon and message-lead categories. For agencies with eligible service clients, this can reduce setup work and improve lead reporting.

For SaaS advertisers outside Local Services, this is primarily an API infrastructure development to watch, not a new acquisition tactic. Lead quality and eligibility checks remain necessary, regardless of how quickly an eligible campaign can be created.

Enhanced conversions now require a closer look at the configuration fields

One important breaking change affects applications that inspect enhanced conversions configuration. Google removed ConversionTrackingSetting.enhanced_conversions_for_leads_enabled, which was accessed through Customer.conversion_tracking_setting. In v26, use ConversionTrackingSetting.enablement_setting to read the configured account-level setting and ConversionTrackingSetting.effective_enablement_setting to read the effective setting. Google’s announcement describes these as Customer.enablement_setting and Customer.effective_enablement_setting in the customer resource context. Both settings are represented by the EnhancedConversionsConfig enum. See Google’s field reference and v26 migration notes for the exact field paths.

The effective setting is particularly important for accounts using cross-account conversion tracking because the value can be inherited from the manager account. Both fields are read-only in the API. Dashboards and integration checks relying on the removed field need an update before moving to v26; the schema change does not, by itself, enable enhanced conversions or improve the quality of uploaded leads.

For a B2B team, the operational test is whether a conversion recorded in Google Ads corresponds to a meaningful CRM event. Duplicate leads, inconsistent sales stages and unqualified form fills require data hygiene, regardless of which API version a dashboard uses.

For teams trying to connect advertising to revenue, this belongs within a broader B2B SaaS measurement framework, not just a developer ticket.

Compliance and campaign controls become more detailed

Google made the EU political advertising declaration optional under defined targeting conditions. Broadly, campaigns positively targeting locations outside the EU, without qualifying proximity or location-group criteria, may no longer need the declaration. Demand Gen campaigns with upgraded targeting are assessed against relevant active ad groups. A targeting change can make the declaration necessary again.

Google Ads API v26 also introduces a YouTube generative content disclosure field within video-upload metadata. Teams building upload workflows can now account for that disclosure in the API process, rather than assuming every upload is handled through an interface.

Three additional changes deserve attention:

• Demand Gen and Shopping: A currency-level field exposes the minimum daily Demand Gen budget, while Shopping campaigns gain expanded listing_type support.
• Search budget recommendations: A new recommendation identifies campaigns whose daily budget may be too low for performance. More budget should still depend on qualified conversions and business goals.
• Travel advertising: Hotel-specific bid-modifier names and related errors have been replaced with terms that work across more travel categories. Existing criterion IDs and targeting behavior stay the same, but code references may need updating.

Budget suggestions still need judgment. Our Google Ads automation framework explains why a platform suggestion should be checked against lead quality and account objectives before anyone applies it.

The breaking changes worth testing before migration

Because v26 is a major API release, some changes are not backward compatible. That makes a tested migration more sensible than swapping the version number in production.

Integration area	Change to check	Practical test
Enhanced conversions	Removed legacy field; new configured and effective settings	Confirm account-status queries still return the correct values.
Local Services PMax	Country code and listing ID are required at creation	Test eligible and ineligible campaign requests, including validation errors.
Travel bid modifiers	Hotel-specific names, types and errors changed	Update field mappings and error-handling checks.
Client libraries	New v26-compatible releases are required	Upgrade the supported library and rerun report, mutate and conversion workflows.

For example, Google lists Python 34.0.0, Java 48.0.0 and .NET 27.5.0 as minimum client-library versions for v26. The exact requirement depends on the language and whether a later minor release is needed.

Teams using AI-assisted development can use guidance from our Google Ads API Developer Assistant coverage to support query checks and troubleshooting. Generated code still needs testing against real accounts and conversion behavior.

Two releases a month changes the maintenance rhythm

Beginning with v26, Google plans two API releases per month, with four major versions per year. The remaining releases will be minor updates intended to add features without breaking existing integrations. This gives reporting platforms and AI-powered advertising agents quicker access to new functionality. It does not require advertisers to migrate to a new breaking version every two weeks. Google’s official announcement explains the faster cadence.

Major versions can introduce breaking changes and should be planned and tested. Minor versions share their parent major version’s sunset date and are intended to be non-breaking. Teams therefore need a more frequent review rhythm, not a mandatory breaking migration twice each month.

That still makes release monitoring worthwhile. Integrations and agents built with Google Ads MCP rely on specific resources, permissions and tools, so changes should be evaluated against the functions those systems actually use.

Google currently schedules a November 2027 sunset for v26 and its minor releases, subject to change. Use the published schedule for migration planning, but test relevant changes well before any sunset date.

Five actions for marketing and SaaS teams

1. Inventory the integrations. Identify scripts, dashboards, ETL jobs, client libraries and third-party tools that call the Google Ads API. Use the Google Cloud Console to inspect recent API methods and versions where possible.
2. Test measurement first. Check enhanced conversions settings, existing conversion uploads and the definition of qualified leads before relying on refreshed reporting.
3. Validate campaign creation. If you manage eligible Local Services accounts, test country, listing, agreement and goal checks before allowing automated campaign creation.
4. Put human approval around changes. Search budget recommendations, geo-targeting updates and agent-generated actions need clear account ownership and review rules.
5. Create a release review routine. Assign an owner to assess changes against actual integrations, test relevant updates and document when an upgrade is necessary.

A routine Google Ads audit can also reveal tracking and campaign-structure problems that API upgrades alone will never solve.

What marketers should watch next

First, track Search Lift study eligibility. The v26 reporting fields can help automate analysis for allowlisted customers, but the quality of the experiment and its relationship to business outcomes determine how useful the results are.

Second, watch adoption of API-created Local Services Performance Max campaigns among eligible businesses, with validation and lead follow-up quality monitored alongside speed of setup.

Third, monitor the major/minor release notes and test any changes affecting conversion tracking, automated campaign creation, YouTube disclosure and AI-agent permissions.

OneMetrik Takeaway

Google Ads API v26 is a useful infrastructure release, not a shortcut to better advertising results. Search Lift reporting becomes easier to automate. Eligible Local Services PMax campaigns become easier to create. Enhanced conversions configuration becomes more transparent, while some existing integrations must change.

The part worth taking most seriously is operational discipline. Two releases per month reward teams that know which API features they rely on, who owns their measurement pipeline and how they test changes before production.

For OneMetrik’s approach to marketing automation, the useful opportunity is reliable account monitoring: connecting ad performance to CRM stages, checking conversion signals, and allowing AI-assisted workflows to flag anomalies before a manager approves changes. Faster APIs make that workflow more responsive, but they do not replace campaign strategy or human accountability.

Google Ads API v26 FAQs