What the Ad Revenue Estimator Does
The ad revenue estimator projects advertising income for websites, blogs, and content apps using the pageview–RPM model that ad networks themselves use for forecasting. RPM (revenue per mille) is what a publisher earns per 1,000 pageviews after the network's share, blended across every ad unit on the page. It is more useful than CPM for planning because it already accounts for how many ads a page carries and how often they are actually viewed. Our editorial analysis uses RPM rather than headline CPM rates precisely because quoted CPMs describe a single ad slot, not a whole page.
```
Revenue = Pageviews × RPM / 1,000
```
What each input means
Worked example
A site receives 250,000 pageviews in a month at an $18 RPM.
1. Divide pageviews by 1,000: 250,000 / 1,000 = 250.
2. Multiply by RPM: 250 × $18 = $4,500 for the month.
Sensitivity — the same traffic at different RPM levels:
| Scenario | RPM | Monthly revenue |
| :--- | :--- | :--- |
| Low | $12 | $3,000 |
| Base | $18 | $4,500 |
| High | $25 | $6,250 |
A $7 RPM swing is worth $1,750 a month at this traffic level — more than many sites gain from a 30% traffic increase.
Limitations — when not to rely on this
RPM is not a constant. It moves with advertiser demand (strong in Q4, weak in January), audience country mix, device split, ad-blocker rates, and how many returning visitors have seen the same ads repeatedly. The estimator also assumes every pageview is monetizable; pages excluded by ad policy, consent refusals in the EU, and bot traffic earn nothing. Treat the output as a planning range anchored by the sensitivity table, not a forecast.
> [!TIP]
> If your network reports RPM by country, compute a blended RPM weighted by your traffic shares before using this estimator — a single global average hides the fact that 10% US traffic can out-earn 50% low-RPM traffic.