Google released version 25 of the Google Ads API on July 22, 2026, removing the legacy CustomerLifecycleGoal and CampaignLifecycleGoal resources and services outright, while adding duration-level breakdowns for non-skippable YouTube inventory, social engagement metrics for Shorts ads, a loyalty retention optimisation goal, and consent-gated access to creator channel analytics.

The announcement, published on the Google Ads Developer Blog by Anash P. Oommen of the Google Ads API Team, describes v25 as a major release. That designation carries weight. According to Google, developers must upgrade their client libraries and client code to use the new capabilities, and all updated client libraries and code examples have been published alongside the post.

Major releases in this API are where breaking changes live. Minor releases are additive. The distinction is not cosmetic for the agencies, bid management vendors, and in-house engineering teams that maintain production integrations against Google's advertising infrastructure, because a removed resource does not degrade gracefully. It fails.

Two resources removed, not deprecated

The most consequential line in the v25 announcement concerns the new customer acquisition goal. According to Google, the feature has been updated to reflect what the company calls the revamped unified goals schema. In the same breath, the announcement states that the legacy CustomerLifecycleGoal and CampaignLifecycleGoal resources and services are removed. Configuration now runs through the Goal and CampaignGoalConfig resources instead.

There is no transition window described in the announcement, no dual-write period, no sunset date offering a grace interval. The resources are gone in v25.

This matters because customer lifecycle goals are not a fringe feature. Google expanded customer lifecycle goals with retention and win-back bidding modes in April 2025, adding new customer acquisition modes and retention categories across campaign types. Any integration built to configure those goals programmatically since that expansion has been writing against resources that v25 no longer exposes.

The shift toward a unified schema is itself a continuation rather than a departure. Google has been consolidating fragmented, product-specific configuration layers across its advertising stack for more than a year. The Data Manager API followed the same logic, replacing per-product ingestion pipelines with a single schema enforced across Google Ads, Google Marketing Platform, and Google Analytics. Goals are now getting the same treatment.

What breaks and where

Teams that create or modify lifecycle goals through automated pipelines face a rewrite, not a version bump. The affected code paths are those that instantiate CustomerLifecycleGoal objects, call CampaignLifecycleGoalService, or reference either resource in mutate operations. Reporting queries that select fields from those resources will also fail against v25.

The remedy Google describes is a move to Goal and CampaignGoalConfig. The announcement does not detail field-level mapping between the old and new resources, directing developers instead to the official release notes for a full list of changes.

Because major versions in this API carry a twelve-month lifecycle, v25 is expected to remain supported into July 2027 under the schedule Google established when it shifted to monthly releases beginning January 2026. Under that arrangement, major versions increased from three to four per year, with minor versions arriving as non-breaking additive updates in between.

YouTube inventory gains duration-level reporting

The second substantive change in v25 concerns how YouTube inventory is measured. According to Google, advertisers can now break down YouTube instream non-skippable ads by duration - standard, max 30s, and max 60s - using a new ad_sub_format_type segment.

The segment carries a technical constraint worth noting. Google states that ad_sub_format_type must always be selected together with the ad_format_type field. It is selectable with AdGroup, AdGroupAd, Campaign, Customer, Video, and VideoEnhancement resources.

Until this release, non-skippable instream inventory reported as a single undifferentiated bucket. A fifteen-second non-skippable spot and a sixty-second non-skippable spot occupied the same reporting row despite representing materially different viewer experiences, different production costs, and, in most auction contexts, different pricing.

The absence of that split has been a persistent gap in video measurement. Reservation-based planning has recognised the distinction for years. Google added support for 30-second non-skippable in-stream ads in reservation plans targeting YouTube Select within DV360 in September 2024. The auction-side reporting layer is only now catching up.

Shorts social metrics enter campaign reports

Google is also opening video-specific social metrics to API consumers. According to the announcement, advertisers can now retrieve comments, likes, and shares for Shorts ads on YouTube, with those metrics available in reports for AdGroup, AdGroupAd, Asset, Campaign, Customer, and Video resources.

This is the second time in less than a month that Google has surfaced Shorts engagement signals to advertisers through a reporting surface. On June 29, 2026, the company added reporting columns for Shorts Ad Actions inside Video View campaigns and folded those actions into automatic budget optimisation. In that announcement, Google reported that Shorts ads generating more than ten seconds of watch time alongside a like produced, on average, 15% more brand consideration and 20% more favorability than ads without that engagement combination.

The v25 addition makes the underlying signals queryable rather than merely optimised against. Comments, likes, and shares are now retrievable at six levels of granularity, which permits creative-level analysis that was previously unavailable outside aggregate campaign views.

Whether those metrics prove diagnostically useful is a separate question. Social engagement on an advertisement is a weaker commercial signal than a conversion, and the correlation between likes on a Shorts ad and downstream purchase behaviour remains a matter Google has quantified only through its own consideration and favorability studies. The sample sizes, industry mix, and measurement windows behind those figures have not been disclosed.

Shorts inventory carries meaningful scale regardless. YouTube Shorts revenue per watch hour matched traditional in-stream video in the United States as of the third quarter of 2025, closing a monetisation gap that had defined the format since its launch. Survey research published in November 2025 found YouTube Shorts leading short-form video consumption at 56%, ahead of TikTok and Facebook at 50% each.

Loyalty retention becomes an optimisation target

The third feature in v25 introduces what Google describes as a retention goal designed to drive customer loyalty and high lifetime value. According to the announcement, campaigns can now be optimised for retaining loyalty program members, configured through either campaign-specific settings or account-level settings.

The campaign-level configuration includes bid adjustments and the option to show member benefits in Product Listing Ad format.

