TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is ARPDAU? Formula, examples and the DAU trap

ARPDAU is a day's revenue divided by that day's active users. The formula, ARPDAU vs ARPU and ARPPU, and a worked example of why it must always be read next to DAU.

Lin Zhou Reviewed by Sophia Bennett Also called average revenue per daily active user Last updated Nov 15, 2026 Glossary

Quick answer

ARPDAU (average revenue per daily active user) is a day's revenue divided by that day's active users. It shows the immediate effect of events and releases, but must be read with DAU: when daily actives fall, ARPDAU can rise while total revenue falls.

Formula: ARPDAU = revenue on a day ÷ daily active users (DAU) on that day; for a period: total revenue ÷ sum of daily DAU

What is ARPDAU?

ARPDAU (average revenue per daily active user) is the revenue an app or game earns in one day divided by the number of people who were active that day. Google's Play Console team describes it as "your daily revenue divided by your DAU", a measure of how well you turn users into revenue. Revenue usually includes in-app purchases, subscriptions billed that day and ad revenue; say which ones you include, because sources differ.

Because it resets every day, ARPDAU reacts quickly to a sale, a new offer or a release, which is why games and ad-funded apps watch it daily. That speed comes with a trap, and it's the point of this page: ARPDAU = today's revenue ÷ today's DAU suits judging the immediate effect of events and releases, but it must be read with DAU. When DAU falls, ARPDAU can "improve" while the business earns less.

ARPDAU formula

Daily ARPDAU = revenue on day d ÷ DAU on day d

For a period longer than a day, there are two common versions:

  • Pooled: total revenue in the period ÷ sum of daily DAU in the period. This weights busy days more.
  • Average of daily DAU: total revenue ÷ number of days ÷ average DAU. PLAYSTUDIOS, a mobile games publisher, defines ARPDAU this way in its SEC filings: game and advertising revenue for the period, divided by the number of days, divided by average DAU.

The two give the same answer (sum of DAU = days × average DAU), so pick either. What you shouldn't do is average seven daily ARPDAU values, which gives a quiet Monday the same weight as a busy Saturday.

What counts as "active" is your DAU definition: usually an app start or a screen view, not just a push notification received. Keep it the same between periods, or ARPDAU moves for reasons that have nothing to do with monetisation.

ARPDAU vs ARPU vs ARPPU

MetricFormulaDenominatorBest forWatch out for
ARPDAURevenue on a day ÷ DAU that dayEveryone active that dayDaily effect of events, offers, releasesRises when low-value users leave
ARPURevenue in a period ÷ active users in the periodEveryone active in the period, counted onceMonthly or quarterly monetisation, plan comparisonsPeriod length changes the number
ARPPURevenue in a period ÷ paying usersOnly payersSpend depth of payers, pricing testsIgnores how many people pay at all
ARPMAURevenue over 28 or 30 days ÷ MAUMonthly activesComparing with monthly targetsPlay Console uses 28-day rolling windows

ARPU's own definition and its pitfalls are covered in the ARPU entry; ARPDAU is ARPU with the period fixed at one day.

Worked example: DAU drops, ARPDAU rises

Sample data: a casual game over seven days. On day 5 a release breaks sign-in on older Android devices, and about 10,000 casual players can't get in.

DayDAURevenue ($)ARPDAU ($)
150,0006,0000.1200
250,4006,0500.1200
349,8005,9800.1201
450,2006,0200.1199
540,0005,4000.1350
640,4005,4300.1344
740,6005,4600.1345

Day 4 to day 5:

  • DAU: 40,000 ÷ 50,200 − 1 = −20.3%
  • Revenue: 5,400 ÷ 6,020 − 1 = −10.3%
  • ARPDAU: 0.1350 ÷ 0.1199 − 1 = +12.6%

Read alone, the ARPDAU line says the release improved monetisation by 12.6%. In fact the game lost $620 a day. The players who left (50,200 − 40,000 = 10,200) had been generating 6,020 − 5,400 = $620 a day, or $620 ÷ 10,200 = $0.061 each, about half the average. Removing low-spending users from the denominator lifts the average for everyone who remains.

The pooled view says the same: days 1–4 = $24,050 ÷ 200,400 = $0.1200; days 5–7 = $16,290 ÷ 121,000 = $0.1346. For the whole week, $40,340 ÷ 321,400 = $0.1255 pooled, while averaging the seven daily values gives $0.1263, a small but avoidable bias toward the low-DAU days.

