Charts
Cohorts: No.
MRR is recurring proceeds revenue normalized in to a monthly amount. It's calculated as a sum of the monthly fee paid by each paying customer with a deduction of Apple comission.
For example, If you have 10 customers paying $10 per month. MRR will be equal to:
MRR = 10 subscribers × $10 per month - 30%(or 15%) Apple Comission = $70.
All non-monthly subscription plans are being normalized in to a monthly plan. For example, annual subscription that costs $120 per year will be normalized in to $10 per month.
Cohorts: No.
Gross revenue is a total amount billed to customers for purchasing subscriptions prior to refunds, taxes and Apple’s commission.
Cohorts: No.
Total amount billed to customers for purchasing in-app purchases. Sales = Gross Revenue - Refunds.
Cohorts: No.
Estimated amount you receive on sales of in-app purchases prior to VAT taxes. Proceeds = Sales - Apple’s Comission.
Please note, that we are not apply VAT taxes to Proceeds (but Apple does).
Cohorts: No.
Amount of in-app purchases refunds within selected period.
Cohorts: Yes.
APRU is Average Revenue Per User.
Calculated on a cohort basis. The cohort is users, that have installed the app within the selected period. They can be segmented and filtered by country, products, marketing campaigns (depending on what was selected in segments and filters).
We calculate ARPU for the users’ lifetime. This means that ARPU for the given cohort will be calculated by dividing the summarized users' revenue by the total number of users who have installed the app within the selected time frame.
Why ARPU is important?
One of the main goals of any mobile business is to maximize revenue. ARPU is one of two critical values for calculating your ROI along with CPI (cost per install).
Knowing the ARPU of different groups of users will let you optimize your marketing efforts and focus on high-performing user acquisition campaigns. ARPU-driven measurement help to point out which media sources could bring the top paying users and which are under-performing and should be stopped.
Understanding who is your high LTV users can help to find more like them through lookalike campaigns and leads you to boost total app revenue.
Cohorts: Yes.
ARPPU is Average Revenue Per Paying User.
It's pretty much the same as ARPU, except there are only paying users counted within the selected time period.
ARPPU will be usually much higher than ARPU because only paying users included in cohorts (a smaller part of all users in the app).
Cohorts: No.
This metric shows how many subscriptions were lost during the selected period.
Subscriptions Churn = (Number of subscriptions expired during the period) / (Number of paid subscriptions at the start of the period) * 100%
Churn also can be negative. This may happen if your app allows customers to have more than one subscription at the same time and the user adds a purchase to existing ones. It's called "expansion". Negative churn is a signal that your app has a strong value to your customers.
Coming very soon!
Cohorts: No.
This metric shows how much revenue was lost during the selected period.
Churned revenue = (MRR Lost to Downgrades + MRR expirations in the period) / (MRR at the start of period) * 100%
Churned revenue especially helpful to ensure that you're not losing the most valuable customers (subscriptions churn can be relatively low while churned revenue is high).
Like subscriptions churn, revenue churn also can be negative if users upgrade subscriptions or subscribe more within your app. And, of course, it's a good signal too.
Cohorts: No.
Yes, these are just new users of the app. By the way, you can filter them, using custom User Properties (if you send any).
Pay attention that new users counted when they were recorded by Apphud SDK (not actual install date). In 99% of cases, these dates are nearly identical.
All charts in this group represented as funnels with particular steps (based on events).
New users are calculated as cohorts. It means that users are "grouped" by the initial event date (i.e. users, who have installed the app on a particular date).
For example, if we have a row with a date of Jan, 28, then trial conversions are summarised by users who had installed the app on Jan, 28 and then converted to regular subscribers any day after install and trial start (not only on Jan, 28).
Cohorts: Yes.
New users, who started a trial and then converted to regular subscribers. Users who converted without a trial period are not counted.
Cohorts: Yes.
New users, who converted to regular subscribers whether with a trial or not.
Cohorts: Yes.
New users, who started a paid intro offer and then converted to regular subscribers.
Cohorts: Yes.
New users, who started a promo offer and then converted to regular subscribers.
You can segment conversion charts by the second additional parameter to get more meaningful results.
For example, you have 100 new users, 10 of them started a trial and 2 were converted to a subscription.
% of total
Shows drop-off in each funnel step calculated as a percent of total (first step) count.
In this case, the total count (new users) will be 100%, the trial started – 10%, and converted – 2%.
% of previous
Shows drop-off in each funnel step calculated as a percent of the previous step.
New users will be 100%, the trial started – 10% and converted – 20% (because started trials are considered as 100% in this case).
User count
Shows absolute users count in each step.
Cohorts: No.
Analyze events related to trials:
Trial started
Trial expired
Trial converted
Trial cancelled
Cohorts: No.
Analyze cancellations and refunds events:
Subscription cancelled
Trial cancelled
Intro refunded
Promo refunded
Non renewing purchase refunded
Cohorts: No.
Analyze regular subscriptions:
Subscription started
Subscription renewed
Subscription cancelled
Subscription expired
Cohorts: No.
Analyze paid intro subscriptions:
Intro started
Intro renewed
Intro converted
Intro expired
Intro refunded
Cohorts: No.
Analyze promo offer subscriptions:
Promo started
Promo renewed
Promo converted
Promo expired
Promo refunded
Cohorts: No.
Analyze other events:
Autorenew enabled
Billing issue
Non renewing purchase
Non renewing purchase refunded