That second element connects the API change to a product surface Google has been building out steadily. In March 2026, Google expanded loyalty program ads to 14 countries and AI surfaces, extending member pricing and benefit displays beyond their original markets. Enforcement requiring member prices to use the loyalty_program attribute began on July 1, 2025.

What v25 adds is the bidding layer. Loyalty membership moves from being a display attribute on a product listing to an optimisation signal that Smart Bidding can act on. For retailers running membership programs, that is a structural change in how the program interacts with paid media, rather than an incremental reporting improvement.

The mechanics of customer identification remain those Google documented in April 2025: auto-detection based on purchases within a 540-day window, Customer Match lists uploaded by advertisers, and tag-based remarketing lists.

Creator analytics open to consenting channels

The final feature in v25 addresses creator data. According to Google, the API now exposes detailed YouTube channel insights - average views, likes, comments, engagement rate, and audience attributes - for creators who have consented to share non-public data.

The consent gate is the operative term. This is not a blanket opening of creator analytics but an API surface for data creators have affirmatively agreed to share.

That consent mechanism has an identifiable origin. YouTube unified BrandConnect and the Creator Partnerships Hub into a single platform in March 2026, launching across seven markets with channel insights sharing as a core discoverability feature. According to YouTube's figures cited in that announcement, creators who opt into sharing insights and appear in Google's creator search tool results see, on average, twice the click-through or interaction rate on their profiles compared to creators who do not share.

The programme has since grown. YouTube expanded Creator Partnerships to four additional countries in early July 2026, bringing the footprint to twenty-four countries per the Help Center's fuller list. YouTube's documentation states that creators remain discoverable by brands even without insights sharing enabled, but the platform recommends opting in on the grounds that it provides advertisers more holistic data about a channel.

For agencies running creator campaigns at volume, API access to consented insights changes the workflow substantially. Channel evaluation that previously required manual review of media kits or bilateral requests for analytics can now be queried programmatically across a candidate pool. That capability is only as broad as the consent base, and Google has not published figures on what proportion of creators in the twenty-four-country footprint have opted in.

Why this matters for marketing teams

The API is the layer where platform strategy becomes engineering obligation. Interface changes can be absorbed gradually. A removed resource cannot.

The removal of CustomerLifecycleGoal and CampaignLifecycleGoal follows a pattern that has recurred across Google's advertising APIs throughout 2026. In May, Google blocked new adopters of offline conversion imports through the Google Ads API from June 15, pushing that traffic toward the Data Manager API. Earlier, the company cut granular reporting data access to 37 months starting June 1, 2026, down from the eleven-year retention window established in November 2024. Each change carried its own migration burden.

The cumulative effect is a maintenance load that scales with integration complexity. Under the monthly cadence, four major versions per year each carry potential breaking changes, and each supported version expires twelve months after launch. Teams tracking three concurrent versions face a rolling migration schedule with no quiet period beyond the November and December holiday window Google excludes from its release calendar.

The v24 cycle illustrated the shape of that workload. Version 24 launched on April 22, 2026, introducing CartDataSalesView, nine lead generation conversion types, and retail filter targeting. Version 24.1 followed on May 13, adding mobile device platform segmentation, passkey field detection, and expanded experiment types. Version 24.2 arrived on June 24 with synthetic content labeling aligned to the EU AI Act, multi-party approvals, and Performance Max network segmentation. Three releases in nine weeks, each requiring evaluation even where no action followed.

There is also a directional signal in what v25 measures. Duration breakdowns for non-skippable inventory, social metrics for Shorts, engagement data for creator channels: the reporting surface is expanding toward video and creator inventory specifically, at a level of granularity that suggests Google expects buying decisions to be made on those dimensions. Advertisers who have treated YouTube as a reach channel measured in impressions and views now have the data structures to treat it otherwise.

Google is hosting a live walkthrough of the release through its Google Ads API Release Highlights event on Discord and an Ads Developers YouTube Live session on July 23 at 10am Eastern, according to the announcement. Both will be recorded and posted to YouTube. Technical support runs through the Google Ads API contact form, and discussion continues in the ads-api channel on Discord.

Timeline

Summary

Who: Google's Ads API Team, with the announcement authored by Anash P. Oommen. The release affects developers, marketing technology vendors, agencies, and in-house engineering teams maintaining programmatic integrations with Google Ads accounts worldwide.

What: Version 25 of the Google Ads API, a major release carrying five highlighted features and at least one confirmed removal. The legacy CustomerLifecycleGoal and CampaignLifecycleGoal resources and services are removed, with configuration moving to the Goal and CampaignGoalConfig resources under a revamped unified goals schema. Additions include an ad_sub_format_type segment for breaking down YouTube instream non-skippable ads by duration, social metrics covering comments, likes, and shares for Shorts ads, a loyalty retention optimisation goal with campaign-level and account-level settings, and consent-gated access to YouTube channel insights covering average views, likes, comments, engagement rate, and audience attributes.

When: The release was announced on July 22, 2026, on the Google Ads Developer Blog. A live walkthrough is scheduled for July 23, 2026, at 10am Eastern via Discord and Ads Developers YouTube Live. Under the twelve-month lifecycle established with the monthly release cadence, v25 support is expected to run into July 2027.

Where: The changes apply to the Google Ads API globally, affecting all accounts managed through programmatic integrations. Client libraries for Java, C#, PHP, Python, Ruby, and Perl have been updated alongside the release, together with code examples.

Why: Google is consolidating goal configuration into a unified schema, mirroring the consolidation already underway in first-party data ingestion through the Data Manager API. The reporting additions extend measurement granularity into video and creator inventory, providing duration-level and engagement-level data that had not previously been available through the API surface.