LTV Over CAC: How Google Ads API v25 Unlocks Dedicated “Loyalty Retention” Bidding

Google released Google Ads API v25 on July 22, 2026 as a major version with breaking schema changes. Its headline lifecycle feature is GoalType.LOYALTY_RETENTION: an account-level goal paired with campaign-level controls for loyalty-member bid adjustments, member-specific value overrides, and targeted loyalty benefits in Product Listing Ad format.

This is not a new standalone bidding strategy with an “LTV” button. It is a lifecycle-goal layer that gives compatible campaign optimization systems better instructions about which customer state matters and how much more that state should be worth. Google does not calculate a retailer’s true LTV from this schema. The advertiser still has to supply defensible membership, conversion values, high-lifetime-value segmentation, and Merchant Center loyalty benefits.

The architectural shift is nevertheless material. A pipeline that once sent a purchase as one undifferentiated conversion can now tell the bidding system that a purchase from a loyalty member carries different economic weight—and coordinate that value signal with a member-specific offer rendered in the shopping unit.

Legacy Pre-v25 Parameters vs. the Active v25 Framework

Google Ads API v25 replaces fragmented lifecycle-goal integrations with a common account-goal and campaign-override model while adding native loyalty-retention controls.

How the Unified Goals Schema Moves Smart Bidding from CAC Toward LTV

The Google Ads API v25 Loyalty Retention Goal changes the optimization input from “get another conversion” to “apply a different value and bid treatment when the converter is a loyalty member.”

CAC optimization asks a narrow question: How cheaply can the system acquire the next conversion or new customer? LTV optimization asks a wider one: How much future economic value is associated with the customer state behind this conversion? v25 does not erase CAC; it makes CAC one constraint inside a lifecycle-value model.

The advertiser can express lifecycle value in one of two ways:

• Incremental value: additional_value or additional_high_lifetime_value adds a currency-denominated uplift.
• Multiplicative value: value_multiplier or high_lifetime_value_multiplier scales the underlying conversion value.

If a standard purchase is reported at CAD 120 and CRM cohort analysis supports a 1.6× factor for a loyalty-member cohort, a multiplier can preserve product-level order-value variation while increasing the bidding weight of that member state. An absolute adjustment is more appropriate when the incremental downstream value is stable across basket sizes.

The governance rule is strict: value_adjustment and high_lifetime_value_adjustment are separate oneof containers. Within each container, absolute and multiplier representations are mutually exclusive. A serializer that sets both does not produce a blended formula.

• A non-member repeat buyer can remain on ordinary conversion value.
• A recognized loyalty member can receive bid adjustment treatment.
• A high-lifetime-value member can receive a stronger, separately governed value treatment.
• A lapsed customer still belongs to the distinct CUSTOMER_RETENTION goal.

If those customer states are collapsed in the CRM, the API cannot recover them. LTV over CAC begins in identity resolution and cohort economics, not in the mutate request. That is the same core infrastructure principle behind journey-aware bidding.

How the Unified Goals Migration Changes the API Contract

The v25 migration is a hard client rewrite because Google removed the old lifecycle resources and services instead of aliasing them.

At the account level, use GoalService.MutateGoals and populate Goal.loyalty_retention_goal_settings.value_settings. At the campaign level, use CampaignGoalConfigService.MutateCampaignGoalConfigs and link the campaign resource to the returned goal resource.

• POST https://googleads.googleapis.com/v25/customers/{customer_id}/Goals:mutate
• POST https://googleads.googleapis.com/v25/customers/{customer_id}/CampaignGoalConfigs:mutate

{
  "account_goal": {
    "resource_type": "Goal",
    "goal_settings_oneof": {
      "loyalty_retention_goal_settings": {
        "value_settings": {
          "value_adjustment_oneof": {
            "value_multiplier": 1.6
          },
          "high_lifetime_value_adjustment_oneof": {
            "high_lifetime_value_multiplier": 2.1
          }
        }
      }
    }
  },
  "campaign_override": {
    "resource_type": "CampaignGoalConfig",
    "campaign_goal_config_settings_oneof": {
      "campaign_loyalty_retention_settings": {
        "enable_bid_adjustments_for_loyalty_members": true,
        "show_targeted_loyalty_member_benefits_in_pla": true
      }
    }
  }
}

