App Revenue Calculator

Use this calculator to estimate app revenue calculator from your own assumptions. The calculation runs locally in your browser, and the formula, example, scope, and source are visible below.

How to use this calculator

• Mode A — actual impressions:: enter the value for the same scenario and period as the other inputs.
• Ad impressions for period: enter the value for the same scenario and period as the other inputs.
• Realized eCPM: enter the value for the same scenario and period as the other inputs.
• Mode B — traffic estimate:: enter the value for the same scenario and period as the other inputs.
• Daily active users: enter the value for the same scenario and period as the other inputs.
• Ad requests/opportunities per user/day: enter the value for the same scenario and period as the other inputs.
• Match rate %: enter the value for the same scenario and period as the other inputs.
• Render/show rate % (editable; optional, default 100%): enter the value for the same scenario and period as the other inputs.
• Days in period: enter the value for the same scenario and period as the other inputs.
• Realized/assumed eCPM: enter the value for the same scenario and period as the other inputs.
• Optional subscription and IAP revenue: enter the value for the same scenario and period as the other inputs.

1. Replace the example values with values from one consistent scenario.
2. Select Calculate and review the primary and supporting results.
3. Change one assumption at a time when comparing scenarios, then verify material decisions against the governing source or a qualified professional.

Formula and method

If actual impressions supplied:
  ad_impressions = actual_impressions
Else:
  ad_requests = DAU * requests_per_user_per_day * days
  matched_requests = ad_requests * match_rate
  ad_impressions = matched_requests * render_rate
ad_revenue = ad_impressions / 1000 * eCPM
total_revenue = ad_revenue + subscription_revenue + IAP_revenue
AdMob defines eCPM = estimated earnings / impressions * 1000; match rate = matched requests / requests.

The implementation uses the audited A17 — Creator / Audience Pricing method. Intermediate values retain calculation precision; the interface formats values only for display unless the formula itself specifies a rounding rule.

Worked example

Inputs: Traffic mode: DAU=10,000; 4 ad requests/user/day; Match rate=90%; Render rate=95%; eCPM=$5; 30 days

Result: Ad requests=1,200,000; Matched requests=1,080,000; Estimated impressions=1,026,000; Ad revenue=$5,130.00

This is the baseline audited scenario used to check that the page, formula, and displayed result remain aligned.

How to interpret the result

The calculator reports Ad requests; matched requests; impressions; ad revenue; total revenue; optional ads ARPU. Treat the output as a scenario estimate: it changes when the entered scope, time period, fee basis, or cost definition changes. It does not establish a universal benchmark or guarantee a business outcome.

Assumptions and limitations

• Corrected from a generic ‘fill rate’ shortcut. Actual-impressions mode is preferred.

• traffic mode is explicitly an estimate.

• Results are informational planning estimates, not accounting, tax, legal, employment, valuation, or investment advice.

• Values are processed in the browser and are not submitted to an application server.

Common mistakes

• Use actual impressions when available.

• match rate is not the same as rendered-impression rate.

• eCPM varies by geography/format/time.

• Corrected from a generic ‘fill rate’ shortcut. Actual-impressions mode is preferred.

• traffic mode is explicitly an estimate.

• Rounding intermediate values before completing the formula can change the final result.

• A worked example is not a default recommendation; replace every assumption that does not match your case.

Frequently asked questions

How this calculator was created and tested

• Formula basis: the public formula is generated from the audited implementation specification for this calculator, not inferred from a search snippet or an AI answer.
• Validation coverage: 2 of 2 release test vectors are marked Audited for this calculator. The suite covers a normal scenario plus boundary or invalid-input behavior where defined.
• Regression behavior: build checks compare expected outputs, validation states, route integrity, structured data, internal links, and release blockers before publication.
• Automation and AI: automation or AI may assist drafting, organization, and regression work, but it is not treated as an authoritative source and does not override the audited formula, official rate registry, or release blockers.
• Editorial responsibility: MIASIN S.R.O. controls publication, source policy, corrections, and release decisions. No named individual expert review is claimed unless a page explicitly identifies one.

Read the full Methodology, Editorial Standards, and Corrections Policy.

Sources and freshness

Sources are ordered by authority: government or official sources first, then first-party platform sources, educational references, and finally supporting industry references.

• First-party / platform source: Google Ads Help

Last reviewed: September 22, 2026
Source set reviewed: September 22, 2026
Next scheduled review: September 22, 2027
Review cadence: Annual or when metric definitions change