CLV is computed automatically on first access and cached. Batch recomputation can be triggered via the API or scheduled as a cron job.
Business Value
| Use Case | How CLV Helps |
|---|---|
| Retention targeting | Identify at_risk customers before they churn and route them into retention flows |
| Budget allocation | Invest more in high-CLV segments, optimize spend on low-CLV segments |
| Offer prioritization | Use CLV as an input to the PRIE arbitration formula’s value dimension |
| Executive reporting | Track CLV distribution across your customer base over time |
How It Works
RFM Model
CLV is derived from three behavioral dimensions:| Dimension | What It Measures | Weight |
|---|---|---|
| Recency | Days since last interaction (lower is better) | 35% |
| Frequency | Total number of interactions (impressions) | 35% |
| Monetary | Total conversion value in currency | 30% |
CLV Score Calculation
Segment Assignment
| Segment | Criteria |
|---|---|
high | CLV score >= 75th percentile |
medium | CLV score >= 25th percentile |
low | CLV score < 25th percentile |
at_risk | 30+ days since last contact AND has prior interactions |
The
at_risk segment takes priority over score-based segments. A customer with a high CLV score who has gone inactive for 30+ days will be flagged as at_risk rather than high.Churn Probability
Churn probability uses a sigmoid curve based on recency:- 0 days inactive: ~7% churn probability
- 30 days inactive: 50% churn probability
- 90+ days inactive: approaches 100%
Predicted Revenue
Predicted revenue extrapolates from the customer’s monthly average spend over a 24-month projected lifespan:Configuration
CLV computation requires no configuration. It automatically uses interaction summaries that the platform collects through the Respond API. To tune the model, you can adjust weights and thresholds through the platform settings:| Setting | Default | Description |
|---|---|---|
| Recency weight | 0.35 | Weight of recency dimension in CLV score |
| Frequency weight | 0.35 | Weight of frequency dimension |
| Monetary weight | 0.30 | Weight of monetary dimension |
| At-risk threshold | 30 days | Days of inactivity before flagging at-risk |
| Lifespan projection | 24 months | Months used for revenue projection |
Using CLV
Single Customer Lookup
Force Recompute
Batch Compute
Recompute CLV for all customers (or a specific segment):Example Response
CLV in Decision Flows
CLV scores are available as customer context in Decision Flows. You can use them in:- Qualification rules with
propensity_thresholdtype to restrict offers to high-value customers - Computed fields using
customer.clv_scorein formulas - Arbitration profiles where CLV feeds the value dimension of the PRIE score
API Reference
See the full CLV API Reference for all endpoints, request/response schemas, and error codes.Next Steps
CLV API Reference
Full endpoint documentation with examples.
Behavioral Metrics
Define custom metrics that feed into CLV and decisioning.
Decision Flows
Use CLV scores to personalize the decision pipeline.
Unified Profile
View CLV alongside all other customer data in one call.