How this calculation works
Each stage has its own explicit assumption. Requests are reduced by the matched-request share; the resulting matches produce the entered average impression count. Applying an impression-based eCPM gives modeled revenue and an implied page RPM.
Revenue = page views × requests/page × coverage × impressions/match × eCPM / 1,000A worked example
100,000 pages × 2 requests × 80% matches × 1 impression × 50/1,000 gives 8,000 and an implied page RPM of 80.
Good to know
A transparent arithmetic model using your inputs. Example prices, rates and multiples are demonstrations, not benchmarks or offers. No tax, exchange-rate conversion, live account access or automatic attribution is supplied. Monetary display is rounded; calculations retain additional precision.
Reference: Google AdSense: request coverage (opens in a new tab) ↗
Make each stage visible
The model starts with page views, then creates an average number of requests per page. Coverage selects the requests that return ads. A separate impressions-per-match assumption translates those matches into the billable impression units used by the chosen eCPM.
Keeping these stages separate prevents a common mistake: treating page views, ad requests and impressions as interchangeable counts. A change in one stage does not automatically imply the same change in every stage.
Test scenarios without inventing measurements
A lower coverage assumption or lower eCPM reduces the revenue scenario. Change each input separately to see which assumption accounts for a difference, rather than interpreting the demonstration inputs as observed performance.
The implied page RPM is derived from modeled revenue divided by the entered page views. It is a consistency check within the scenario, not an independent measured metric that validates the other assumptions. Actual earnings, request definitions and adjustments need compatible source reports.
A few questions, answered
Why can expected counts be fractional?
Average requests per page and average impressions per match describe expected quantities across many pages, not a claim that one individual ad is fractional.
Does this create ad requests?
No. It performs arithmetic locally and does not refresh ads or contact an ad network.