Google released version 25.1 of the Google Ads API on Wednesday, August 19, 2026, adding read-only access to conversion lift and brand lift study data, category scoping for competitive benchmarks, creator sentiment retrieval, loyalty tier segmentation, an unadjusted conversion value metric and parental status targeting in reach forecasts. Two of the six features are restricted to allowlisted accounts.

The release arrived through the Google Ads Developer Blog under the name of Anash P. Oommen of the Google Ads API Team, the same author who signed the v24.2 and v25 announcements earlier this year. Its framing is deliberately low-drama. According to Google, v25.1 is a "drop-in upgrade for v25," which in the vocabulary of this API means no breaking changes, no removed resources and no forced code rewrites. Developers running against v25 can pull the latest client library and query the new surfaces without renegotiating their integrations.

That distinction carries weight because the previous release did not offer it. Google Ads API v25 removed the CustomerLifecycleGoal and CampaignLifecycleGoal resources on July 22, 2026, breaking any pipeline that configured lifecycle goals programmatically. Minor releases in this cycle are additive by design. Major releases are where things disappear.

Google also scheduled a live walkthrough of the release for August 20 at 10am ET, running simultaneously on the Google Advertising and Measurement Community Discord server and the Ads Developers YouTube Live channel, with a recording posted afterwards for those who could not attend. Questions were directed to the ads-api Discord channel and, for technical support, to the separate Google Ads API support channel.

Lift measurement becomes queryable, not configurable

The largest item in v25.1 concerns measurement. Two new read-only resources, LiftMeasurementConfig and LiftMeasurementFlight, expose the internals of lift studies to API consumers. According to Google, these allow inspection of study configurations, flight dates, campaign details and conversion goals.

Read-only is the operative constraint. Nothing in this release lets a developer create, modify or terminate a lift study through the API. The study is still set up inside the Google Ads interface or through an account representative; what changes is that its parameters and results can now be pulled into external systems rather than transcribed from a dashboard.

The release includes 24 new Conversion Lift metrics along with winner score metrics intended for statistical analysis. Brand lift arrives as a set of dimension resources rather than a single table: LiftMeasurementAgeRange, LiftMeasurementCampaign, LiftMeasurementDevice, LiftMeasurementGender and LiftMeasurementVideo. The structure implies that brand lift results can be sliced by demographic and creative dimensions in the same query grammar the API uses elsewhere for segments.

Both features are available only to allowlisted Google Ads accounts, and Google directs interested advertisers to their account representative to request access. That gate is not incidental. It places the most substantive part of the release outside the reach of self-serve developers and inside the managed-account relationship, which is where lift studies have historically lived anyway.

Why incrementality data moving into the API matters now

Lift measurement has been widening its addressable base for roughly two years. Google lowered the minimum budget for incrementality experiments to 5,000 dollars in November 2025, down from thresholds that had approached six figures, and made Conversion Lift results visible at product or brand level inside the Lift Measurement table in Google Ads. Guidance published at the time recommended minimum study durations of 14 days, noting that studies running shorter than that showed drops of up to 17% in Absolute Lift for businesses with longer conversion lags.

Those studies produced numbers that lived in one interface. Pulling them into a warehouse alongside spend, attributed conversions and marketing mix model outputs required manual export. Exposing configuration and flight metadata programmatically changes the joinability of that data, because a lift result without its exposure window and campaign scope is difficult to reconcile against anything else. The winner score metrics point in the same direction: statistical significance handled as a queryable field rather than a badge on a screen.

The commercial context is worth stating plainly. Lift studies measure the causal contribution of Google inventory using Google's own randomised control groups, and the API now makes those figures easier to feed into models that adjudicate budget between channels. Whether independent verification of those control groups improves as a result is a separate question, and one this release does not address.

Benchmarks gain a category filter and share of voice