The decision rule: when ARPDAU rises, check DAU and total revenue the same day. If DAU fell and revenue fell, the "improvement" is a shrinking denominator.

A real filing that moves the other way

PLAYSTUDIOS' 10-Q for the quarter ended 31 March 2023 shows the same arithmetic in reverse. Average DAU rose from 1,555 thousand to 3,565 thousand (+129%), game and advertising revenue rose from $70.0 million to $77.5 million, and reported ARPDAU fell from $0.50 to $0.24 (−52%). Recomputed: $77,470k ÷ 90 days ÷ 3,565k = $0.24; $70,010k ÷ 90 ÷ 1,555k = $0.50. A falling ARPDAU there came with more revenue, because the company added many lower-spending players. Neither direction means anything without DAU next to it.

Where ARPDAU fits

  • Free-to-play games. Daily events, limited offers and ad placements change spending within a day; ARPDAU shows the effect by the next morning.
  • Ad-funded apps. Revenue per day depends on impressions per user and ad prices, both of which move daily.
  • Subscription apps. Less useful. Renewals bill on a monthly or annual cycle, so daily revenue is lumpy; ARPU per month, trial-to-paid conversion and retention say more.
  • Comparing releases or countries. Fair only when DAU definitions, currencies and time zones match.

For which engagement numbers to put next to it, see app engagement metrics; to check the DAU side, the DAU / MAU calculator gives stickiness from your daily and monthly actives.

Common mistakes

  • Reading ARPDAU without DAU. The example above: +12.6% ARPDAU, −10.3% revenue.
  • Averaging daily ARPDAU values. Use total revenue ÷ total daily actives instead.
  • Mixing gross and net revenue. Store fees, refunds and taxes change the number. Pick one and label it.
  • Counting revenue by order date in one tool and by payment date in another. Late payments and refunds then land on different days.
  • Comparing across time zones. A day in UTC and a day in the project's time zone contain different revenue and different users.

ARPDAU in TapCub

The question behind the example is "how do I watch monetisation every day without being fooled by the denominator?" In TapCub:

  1. Read ARPU and its parts together. All-platform analytics › Business › Commerce & revenue shows revenue, buyers, paying rate and revenue per user, where revenue per user divides order revenue by active users in the period. Refunds in the same period are reported separately, not subtracted, so state that when you compare with store payouts.
  2. Define ARPDAU once. TapCub has no built-in ARPDAU metric, so in All-platform analytics › Behavior › Metrics & SQL create a formula metric: the property sum of revenue on your purchase event (PROPSUM) divided by unique active people (UNIQUES). View it by day in event analysis, next to DAU and revenue as separate lines, which is exactly the check the example needs.
  3. Watch the denominator. App analytics › Users › Users draws daily, weekly and monthly active users, so a day-5 drop in DAU is visible on its own.
  4. Get told, not surprised. All-platform analytics › Operations › Monitors can check a saved custom metric or a built-in one on a daily schedule; set one on ARPDAU and one on DAU, and mark the release date with Configuration › Annotations so the spike has a reason on the chart.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Lin Zhou

Product Experience Specialist

Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

How do you calculate ARPDAU?

Divide the revenue earned on one day by the number of users active that day. For a week or month, divide total revenue by the sum of each day's DAU, or by days times average DAU, which is the same thing. Don't average the daily ARPDAU values, because that gives quiet days the same weight as busy ones.

What is the difference between ARPDAU and ARPU?

ARPDAU fixes the period at one day and divides by that day's active users. ARPU uses a longer period, such as a month, and counts each active user once. ARPDAU reacts faster to events and releases; ARPU is steadier and better for comparing months, plans or countries over time.

What is a good ARPDAU?

It depends on genre, platform, country and whether ad revenue is included, so compare against your own history rather than a single benchmark. More useful than any target is the rule of reading it with DAU and total revenue: a higher ARPDAU with lower DAU and lower revenue is not an improvement.

Does ARPDAU include ad revenue?

It can. Many games and ad-funded apps include in-app purchases, subscriptions and ad revenue; some benchmark sources count only purchase revenue. PLAYSTUDIOS, for example, uses game and advertising revenue in its filings. Say which revenue you include and keep it the same over time so comparisons stay fair.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics