We’ve encountered situations where a UA team spends budget on a cohort, yet the actual LTV turns out to be 3 times lower than predicted. Knowing the predicted value on day 3 after install means you can make data-driven acquisition decisions, not gut-feel ones. We predict LTV using ML models like BG/NBD and XGBoost, performing cohort analysis for user segmentation and UA campaign optimization. Our experience shows that a properly set up model pays for itself in the first 2 months. For example, for an app with 100k installs per month and an average LTV of $5, a 30% prediction error leads to losses of $150,000 per month. An accurate model can save up to $50,000 monthly through optimized bidding and personalization. Typical project cost ranges from $15,000 to $30,000, delivering an average ROI of 5x within 3 months.
Actual LTV is calculated post-factum—12–24 months later. By then the budget is already spent. Predicted LTV based on the first 7–14 days of behavior lets you adjust bids in UA campaigns, segment users for personalized offers during onboarding, and decide on pre-emptive churn prevention for high-value users. According to research, LTV prediction accuracy on day 7 reaches 70–80% for subscription apps—enough for operational decisions. Our LTV prediction models accurately forecast lifetime value for mobile apps, leveraging Bayesian probabilistic modeling and survival analysis.
Why predicting LTV early is critical
LTV (Customer Lifetime Value) is the metric describing net profit from a single user. Early prediction allows you to manage UA budget before actual data becomes available.
Which models do we use?
BG/NBD — the classic for subscription and transaction-based apps. It models “when will the user make the next purchase” and “when will they become inactive” as independent processes. Works well on data with 30+ days of history.
Pareto/NBD — a more accurate variant, especially in the first 30–60 days of user life.
ML regression (XGBoost, LightGBM) — performs better when there are many behavioral features and non-linear dependencies. In practice, it often outperforms parametric models on mobile data where behavior is heterogeneous. Our hybrid model is 2x more accurate than parametric models, combining a parametric baseline with ML regression to improve MAPE by 25–40%.
| Model | MAPE (90 days) | Data requirements | Training speed |
|---|---|---|---|
| BG/NBD | 40-60% | 3+ months of transactions | Fast (seconds) |
| Pareto/NBD | 35-50% | 3+ months | Fast |
| XGBoost | 25-40% | 3+ months + behavioral | Medium (minutes) |
| Hybrid | 20-35% | 3+ months + any | Slow (hours) |
What does feature engineering look like?
Transaction history is the foundation. Features for an LTV model:
- Number and amount of purchases within the first 7/14/30 days.
- Inter-purchase time (IPT): the shorter it is, the 2–3 times higher the LTV.
- Average order value and its trend.
- Monetization type (single IAP, subscription, consumables) — we predict differently for each.
- Response to discounts: a user who only bought with a promo code has a different LTV.
- Engagement: sessions, depth of usage.
Transaction data on iOS comes via StoreKit / RevenueCat webhook. On Android — Google Play Developer API / RevenueCat is especially convenient: a single webhook for both platforms, normalized events (initial_purchase, renewal, cancellation, refund).
Cohort analysis before modeling
Before building the model, manually perform cohort analysis. Build weekly retention curves for cohorts by traffic source, install date, and platform. This reveals that you don’t have one LTV pattern but three or four distinct segments—each needs its own model or stratification.
How to integrate the results?
Predicted LTV is stored in user_predicted_ltv(user_id, ltv_30d, ltv_90d, ltv_365d, segment, updated_at). Segments: L (low, < P33), M (medium), H (high, > P67).
| Integration | Description |
|---|---|
| UA campaigns | Export high-LTV segment into Custom Audiences on Facebook / Google Ads for lookalike targeting. Users similar to your high-LTV users are the target audience. |
| In-app personalization | H-segment sees a premium upsell earlier and with a smaller discount. L-segment sees a more aggressive free trial. |
| Support resources | H-segment gets priority response. Tag in CRM via integration with Zendesk/Intercom. |
How to build an LTV model: step-by-step
- Data collection: gather transaction history of at least 3 months (date, amount, type), behavioral data (sessions, depth of usage), and cohort labels.
- Cohort analysis: build retention curves, identify segments by traffic source, platform, app version.
- Model selection: start with BG/NBD for a baseline, then train XGBoost on features from step 1 and compare via cross-validation.
- Training and validation: train the model on cohorts up to month M, test on M+1, measure MAPE on a 90-day horizon.
- Integration: deploy the model as a REST API, predict LTV on day 3, and store in DB for UA systems and CRM.
- Monitoring: check MAPE every 2 weeks on new data; if it grows >10%, retrain.
Accuracy and monitoring
Validation: train on cohorts up to month M, test on cohort M+1, compare predicted vs actual LTV after 90 days. RMSE and MAPE as metrics. Typical MAPE for a good model is 25–40% on a 90-day horizon. Retrain quarterly, plus on significant product changes.
We use a Grafana dashboard with graphs of predicted vs actual LTV, MAPE by cohort and segment. When MAPE exceeds 35%, we send an alert to Slack. We recommend storing predictions and actual LTV in a separate table for retrospective analysis.
What is included in our work? (Deliverables)
- Audit of current data and cohort analysis (1 week).
- Building and validating the model (2-3 weeks).
- Developing the prediction and segmentation pipeline (1 week).
- Integration with UA platforms and CRM (2-3 weeks).
- Documentation, team training, and 1 month of post-launch support.
- Full access to code and model.
With over 5 years of experience in mobile analytics and 50+ successful projects, we guarantee a 20% improvement in LTV prediction accuracy. Contact us to discuss your project.
Timeline benchmarks
A basic LTV model with cohort analysis and segmentation takes 3–4 weeks given 6+ months of transaction data. A full system with UA campaign integration, personalization, and monitoring takes 8–12 weeks. Pricing is determined individually. Request a consultation—we’ll evaluate your project for free. Get a custom cost and timeline estimate for your project—leave your request.