If you pull Google Ads data into a warehouse, dashboard, or client-facing platform, adding fields is the easy part. The harder job is deciding which business question each field can answer without turning unlike signals into one misleading performance score.
Google Ads API v25.1 gives you several useful separations: original versus adjusted conversion value, attributed results versus incremental lift, internal performance versus category benchmarks, and total converters versus loyalty segments. Used carefully, those distinctions can make your reporting more explainable. Used carelessly, they can produce a wider dashboard that is no more trustworthy than the old one.
Key takeaways
- Store original_conversion_value beside the corresponding adjusted value. The difference shows how conversion value rules and customer lifecycle goals are changing the values used downstream.
- Treat Conversion Lift and Brand Lift as distinct measurement layers. Their API resources are read-only, and access is currently limited to allowlisted Google Ads accounts.
- Use Product & Service Category benchmarks as context for investigation, not as automatic bidding instructions.
- Keep brand sentiment separate from campaign outcomes. It can guide review and creator analysis, but it does not establish incremental impact.
- Model loyalty tier, loyalty membership conditions, and conversion value as separate fields so you can explain who converted and why a value adjustment applied.
- Although v25.1 is a drop-in upgrade for v25, you still need updated client libraries, code changes for the new capabilities, and semantic regression tests before using the data in decisions.
Build your measurement model around six different questions

The most important design choice is not which new metrics to retrieve. It is which question each capability answers. A clean measurement model keeps the following layers separate:
| Business question | v25.1 capability | Appropriate use |
|---|---|---|
| What was the conversion worth before Google applied value adjustments? | original_conversion_value | Audit the effect of value rules and lifecycle goal adjustments. |
| Did advertising create incremental conversions or awareness? | Conversion Lift and Brand Lift resources | Inspect eligible lift studies, configurations, dimensions, and results. |
| How does performance compare with a relevant market category? | BenchmarksService with Product & Service Categories | Add competitive context to internal performance analysis. |
| What sentiment is associated with a creator or brand? | ContentCreatorInsightsService sentiment data | Support creator intelligence, brand review, and reporting workflows. |
| Which loyalty groups converted, and did membership affect value? | Loyalty tier segmentation and loyalty membership dimensions | Analyze converters by tier and explain membership-based value rules. |
| How might parental-status targeting affect planned reach? | ReachPlanService targeting | Use parental status in forecasting and plannable product discovery. |
Do not collapse these capabilities into a composite campaign health score. A strong benchmark, positive sentiment, and positive lift are different observations with different scopes. Combining them can hide the exact information a decision-maker needs.
Make original conversion value an audit layer
The new original_conversion_value metric exposes the value of a biddable conversion before conversion value rules or customer lifecycle goal adjustments. That distinction matters whenever the value used for reporting and optimization is not identical to the underlying conversion value.
For each compatible reporting grain, preserve at least three concepts in your own model:
- Original value: the pre-adjustment value returned by original_conversion_value.
- Adjusted value: the corresponding value after the applicable rules or lifecycle adjustments.
- Adjustment delta: adjusted value minus original value, calculated in your reporting layer.
Report the absolute delta before reaching for a percentage. A percentage becomes undefined when the original value is zero and can look extreme when the denominator is small. If you do show a percentage, define how zero and missing values are handled instead of letting a dashboard silently convert them into zeros.
The delta is not evidence that Google changed a value incorrectly. It tells you that an adjustment occurred. Your next question is whether that adjustment matches the value rule or lifecycle policy your team intended. Where your system already stores rule metadata, expose it beside the delta so an analyst can move from detection to explanation.
Do not replace an established revenue or return-on-ad-spend metric with original_conversion_value in one step. That can change budget conclusions simply because the definition changed. Run original and adjusted value in parallel, reconcile known value-rule cases, and label both clearly before either number reaches automated budget logic.
Keep lift, benchmarks, and sentiment in their own lanes
Lift data needs its study context
Google Ads API v25.1 adds read-only resources for Conversion Lift and Brand Lift studies. You can inspect configurations, flight dates, associated campaigns, and conversion goals. The API also adds 24 Conversion Lift metrics, winner score metrics for statistical analysis, and Brand Lift dimensions covering age range, campaign, device, gender, and video.
Read-only is an important boundary. Build your integration to retrieve and explain study data, not to promise study creation or modification through these resources. Put configuration and result data in the same analytical view: a result without its flight dates, campaign scope, and conversion goal is easy to apply to the wrong period or objective.
Access is another boundary. Brand Lift and Conversion Lift API capabilities are currently limited to allowlisted accounts, and advertisers are directed to contact their Google representative for access. Check eligibility before committing a delivery date. In a multi-account platform, treat eligibility as an account-level capability rather than assuming that one successful request means every account is supported.
Your internal presentation should distinguish at least four states: supported with data, supported with no returned data, unavailable because eligibility has not been established, and failed because the request encountered an error. Those are product states you define in your application, not API status labels. Keeping them separate prevents an access limitation from being reported as a zero lift result.
Winner score metrics should retain Google’s metric names and definitions in your semantic layer. Do not relabel a winner score as probability, certainty, or incremental return unless the applicable definition supports that interpretation. The safe workflow is to display the score with its study scope, then let the measurement owner determine how it informs a campaign decision.
Category benchmarks provide context, not a target
BenchmarksService can now compare performance within specific Product & Service Categories and return aggregate cost and views alongside share-based measurements such as share of voice. The narrower category dimension can make a comparison more relevant than a broad benchmark group, but relevance still depends on whether the selected category represents the business being evaluated.
Before placing a benchmark beside an account metric, document the category, measurement window, metric definition, and any other comparability controls available in your query. If those elements differ, show the benchmark as external context rather than a direct performance gap.
A share metric and an aggregate volume metric also answer different questions. Share of voice describes relative presence, while aggregate cost and views add scale context. Show both when available. A low share in a large category may deserve a different response from the same share in a small category.
Do not let a benchmark variance trigger bid or budget changes automatically. The comparison may identify an issue worth investigating, but it does not tell you whether the right response is more spending, different creative, narrower targeting, or no change at all. Route the variance into an analyst review that also considers the account’s own goals and economics.
Brand sentiment is an intelligence signal
ContentCreatorInsightsService now supports brand sentiment distributions and summaries for creators and brands. That gives advertising platforms another signal for creator research and brand reporting, but sentiment should not be presented as conversion performance or causal campaign impact.
Use the distribution when you need to understand the mix behind a summary. A single summary can conceal whether sentiment is consistently moderate or sharply divided. The practical use is triage: identify creators or brands that warrant closer review, then examine the relevant campaign and brand context before acting.
Connect loyalty reporting to value-rule governance

