ARPDAU

What ARPDAU measures

Average revenue per daily active user divides a day's revenue by that day's active users:

ARPDAU = Daily revenue ÷ Daily active users (DAU)

An app earning $4,200 from 60,000 DAU runs a $0.07 ARPDAU. The metric's power is its completeness: it absorbs all monetization — ad revenue across every format and network, in-app purchases, subscriptions — and normalizes by audience, so it stays comparable as the app grows or shrinks.

This is what makes ARPDAU the operating truth metric of app monetization, sitting above the diagnostics. eCPM tells you what impressions earn; fill rate tells you what fraction of requests deliver; ARPDAU tells you what a user-day is actually worth. Monetization changes that look brilliant at the impression level — more aggressive interstitials, tighter floors — face their audit at the ARPDAU level, where session length, ad frequency, and payer behavior all net out.

The decomposition for ad revenue makes the chain explicit:

Ad ARPDAU = Impressions per DAU × eCPM ÷ 1,000

Impressions per DAU itself splits into sessions per user × ad exposure per session — which is where monetization design meets product design.

Using ARPDAU without fooling yourself

Segment it. Blended ARPDAU mixes payers with non-payers, tier-one with emerging markets, day-1 users with veterans. The decision-relevant views:

• By revenue stream. Ad ARPDAU versus IAP ARPDAU evolve differently and respond to different levers; a hybrid app managing them as one number will misattribute every change.
• By geography. Same structural gaps as eCPM — comparing a US-heavy week against a campaign-driven emerging-market week tells you about traffic mix, not monetization skill.
• By cohort age. New users monetize differently from retained veterans. A UA burst floods DAU with low-monetizing day-1 users and mechanically depresses ARPDAU with no real deterioration anywhere.

Pair it with retention. ARPDAU is a per-day rate; it says nothing about how many days a user stays. The product ARPDAU × retained days is what accumulates into LTV — and the classic monetization failure is trading retention for daily rate. An interstitial-frequency increase that lifts ARPDAU 10% while shaving retention pays out negative within weeks; only cohort-level revenue curves reveal it.

Mind the DAU definition. Counting rules (timezone boundaries, what counts as "active", platform splits) change the denominator; keep them constant and documented, especially across analytics migrations.

Improving ARPDAU in practice

1. Find the binding constraint first. Decompose: is ad ARPDAU limited by impressions per user (exposure design) or by eCPM (demand and signal)? Is IAP ARPDAU limited by payer conversion or by payer depth? Different constraints, different work.
2. Grow exposure through engagement, not density. More sessions and longer sessions raise impressions per DAU without raising per-session ad pressure. Rewarded video is the canonical positive-sum lever — opt-in exposure that often improves session metrics.
3. Strengthen the auction. Mediation competition, in-app bidding, and latency fixes raise eCPM at constant exposure — pure ARPDAU gain with no UX cost.
4. Run monetization changes as retention-instrumented experiments. Measure treatment-versus-control on ARPDAU and D7/D30 retention and cohort revenue. Tools like Firebase A/B testing make the harness cheap; skipping it makes every win provisional.
5. Watch segment mix when judging trends. Before declaring a monetization regression, check whether geography, platform, or cohort-age composition moved. Most ARPDAU "drops" after UA pushes are mix effects.

Common mistakes

• Increasing short-term revenue while damaging retention. The signature failure: daily rate up, cohort value down. Any ARPDAU win not validated against retention curves is unproven.
• Mixing payer and ad revenue without context. A whale's purchase day distorts blended ARPDAU; ad-side decisions made on IAP-noisy numbers chase ghosts. Separate the streams.
• Comparing different audience markets. ARPDAU differences across geos are mostly demographics and demand, not performance. Compare like segments over time instead.
• Judging ARPDAU during a UA burst. Cohort-age mix shifts mechanically depress the blend; evaluate new-user monetization on new-user cohorts, not on the sitewide average.
• Optimizing the rate while the base erodes. Revenue = ARPDAU × DAU. Aggressive monetization that lifts the rate and shrinks DAU through churn is self-cannibalizing — the same trap as eCPM-versus-fill, one level up.

FAQ

What's a good ARPDAU? Spans run from under a cent (hypercasual, ad-only, broad geos) to dollars (hybrid-monetization games with strong payer bases in tier-one markets). Cross-app benchmarks mostly encode genre, monetization model, and geography. The operative comparison is your own ARPDAU by segment, trended over time at constant mix.

ARPDAU or ARPU — what's the difference? ARPDAU uses daily actives as the denominator and a day as the window; ARPU is typically monthly (revenue ÷ MAU) or lifetime-ish depending on convention. ARPDAU is the operational dial; monthly ARPU smooths it for planning. State the window — unlabeled "ARPU" causes more confusion than any other monetization term.

How does ARPDAU connect to LTV? LTV is the integral of ARPDAU over a user's retained days: ARPDAU × expected active days within the horizon (refined per cohort). That identity is also the warning: raising ARPDAU at retention's expense can lower LTV while every daily dashboard looks better.

Why did ARPDAU drop after my UA campaign? A flood of new users shifts cohort mix toward day-1 users, who monetize least. Mechanical, expected, usually temporary. Check the same-cohort-age comparison before suspecting monetization, and judge the campaign on its cohorts' CPI-to-LTV ratio, not its effect on the blended rate.

Should hybrid apps track ad and IAP ARPDAU separately? Always — plus the blend. The streams respond to different levers, interact (heavy ad pressure can suppress purchases; rewarded placements can boost them), and the interaction is only visible when both are tracked per segment. The app monetization path covers the full measurement hierarchy.