This is a structural schema example, not a copy-paste REST request: wrapper names ending in _oneof explain protobuf exclusivity and are not literal JSON fields. REST client libraries translate proto fields to lower camel case, such as loyaltyRetentionGoalSettings, valueSettings and enableBidAdjustmentsForLoyaltyMembers.

At least one loyalty-retention mode must be active. If both enable_bid_adjustments_for_loyalty_members and show_targeted_loyalty_member_benefits_in_pla are false, the API can return LOYALTY_RETENTION_GOAL_INVALID_MODE. Build explicit handling for:

• LOYALTY_RETENTION_GOAL_INVALID_MODE
• CANNOT_USE_INCOMPATIBLE_CLO_GOALS
• LOYALTY_RETENTION_GOAL_ALREADY_EXISTS
• NEW_CUSTOMER_ACQUISITION_GOAL_ALREADY_EXISTS

Do not automatically retry these as transient failures. Send them to a dead-letter queue with customer ID, campaign ID, goal resource name, field mask, sanitized payload hash, API request ID and deployment version.

Why It Matters: Driving LTV Directly inside Product Listing Ads (PLAs)

The v25 PLA control joins auction-time loyalty optimization with a member-specific merchandising surface, but only when Ads identity and Merchant Center benefit data are both ready.

CampaignGoalConfig.campaign_loyalty_retention_settings.show_targeted_loyalty_member_benefits_in_pla tells an eligible campaign to show targeted loyalty-member benefits in PLA format. The benefits themselves come from Merchant Center:

• Member pricing submitted through the product-level [loyalty_program] attribute.
• Member shipping mapped through the loyalty-program shipping configuration and, where applicable, its [shipping_label].
• Loyalty points associated with the correct program and tier labels.

For known-member personalization, Google’s Merchant Center documentation requires Customer Match. Tier names in uploaded member lists must align with Merchant Center tier labels. When a recognized member is signed in to a Google Account, eligible Shopping ads can show that member’s exclusive benefit.

For a Canadian retailer, the geography is relevant: Canada is among the supported merchant-loyalty countries, although Google says availability and shopper experience can vary by country. Member pricing in ads also has a display threshold: the member discount must be at least 5% or five units of the relevant currency versus the regular or sale price. An unconditional merchant promotion can take display precedence over member pricing.

This is why the feature is more than ad formatting. A member may see a differentiated offer while the campaign simultaneously values that member state differently. The system can align who receives the offer, what benefit is rendered, and how the auction values the expected outcome.

Technical Highlights: AI Attestation & YouTube Shorts Granularity

Google Ads API v25 turns synthetic-content declaration into a writable workflow and makes YouTube reporting materially more granular.

Synthetic content becomes an active publishing control

The exact v25 field is synthetic_content_info on Ad and Asset, not syntheticContentAttestationStatus on Creative or AdAsset.

Each SyntheticContentInfo separates advertiser_attestation from system_attestation. Each attestation contains status and source. Status uses SyntheticContentAttestationStatus, including IS_SYNTHETIC and NOT_SYNTHETIC; source uses SyntheticContentSource, including ADVERTISER_ATTESTED, GOOGLE_GENERATED_ADVERTISER_REVIEWED and GOOGLE_GENERATED_FULLY_AUTOMATED.

1. Classify the asset source before upload.
2. Require advertiser or agency approval for the declared state.
3. Write advertiser_attestation with the ad or asset mutation.
4. Query the returned system_attestation.
5. Alert when advertiser and system states diverge.

Store both states with the asset hash, generation or editing tool, prompt lineage where policy permits, reviewer, approval timestamp, market and campaign linkage. This is the production sequel to the earlier Google Ads API synthetic-content attestation analysis.

ad_sub_format_type splits non-skippable inventory by duration

