What the AdSense revenue calculator estimates
Display-ad earnings are often modeled in one of two ways. An RPM model multiplies page views by page revenue per thousand views. A click model estimates clicks from page views and click-through rate, then multiplies those clicks by average cost per click. Both are planning models, not promises about what Google AdSense or another network will pay.
Actual revenue varies with visitor country, device, topic, advertiser demand, season, consent choices, viewability, ad placement, invalid-traffic filtering, and the network's revenue share. Use recent data from your own reporting account whenever possible. A generic industry number may be useful for a range, but it is too weak for a precise business commitment.
Estimate revenue with page RPM
- Enter expected page views for the period you are forecasting.
- Enter a page RPM based on comparable historical traffic.
- Calculate estimated revenue and confirm that the period matches your input.
- Repeat with low, expected, and high RPM assumptions to create a range.
The formula is page views ÷ 1,000 × page RPM. If a site records 250,000 monthly page views at a $6 page RPM, the model returns $1,500 for that month. Page RPM already expresses revenue per thousand page views, so do not multiply it by an additional click estimate.
Estimate revenue from clicks
- Enter page views and the expected page click-through rate as a percentage.
- Enter average cost per click in the same currency used for your forecast.
- Calculate estimated ad clicks and revenue.
- Compare the implied RPM with your real reports as a reasonableness check.
The click model uses page views × CTR ÷ 100 × CPC. For 100,000 views, a 1.2% CTR, and a $0.35 CPC, it estimates 1,200 clicks and $420. This simplification assumes the CPC input represents publisher revenue per valid click. Reporting terminology can differ, so check whether your source figure is gross advertiser cost or your realized earnings.
Build a forecast you can defend
Match periods and traffic quality
Do not apply a holiday-season RPM to an ordinary month or a United States RPM to a forecast dominated by other regions. Segment historical performance by country, device, content type, and season when those differences are material. Forecast page views separately from monetization so a traffic assumption is not hidden inside the RPM.
Use scenarios instead of false precision
A low, base, and high case exposes uncertainty better than one number with cents. Change one assumption at a time to see whether traffic, RPM, CTR, or CPC drives the outcome. Record the source and date for every assumption, then replace estimates with actual reporting data as it becomes available.
Useful planning cases
A publisher can estimate how many additional monthly page views would support a content budget. A buyer reviewing a website can compare claimed revenue with a plausible RPM range, while remembering that verified account reports matter more than a calculator. An editor can compare a high-volume, low-RPM topic with a smaller commercial topic without assuming page views alone determine value.
The calculation does not include taxes, hosting, writers, ad-management fees, refunds, currency conversion, or revenue from subscriptions and affiliate links. Treat the result as gross modeled ad revenue unless your inputs already account for those factors. Never click your own ads or encourage invalid clicks to reach a forecast; networks can withhold earnings or suspend accounts for manipulated traffic.
Privacy
Calculations run in your browser and the entered figures do not need to be uploaded to PagesTools. Even so, use rounded or anonymized numbers on a shared screen if traffic and revenue are commercially sensitive. The calculator does not connect to your AdSense account, fetch reports, or store an account identifier. Your official dashboard remains the source of truth for finalized earnings.