Why it matters
Platforms report value inside short attribution windows and on conversion events you choose. Finance and growth need LTV on longer horizons with returns, churn, and margin applied. Without disciplined LTV reporting, teams argue from incompatible numbers: platform ROAS on 7-day purchase value vs finance LTV at D180 with refunds stripped out.
LTV reporting also exposes when acquisition looks efficient but cohorts decay. A campaign with low cost per acquisition (CPA) can show weak cohort LTV at maturity. That gap is the business case for sending modeled value to ad platforms before outcomes fully mature.
Reporting grain matters. User-level LTV supports activation and user-level pLTV. Cohort-level LTV supports board metrics and payback. Mixing grains in one dashboard creates false confidence.
Lifetime value (LTV) reporting
LTV reporting is the feedback loop for pLTV; pLTV is the feed-forward signal:
- First-party data in your data warehouse powers retrospective LTV and cohort LTV reports by acquisition source.
- Churney trains user-level pLTV against those realized outcomes at agreed prediction horizons (D30, D90, etc.).
- Calibration compares predicted vs realized LTV by score decile before scaling value sent directly to ad networks via Meta CAPI and the Google Ads Conversion API.
- Holdout tests validate that pLTV-shifted acquisition improves reported LTV at cohort maturity, not just platform metrics.
- LTV reporting continues post-activation to catch model drift and feedback loop effects.
Retrospective LTV reporting tells you what happened; pLTV tells the platform what to optimize for next.
Category variants
| Model | How LTV reporting shows up |
|---|---|
| Ecommerce / DTC | Cohort revenue and net margin by acquisition month; repurchase rate and refund rate curves; often D30/D90/D365 cuts. |
| Subscription app | Subscriber LTV by install or trial cohort; trial-to-paid and retention rate shape early reads before annual LTV stabilizes. |
| SaaS / PLG | Account-level ARR expansion; longer sales cycles push meaningful LTV reporting past initial activation events. |
Common mistakes
- Using platform value as LTV. Attributed purchase value is not cohort LTV with returns and churn applied.
- Skipping cohort maturity labels. Immature cohorts ranked as winners before repeat patterns stabilize.
- No link between LTV reporting and pLTV calibration. Predictions drift unchecked against realized reports.
- Attribution-only channel LTV. Organic and paid overlap inflates channel LTV without incrementality context.
Advertiser lens
| Role | What they ask | What good looks like |
|---|---|---|
| Head of Performance / UA | Which campaigns produce best LTV? | Cohort LTV by campaign with maturity flags and aligned customer definition. |
| VP Growth / CMO | Does paid acquisition pay back? | LTV:CAC and payback in the same reporting pack as platform ROAS. |
| Marketing Analytics / Data Science | Is pLTV accurate vs reported LTV? | Calibration dashboards: predicted vs realized by decile and horizon. |
| Data Engineering | Can we reproduce LTV numbers? | Documented SQL or metric definitions, single customer ID spine, refund latency noted. |
| Finance / Procurement | Which LTV number is authoritative? | One blessed definition (revenue vs margin, horizon, new vs all customers) referenced in pilots. |
FAQ
What is LTV reporting?
LTV reporting is the practice of measuring and distributing customer lifetime value metrics by cohort, channel, segment, or campaign using agreed definitions of revenue, margin, and time horizon.
How is LTV reporting different from pLTV?
LTV reporting looks backward at realized customer value over time. Predicted lifetime value (pLTV) forecasts value early (often at an anchor event) to steer live ad optimization before full LTV is observable.
What horizons should LTV reports use?
Common cuts include D30, D90, D180, and full cohort lifetime. Match horizons to sales cycle length and to the prediction horizon used in pLTV models.
Should LTV reporting use revenue or margin?
Use the definition leadership will act on. Many teams report revenue LTV for simplicity and margin LTV for payback decisions; label both clearly.
How does LTV reporting support value-based bidding?
Reported cohort LTV validates whether platform optimization on short proxies improved true long-term value. It also calibrates pLTV scores sent via Meta CAPI and the Google Ads Conversion API.
Why do cohort LTV and platform ROAS disagree?
Different windows, attribution rules, gross vs net revenue, and immature cohorts. Align definitions before comparing.
When is cohort LTV mature enough to trust?
When cohort maturity criteria are met for your category (repeat purchase patterns, refund lag, subscription renewal cycles documented).
Not the same as
| Term | Difference |
|---|---|
| pLTV | Early prediction for activation; LTV reporting is retrospective measurement. |
| Platform ROAS | Short-window attributed value ratio; not full LTV reporting. |
| Cohort-based LTV model | Modeling method; LTV reporting is the output layer for decisions. |
| Average order value (AOV) | Single-order metric; not lifetime value. |
