How Much Data Does Predictive LTV Need for App Cohorts?

You launched a new paid campaign on Tuesday, spent budget across ad channels by Friday, and now have to decide whether to scale that budget or cut it before another week of cash disappears. Waiting three months for subscription renewals to trickle in means flying blind while your ad spend is actively burning. Yet looking at a predictive model too early—or with a tiny handful of installs—leaves you second-guessing whether the numbers on your screen mean anything at all. In the Revenue Report, Airbridge Predictive LTV requires each cohort to have at least 30 users and a date range starting a minimum of 3 days before today just to turn on. Knowing the exact line between basic feature enablement and recommended calculation accuracy lets you read early cohort signals without misinterpreting raw noise.

Cohort Data Thresholds

Turning on Predictive LTV (pLTV) in your reporting and getting a sharper calculation rely on two different date-range windows alongside a hard cohort size floor. When you open the Revenue Report to evaluate a young campaign, your cohort data has to clear specific historical depth and user volume thresholds.

Setting the Revenue Report date range to start at least 13 days before today is recommended for a more accurate calculation.

Revenue Report Setup

Enabling pLTV in the Revenue Report requires the following settings:

• Set the date-range granularity to Daily in your Revenue Report view.
• Select Install (App) as the Start Event so every cohort anchors to app installation.
• Define a calculation period so the report knows how far out to project.
• Keep that calculation period within the supported 1 to 180 days range.
• Collect the event value for whatever event you designate as the Revenue Event in the Revenue Report.

If you normally review weekly cohort rollups or use a post-install sign-up event as your cohort anchor, switching back to daily granularity and the app install start event is required whenever you want to check pLTV.

Early Campaign Planning

Once the metric is active in your report, pLTV shows the estimated revenue a cohort user is expected to generate across your chosen calculation period, starting on the exact day the Start Event occurred. Instead of waiting months for every renewal cycle to finish, you can use Subscription Attribution to compare average revenue per user across eligible install cohorts with Predictive LTV for a forecast window up to 180 days, informing your budget decisions while those cohorts are still young.

When you are wearing five hats and managing paid acquisition yourself, the hardest part of weekly budget reviews is knowing whether a higher-cost channel is bringing in users who will actually pay over time. Comparing pLTV directly against Customer Acquisition Cost (CAC) in your cohort analysis bridges that gap by placing predicted cohort revenue next to what you paid to acquire those users, helping you plan future campaigns. You can build and optimize campaigns around users' future potential to drive revenue.

If you prefer looking at return on spend as a ratio, pROAS expresses the predicted total revenue from users who performed the Start Event during your selected date range as a percentage of total ad spend. Both metrics are included in the Core Plan, and pROAS also requires ad spend data for the cohorts you compare. You can start with a 30-day free trial, followed by $40+/mo including 500,000 data points per month ($0.0001 per additional data point), with no annual lock-in and cancellation anytime.

Reference vs. Actual Profit

In the Revenue Report, pLTV does not correspond to actual net profit and must be used strictly as a reference rather than booked revenue data. Even in cohorts where pLTV sits higher than your CAC, your actual net profit can end up lower than CAC.

Because predictive metrics—including predictive lifetime and pLTV—rely on historical data to guide future campaign planning, the estimates may differ from the actual numbers a cohort eventually records. Use pLTV and CAC comparisons to help with future campaign planning, while treating pLTV strictly as a reference rather than actual revenue data.