BenchmarksService, which generates comparative performance figures against other advertisers, receives a category_filter parameter in its GenerateBenchmarksMetrics method. According to Google, supported categories can be discovered through ListBenchmarksSources, and the filter scopes benchmark analysis to advertisers within specific Product & Service Categories.

Unscoped benchmarks are a blunt instrument. A regional furniture retailer compared against the entire advertiser population learns little; compared against advertisers in a matched category, the comparison acquires some diagnostic value. The release also surfaces new customer ad metrics covering aggregate cost and views, plus share metrics including share_of_voice, through AggregateMetrics and ShareMetrics.

Share of voice is a competitive metric with a history in this API. Version 22 introduced fixed share of voice as a bidding strategy in October 2025. Microsoft Advertising added share of voice metrics for its Performance Max implementation on November 10, 2025. Google Analytics separately expanded its benchmarking capability to 20 additional unnormalised metrics on October 2, 2025, and benchmarking against anonymised peer averages appeared inside Google Analytics again on August 10, 2026. Competitive comparison is being assembled across several surfaces at once, and v25.1 supplies the programmatic version.

Creator sentiment enters the insights service

ContentCreatorInsightsService now supports brand sentiment data through a new BrandSentimentInsight resource, which returns sentiment distributions and summaries for creators and brands.

The service itself is restricted to allowlisted customers and has been accumulating capability steadily. Version 24 removed the is_brand_connect_creator field from GenerateCreatorInsights and GenerateTrendingInsights, one of several removals in that April 2026 release. Version 25 then opened detailed YouTube channel insights covering average views, likes, comments, engagement rate and audience attributes for creators who consented to share non-public data.

Sentiment is a different category of signal from those. Views and engagement rate are counts. A sentiment distribution is a model output, and Google's announcement does not describe the methodology behind it, the data sources it draws on, or how brand sentiment is distinguished from creator sentiment when a creator features multiple brands. Agencies building creator shortlists programmatically acquire a new column without a published definition of what generates it.

Loyalty tiers become a reporting and bidding dimension

Two changes connect loyalty programme membership to conversion measurement. Segments.loyalty_membership allows report metrics to be segmented by the loyalty tier of converting users. Separately, a new LOYALTY_MEMBERSHIP value in ConversionValueRulePrimaryDimension records when a loyalty membership condition was satisfied for a conversion value rule.

The second is the more consequential of the pair. Conversion value rules modify the recorded value of a conversion based on impression dimensions such as audience, location, device or travel itinerary, and those adjusted values feed automated bidding. Adding loyalty membership as a primary dimension makes the rule's trigger auditable in reporting, which matters when a bidding strategy is optimising against values that no longer match transaction amounts.

Loyalty has been expanding across Google's commerce surfaces on a parallel track. Google extended loyalty programme features to 14 countries on March 25, 2026, pushing member pricing and benefits into local inventory ads, regional Shopping ads and AI-powered surfaces including AI Mode and the Gemini app. Loyalty data entering the bidding layer is the logical continuation of that.

An interface metric arrives in the API, nine months later

Metrics.original_conversion_value surfaces the unadjusted conversion value from biddable conversions, measured before conversion value rules or customer lifecycle goal adjustments are applied.

Practitioners have had this figure in the interface since late 2025. The Original Conversion Value column appeared in Google Ads accounts during November 2025, described in the platform tooltip as showing the unadjusted value before value rule adjustments or lifecycle goal adjustments. Its purpose was diagnostic: separating genuine movement in results from movement produced by the rules layered on top.

The nine-month gap between interface availability and API availability is a familiar pattern, and it is precisely the gap that Google's release cadence change was meant to narrow. Reporting parity of this kind is unglamorous and, for anyone reconciling API pulls against interface exports, it removes a specific class of discrepancy.

Reach planning adds parental status

ReachPlanService now supports parental_statuses targeting within both Targeting and PlannableTargeting, extending reach forecasting and plannable product discovery. Version 22 had already added parental_status and income_ranges to AudienceInsightsService.GenerateInsightsFinderReport, and renamed the views field in ReachPlanService to trueview_views.

