The denominator explains the difference
Page RPM describes estimated earnings per thousand page views. Ad RPM describes estimated earnings per thousand ad impressions. Google’s AdSense documentation uses these different denominators. A page can produce a different number of ad impressions from its page-view count, so the two rates cannot be substituted without changing the model.
Use the AdSense RPM Calculator to make the unit explicit. A number labelled only “RPM” is incomplete for a forecast: first establish what is counted, which earnings are included and which period the report covers.
Reconcile one set of totals
Take an original hypothetical report with 96 estimated earnings, 24,000 page views and 48,000 ad impressions. Page RPM is 96 ÷ 24,000 × 1,000 = 4. Ad RPM is 96 ÷ 48,000 × 1,000 = 2. Both describe the same earnings. Neither figure is wrong, and the larger page RPM does not mean that the ads became more valuable.
| Measure | Calculation | Result |
|---|---|---|
| Page RPM | 96 ÷ 24,000 × 1,000 | 4 per thousand page views |
| Ad RPM | 96 ÷ 48,000 × 1,000 | 2 per thousand ad impressions |
| Average impressions per page view | 48,000 ÷ 24,000 | 2 |
In that dataset, multiplying ad RPM by average ad impressions per page view gives page RPM: 2 × 2 = 4. This identity assumes the same earnings scope and reporting period. It is not a promise that every page displays two ads.
Forecast using the matching input
With a hypothetical page RPM of 4, 40,000 page views imply 160 estimated earnings. With an ad RPM of 2, the same result requires 80,000 ad impressions. Applying the ad RPM directly to 40,000 page views would instead give 80, because the denominator changed.
The Revenue Calculator and Ad Impressions Calculator serve these connected but distinct jobs. Do not add a second estimate for the same ad inventory to the first: two ways of describing one revenue stream are not two revenue streams.
Do not turn a rate into a guarantee
RPM is a rate derived from a dataset, not an assured payment for future traffic. For your planning worksheet, create a lower-rate case, a central case and a higher-rate case. Label them as assumptions rather than market benchmarks. WAM does not supply a universal expected RPM for a niche or country.
Also keep estimated and finalised earnings separate. Compare reports on the same basis and include the date range. If a report has no page views or impressions, the corresponding rate is undefined; do not use a missing denominator to create an apparently precise forecast.
Understand what extra ad inventory does not prove
The arithmetic relationship between impressions and revenue does not justify simply multiplying ad slots. Whether extra inventory serves, earns or affects the reader experience requires evidence from the actual setup. A planning calculator cannot establish fill, viewability, advertiser demand or policy eligibility.
Use the Ad Revenue Forecast Calculator to state assumptions across periods. If traffic and rate both vary, enter them separately. Averaging monthly RPMs without weighting their denominators can misrepresent a combined period. For example, combine total earnings and total views first, then calculate the overall page RPM.
Compare monetisation on a common audience basis
Affiliate EPC uses affiliate clicks, while page RPM uses page views. To compare them, first connect affiliate clicks to relevant visits with an explicit click-through assumption. The Affiliate vs AdSense Calculator provides a labelled comparison, and the Website Monetisation Calculator considers combined scenarios.
Neither approach proves that two revenue streams can be added without interaction. State which traffic belongs to each model and avoid counting the same commission or advertising estimate twice. Your next step is to annotate an existing report with its denominator, earnings status and period before using its rate in a forecast.