Page RPM (revenue per mille)
Page RPM (revenue per mille) is estimated earnings per thousand pageviews: total revenue divided by pageviews, times 1,000. It is the publisher-side companion to CPM — where CPM is what an advertiser pays per thousand impressions, RPM is what a page earns per thousand views, blending fill, viewability, and multiple ad units. Google AdSense documents the calculation; it is a derived metric, not a guaranteed rate.
What this means
Page RPM = (estimated revenue ÷ pageviews) × 1,000. It expresses earnings on a per-thousand-pageviews basis so pages with different traffic can be compared on revenue efficiency. Google AdSense defines page RPM exactly this way and contrasts it with impression RPM (per thousand ad impressions) and query RPM. RPM is the publisher's mirror of the advertiser's CPM.
Why it is derived, not a price
RPM is an outcome, not a rate you set. It rolls up everything between a pageview and revenue: how many ad units a page shows, what share of slots fill, viewability, advertiser demand, and the mix of ad types. Two pages with identical traffic can have very different RPMs because of layout and demand. That makes RPM useful for normalized comparison but misleading if read as a fixed earning rate — it moves whenever any link in the monetization chain changes. Use it with fill rate and CPM to see why it moved.
This page is educational and not financial advice.
- (Revenue ÷ pageviews) × 1,000
- Publisher mirror of CPM; blends fill, viewability, unit count
- An outcome metric, not a guaranteed rate
How it appears in analytics and logs
A higher page RPM means each thousand views earns more — driven by ad demand, fill, viewability, and how many units a page carries. It is an outcome metric, so changes reflect the whole monetization chain, not a single price.
Diagnostic use case
Track how much a thousand pageviews earns across all monetization on the page, to compare content or layouts on a normalized revenue basis.
What WebmasterID can help detect
WebmasterID counts pageviews first-party with bots classified out, so the pageview denominator behind RPM reflects human views rather than inflated counts.
Common mistakes
- Reading RPM as a fixed earning rate rather than an outcome.
- Comparing page RPM to impression RPM as if identical.
- Computing RPM on bot-inflated pageviews.
Privacy and accuracy notes
Page RPM aggregates revenue over pageview counts and needs no personal identifiers. This page is educational and not financial advice.
Related pages
- Session RPM (revenue per session)
Session RPM is estimated revenue per thousand sessions: total revenue divided by sessions, times 1,000. It normalizes earnings to visits rather than pageviews, so it rewards monetizing an entire session — across every page a visitor sees — rather than a single page. It became prominent as ad programs shifted toward session-based reporting. The session definition matters, and it is a publisher convention layered on standard RPM.
- Cost per mille (CPM)
Cost per mille (CPM) is the cost of one thousand impressions — 'mille' is Latin for thousand. It is the standard pricing unit for awareness and display buying, where advertisers pay for exposure rather than clicks. CPM depends entirely on how an impression is defined (served vs viewable), and it says nothing about whether anyone clicked or converted, so it is an exposure-cost metric only.
- Ad fill rate
Ad fill rate is the percentage of ad requests that were answered with an ad — ads served divided by ad requests. A request that returns no ad ('unfilled') earns nothing, so fill rate directly gates a publisher's revenue: low fill means inventory went to waste. Google Ad Manager reports fill rate from match rate and coverage. It is a documented programmatic metric, though exact request/impression accounting varies by platform.
- Web analytics
Count human pageviews behind RPM first-party.
Sources and verification notes
- Google AdSense Help — What is RPM?Defines page RPM, impression RPM, and query RPM with the calculation.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.