segments.ad_sub_format_type adds duration-level reporting and must be selected together with segments.ad_format_type.

• INSTREAM_NON_SKIPPABLE_STANDARD
• INSTREAM_NON_SKIPPABLE_MAX30_SEC for ads no longer than 30.99 seconds
• INSTREAM_NON_SKIPPABLE_MAX60_SEC for ads no longer than 60.99 seconds

SELECT
  segments.date,
  segments.ad_format_type,
  segments.ad_sub_format_type,
  metrics.impressions,
  metrics.cost_micros,
  metrics.conversions,
  metrics.conversions_value
FROM campaign
WHERE segments.date DURING LAST_30_DAYS

The segment is selectable with AdGroup, AdGroupAd, Campaign, Customer, Video and VideoEnhancement. Add both format fields to the warehouse key or a campaign-date upsert can overwrite duration-specific rows.

Shorts receives native social-engagement metrics

The new metrics.youtube_comments, metrics.youtube_likes and metrics.youtube_shares fields expose social response to Shorts ads.

• Delivery: impressions, reach, frequency and cost.
• Response: clicks, views, comments, likes and shares.
• Business outcome: conversions, conversion value, profit, new-customer CAC, member retention and modeled LTV.

A like is not a purchase, and a share is not retained revenue. The fields improve creative diagnosis; they do not change attribution semantics.

The “Advertiser resource default branding” claim is not in v25

The official v25 schema does not add an Advertiser resource that auto-populates business names and logos across Demand Gen and YouTube responsive ads.

The relevant documented change occurred in v24, when videos and logo_images became required for DemandGenVideoResponsiveAdInfo, while videos, business_name and logo_images became required for VideoResponsiveAdInfo. In v25, the adjacent creative feature is AssetAutomationType.GENERATE_ANIMATED_IMAGES_FROM_OTHER_ASSETS for DemandGenMultiAssetAds.

Keep business-name and logo checks as hard preflight requirements. An integration that assumes silent advertiser-level defaulting can fail mutations or publish the wrong brand treatment.

Actionable Agency Blueprint: Upgrading Your MarTech Pipeline

Agencies should treat v25 as a schema, identity and measurement migration—not a client-library version bump.

1. Inventory and rewrite every lifecycle-goal dependency

• Search source, generated clients, protobuf descriptors, SQL models, dashboards, fixtures and alerts for the removed lifecycle resources, services, settings and enums.
• Replace customer-level writes with GoalService.MutateGoals.
• Replace campaign-level writes with CampaignGoalConfigService.MutateCampaignGoalConfigs.
• Refactor standalone value fields into the correct oneof; choose additive or multiplier semantics explicitly.
• Run v24.2 and v25 payloads against separate test accounts and block production until removed-field tests fail closed.

2. Build the loyalty identity and value contract before enabling bidding

• Define member, tier, high_lifetime_value, lapsed, consent_status, effective_from and effective_to in the CRM or customer data platform.
• Align Customer Match tier labels with Merchant Center program and tier labels.
• Derive value adjustments from contribution margin and retained cohort value, not gross revenue alone.
• Create the account Goal, then attach campaign-specific CampaignGoalConfig resources.
• Start with one campaign cell and a mutually exclusive holdout. Monitor member match rate, incremental conversion value, repeat purchase, margin, cannibalization and payback period.

3. Upgrade creative governance and reporting in the same release

• Add advertiser synthetic-content attestation to asset publishing and retain Google’s system attestation separately.
• Extend GAQL extraction with both format segments and all three YouTube social metrics.
• Update warehouse uniqueness keys, data contracts, null handling and dashboard definitions before the first v25 backfill.
• Validate required business-name and logo assets explicitly; do not depend on an undocumented Advertiser default.
• Deploy canary mutations, capture request IDs and route configuration errors to human review.

Generative Engine & Voice Agent FAQs

Google Ads API v25 gives retrieval systems three direct answers: what the Loyalty Retention Goal does, how PLA member benefits render, and which lifecycle resources integrations must remove.