How Airbridge Revenue Report Calculates Cohort Revenue and Paying Users
See how Airbridge Revenue Report defines cohorts and unique users, calculates revenue, ROAS and ARPU by view, and predicts pLTV and pROAS.

Key Takeaway
- In Airbridge, the Revenue Report calculates cohort revenue from users who perform a Start Event and later a Revenue Event.
- Top-row User Count deduplicates unique users across the full date range, while sub-rows count unique users per interval.
- Top-row ROAS, ARPU, and ARPPU use weighted sub-row calculations in both Cumulative and Non-Cumulative views rather than a simple sum.
You open your billing dashboard after a weekend of running paid acquisition campaigns, and the daily subscription totals do not line up with the cohort table in front of you. When you are wearing five hats and watching every dollar of ad spend, a discrepancy between daily rows and the summary row makes it hard to know which campaign actually paid off. In Airbridge, the calculation of top-row and sub-row metrics depends on the view type, alongside how cohort boundaries and unique user counts are defined.
Cohort Revenue Scope
A cohort in the Revenue Report is defined by the Start Event you select: only users who perform that Start Event within your configured date range enter the cohort, and the report displays their revenue data. Revenue is the amount generated by those users who perform the Revenue Event after performing the Start Event during the set date range.
You are not restricted to a single entry trigger. More than one Start Event can be selected; for example, choosing both Install (App) and Deeplink Open (App) groups together users who either installed the app or opened it via a deep link.
Beyond the Start Event, a cohort is the user group analyzed in the report, and you can set conditions specifying which events users generated, how often they triggered them, and which event types apply. If you do not configure a cohort, the Revenue Report aggregates data across all users. Leaving the cohort blank is useful when you want a broad snapshot of total user activity rather than filtering for a specific behavioral segment.
Top-Row vs. Sub-Row Users
To see how many people actually converted, you can view the number of users who performed both the Start Event and the Revenue Event by selecting Paying Users as the sub-metric in the configuration box.
The top-row User Count represents the number of unique users across the entire configured date range, whereas each sub-row User Count reflects the number of unique users during that sub-row's specific time range. Because of this deduplication across the full period, each sub-row's User Count is always less than or equal to the top-row User Count. If the same user triggers your chosen Start Event on Monday and again on Wednesday, they appear once in Monday's sub-row and once in Wednesday's sub-row, but only once in the top row covering the whole week.
Subscription Revenue Metrics
Airbridge Core Plan comes with 25 preconfigured standard events in total, and among them, only Start Trial, Subscribe, and Unsubscribe are subscription events.
Average revenue metrics isolate what each cohort member or payer brings in. ARPU is the average revenue per user, calculated from the revenue generated by users who performed the Start Event during the set date range and then performed the Revenue Event. ARPPU narrows the denominator to payers: it is the average revenue per paying user based on revenue from users who performed the Start Event in the date range and performed the Revenue Event. In Cumulative view, a sub-row's ARPPU is calculated by taking the cumulative sum of revenue and dividing it by that sub-row's Total Paying Users. If you run a free trial model where only a fraction of installs convert, comparing ARPU and ARPPU shows you both the baseline value of an acquired user and the actual ticket size of a subscriber.
For broader return and forward-looking analysis, the Revenue Report includes Total ROAS, Total ARPU, and pROAS as sub-metrics. CAC is also available as a sub-metric, and it is selected automatically with pROAS when you enable pLTV. CAC requires cost integration with the ad channels where you run campaigns.
pLTV estimates the revenue a user in a cohort is expected to generate over the calculation period starting on the day they performed the Start Event. The Revenue Report predicts both pLTV and pROAS for install cohorts over a chosen period of up to 180 days, provided the granularity is Daily, Install (App) is the only Start Event, the selected date range starts at least 3 days ago, and the cohort has at least 30 users. You can enable the pLTV calculation by turning on the pLTV toggle in the Revenue Report and setting the calculation period.
Why Totals Differ
When you export a table or check the numbers by hand, the way top-row and sub-row metrics are calculated depends on the view type you have selected.
For raw revenue, the two views behave differently:
- In Non-Cumulative view, each sub-row displays the revenue amount for its set date range, and the top-row revenue is the sum of the sub-row revenue amounts.
- In Cumulative view, each sub-row shows the cumulative sum of revenue generated by users who performed the Start Event during that sub-row's set date range, while the top-row revenue is the cumulative sum of revenue from users who performed the Start Event during the set date range.
For ROAS, ARPU, and ARPPU in both views, top-row metrics apply weighting so days with higher spend or larger user volume are represented proportionally:
- In Cumulative view, a sub-row ROAS is the cumulative revenue generated divided by that sub-row's Total Cost, multiplied by 100, while the top-row value is the sum of each sub-row ROAS multiplied by that sub-row's weighted daily Total Cost.
- In Non-Cumulative view, a sub-row ROAS is the daily revenue of each range divided by the sub-row's Total Cost, multiplied by 100, and the top-row value is the sum of each sub-row ROAS multiplied by its daily Total Cost weight.
- In Cumulative view, a sub-row ARPU is cumulative revenue divided by the sub-row's Total Users, and the top-row cumulative ARPU is the sum of each sub-row ARPU multiplied by the weighted value of daily Total Users.
When your daily ad spend varies across the week, taking an unweighted average of each day's ROAS would distort your actual return. Weighting by daily cost or daily users keeps a quiet testing day from skewing the summary row for your entire campaign window.
FAQS
FAQ
When can I see pLTV and pROAS predictions for an install cohort?
The Revenue Report predicts pLTV and pROAS for install cohorts when the granularity is Daily, Install (App) is the only Start Event, the selected date range starts at least 3 days ago, and the cohort has at least 30 users, covering a chosen prediction period of up to 180 days. To view the pLTV calculation, turn on the pLTV toggle in the report and set your calculation period.
How do I make CAC show up in the Revenue Report?
CAC is a Revenue Report sub-metric that is selected automatically with pROAS when you enable pLTV. To populate it, complete cost integration with the ad channels where you run campaigns.
How much does Airbridge Core Plan cost to start running Revenue Reports?
The Core Plan, which includes the Revenue Report, starts with a 30-day free trial and then costs $40+/mo. It includes 500,000 data points per month, charges $0.0001 per additional data point, and you can cancel anytime.
Related reading
See your cohort revenue
Set up a Start Event and Revenue Event to track paying users and ROAS.


