> Site index: https://usehardal.com/llms.txt
> Every content route also serves markdown at <url>.md

# What Are ARPU, ARPDAU, and ARPPU?

ARPU, ARPDAU, and ARPPU divide revenue by users, daily active users, or paying users. Each ratio needs a stated revenue definition, audience, and time window.

Source: https://usehardal.com/glossary/arpu-arpdau-arppu

---

ARPU, ARPDAU, and ARPPU are average-revenue ratios. They compress a period of revenue and a count of people into one number. The abbreviations are easy to swap, and the swap changes the story, because each one divides by a different group.

They are descriptive. They do not say which campaign caused the revenue.

## How do you calculate each one?

Write the numerator and the denominator before you publish the ratio.

- **ARPU (average revenue per user).** Revenue in the period divided by users in the period. "Users" might mean installs, accounts, or monthly active users. Pick one and keep it.
- **ARPDAU (average revenue per daily active user).** That day's revenue divided by that day's [daily active users](https://usehardal.com/glossary#dau). The activity rule for DAU (an app open, a session, a level start) has to be the same one used everywhere else you quote DAU.
- **ARPPU (average revenue per paying user).** Revenue divided by users who paid in the period. People who spent nothing are not in the denominator. ARPPU is therefore higher than ARPU whenever some users do not pay, which is the usual case.

The revenue sum has to name its parts: validated store purchases, subscription renewals, impression-level ad revenue, refunds. A purchase counted before [receipt validation](https://usehardal.com/glossary/receipt-validation) can include transactions the store did not charge. Ad revenue counted from both `ESTIMATED` and `PRECISE` rows needs a label. See [impression-level ad revenue](https://usehardal.com/glossary/ad-revenue-ilrd).

## A concrete example

Use field names, not a target.

For one calendar day in one currency:

- Sum `purchase.value` where `value_type` is `observed` and the store state is purchased. Subtract `refund.value` with the same `transaction_id` set.
- Optionally add `ad_impression.value` where `precision` is `PRECISE` or where you have explicitly chosen to include `ESTIMATED`.
- Count distinct `user_id` with a `session_start` that day. That count is DAU for this report.
- Count distinct `user_id` with a `purchase` that day. That count is paying users.

ARPDAU is the revenue sum divided by the DAU count. ARPPU is the purchase sum (usually without ad revenue, unless you document otherwise) divided by the paying-user count. ARPU for the month uses the month's revenue and the month's user definition, which is not the sum of daily DAU.

If `purchase.value` is still in micros, or ad revenue is in micros while purchases are in currency units, the ratio is wrong by orders of magnitude. Convert units before you divide.

No sample dollar figure belongs in the definition. Two products with the same ARPU can have completely different paying rates.

## What are the limits?

Averages hide the skew. A few high spenders raise ARPU and ARPPU while most users contribute nothing. Pair the ratio with the share of users who paid, or with a median, when the decision depends on how typical the average is.

Time zones and late events move DAU and revenue across dates. A refund recorded next month lowers this month only if your rule says so. Say which rule you use.

Currency mix needs a conversion or a split by `currency`. An unweighted sum of USD and EUR values is not a revenue total.

These ratios do not attribute credit to ads. Cost per install and predicted value answer different questions. See [cost per install](https://usehardal.com/glossary/cost-per-install) and [predicted lifetime value](https://usehardal.com/glossary/pltv).

## How Hardal handles it

Hardal does not define a single ARPU for you. It stores the revenue and user events you send, including purchases, refunds, and ad impressions, so a report can divide a documented numerator by a documented denominator. [Data Hub](https://usehardal.com/glossary/data-hub) is the workspace for building that dataset from the events you already collect.

If the events are missing or duplicated, the ratio will be too. Validate store purchases first, deduplicate `transaction_id`, and keep estimated ad revenue out of a settled-revenue ARPU unless the label says it is included. [Hardal for Gaming](https://usehardal.com/solutions/gaming) is the mobile context where these ratios usually sit next to install cost.

**Related terms:** [Session](https://usehardal.com/glossary/session), [Events](https://usehardal.com/glossary/events), [Predicted lifetime value](https://usehardal.com/glossary/pltv), [Cost per install](https://usehardal.com/glossary/cost-per-install)