Access to this service is tiered. ReachPlanService is blocked entirely under Explorer Access, the intermediate developer token level Google introduced on February 6, 2026 alongside an acknowledged application backlog. Planning capability therefore remains conditional on holding Basic Access or higher, which is a constraint on who can use the new targeting dimension at all.

The release cadence, and one deadline already running

Version 25.1 is the first minor release in the v25 cycle. Under the schedule Google announced on September 4, 2025 and began in January 2026, the API ships monthly, with four major versions per year and minor versions filling the intervening months. Major versions carry a twelve-month support window; minor versions retire alongside their parent. Version 25 launched July 22, 2026, placing its expected sunset in July 2027.

The cadence has produced a dense sequence. Version 23 arrived January 28, 2026 with channel-level reporting for Performance Max. Version 24 followed on April 22. Version 24.2 landed June 24 with synthetic content labelling structures aligned to the EU AI Act's Article 50 transparency obligations, which took effect August 2, 2026.

One item already attached to the v25.1 version string predates this announcement. Google is removing the enable_local opt-out for Shopping campaigns from August 31, 2026, and on v25.1 and later, code that sets the field to false returns a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error rather than being silently ignored. Integrations on earlier versions treat the value as true without throwing. The upgrade path to v25.1 therefore carries a behavioural change that the release announcement itself does not mention, because it was published separately in July and applies at the version boundary rather than to any resource listed here.

What the release does and does not open

Read across the six features, the pattern is retrieval rather than control. Lift studies can be inspected but not created. Benchmarks can be scoped but not configured. Creator sentiment can be read. Loyalty tiers can be segmented. Conversion values can be seen before adjustment. Only parental status targeting in reach planning is an input rather than an output, and reach forecasts are hypothetical by nature.

For agencies and measurement vendors, the practical consequence is narrower than the feature count suggests. Two of the six additions sit behind an allowlist administered through account representatives, which means the release expands what is technically possible in the API well ahead of what is generally available to the developer base. Google has not published figures on how many accounts hold allowlist status for lift measurement or for ContentCreatorInsightsService.

The rest is reporting parity: metrics and dimensions that existed in the interface, or in adjacent products, arriving in the query layer where automated systems can reach them.

Timeline

Summary

Who: Google, through Anash P. Oommen of the Google Ads API Team, publishing on the Google Ads Developer Blog. The changes affect developers, agencies, bid management vendors and in-house engineering teams maintaining programmatic integrations with Google Ads, plus the measurement and creator-marketing functions that consume their output.

What: Version 25.1 of the Google Ads API, a non-breaking minor release adding six features: read-only LiftMeasurementConfig and LiftMeasurementFlight resources with 24 new Conversion Lift metrics and five brand lift dimension resources; a category_filter parameter and share_of_voice metrics in BenchmarksService; BrandSentimentInsight in ContentCreatorInsightsService; loyalty tier segmentation and a LOYALTY_MEMBERSHIP conversion value rule dimension; Metrics.original_conversion_value; and parental_statuses targeting in ReachPlanService. Lift measurement and creator insights require account allowlisting.

When: Announced Wednesday, August 19, 2026, with a live walkthrough scheduled for August 20 at 10am ET. Version 25 launched July 22, 2026, with support expected into July 2027. A separate v25.1 behavioural change on the enable_local field takes effect August 31, 2026.

Where: The Google Ads API, accessed through updated client libraries across all supported languages, with access levels governed by developer token tier and, for two features, by account-level allowlisting administered through Google account representatives.

Why: The release closes reporting gaps between the Google Ads interface and its programmatic layer, moves incrementality study metadata into a form that can be joined against other measurement data, and continues the monthly cadence Google adopted in January 2026 to shorten the interval between interface and API availability.