Google Ads API v25.1 allows reporting metrics to be segmented by the loyalty program tier of users who converted. It also makes loyalty membership a primary dimension for conversion value rules, allowing you to identify when a loyalty membership condition was satisfied.
Those capabilities describe two related but different facts:
- Loyalty tier segmentation tells you which tier is associated with a converting user.
- Loyalty membership as a value-rule dimension tells you whether a membership condition was met when a conversion value rule was evaluated.
Do not infer the second from the first. A converter’s tier is an audience attribute; a satisfied rule condition is part of value-processing logic. Store them separately even if your first dashboard shows them together.
The most useful loyalty analysis combines tier segmentation with the original-versus-adjusted value audit. Start with these questions:
- How many conversions and how much original conversion value came from each returned tier?
- How much adjusted conversion value was reported for those same segments?
- When a loyalty membership condition was satisfied, did the resulting delta match the intended value policy?
- Are any apparent differences driven by a small number of conversions rather than a stable segment pattern?
Always report conversion volume beside value when reviewing tiers. A high average value from a small segment can dominate a ranking without providing a dependable basis for budget changes. You do not need an invented universal threshold; you need enough context for the owner of the loyalty program to judge the segment responsibly.
Parental-status targeting in ReachPlanService belongs in a different part of your model. It expands reach forecasting and plannable product discovery; it is not an observed conversion result. Keep forecast inputs and planned reach outside outcome tables so users cannot mistake a planning scenario for delivered performance.
Roll out v25.1 without changing metric meaning by accident
Google describes v25.1 as a drop-in upgrade for v25, but access to the new capabilities still requires the latest client libraries and corresponding code updates. Drop-in compatibility reduces migration friction; it does not replace testing of your transformations, labels, and downstream decisions.
- Inventory the current integration. Record the v25 services, fields, generated client types, transformation jobs, dashboards, and automated decisions that could be affected.
- Update the client library in an isolated change. Confirm that the existing extraction and build processes still work before requesting new resources or metrics.
- Regression-test existing outputs. Run representative unchanged queries through the old and upgraded paths. Compare row grain, identifiers, null handling, totals, and field mappings.
- Add one capability group at a time. Original conversion value, lift studies, benchmarks, sentiment, loyalty, and reach planning should enter separate staging models. This makes a semantic error easier to locate.
- Model access explicitly. Check allowlist eligibility for lift features and make unavailable capabilities visible to the user. Do not coerce an unavailable response into zero.
- Validate with known business logic. For accounts using conversion value rules or lifecycle goals, select known cases and verify that the original-to-adjusted relationship matches the configured intent.
- Release reporting before automation. Let analysts inspect the new fields and definitions in read-only dashboards before any benchmark, sentiment, loyalty, or value delta changes bids, budgets, or alerts.
Give every new metric a short data contract. It should name the business question, API service or resource, reporting grain, raw and derived fields, eligibility requirement, refresh process, null policy, and downstream decision. That document is what stops an accurate field from becoming a misleading KPI six months later.
If you need one place to start, add original_conversion_value as a parallel audit field and trace its path through your warehouse and reports. Then add category benchmarks and loyalty segmentation as separate analytical views. Treat lift integration as its own workstream because account eligibility and study context must be resolved first. Your next API pull should not merely contain more columns; it should make the path from underlying value to business decision easier to explain.
References




























