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.
What this means
Session RPM = (estimated revenue ÷ sessions) × 1,000. Where page RPM normalizes to pageviews, session RPM normalizes to sessions — a session being one visit, grouped by an inactivity timeout. The result is revenue per thousand visits, blending every ad shown across all pages in a visit. It answers 'how much does a visit earn' rather than 'how much does a page earn'.
Why it differs from page RPM
Page RPM and session RPM diverge whenever pages-per-session changes. A site that earns the same per visit but spreads it over more pages will show a lower page RPM but an unchanged session RPM. That makes session RPM more robust to layout and navigation changes and a better gauge of per-visitor value. The catch is the session definition: the inactivity timeout and reset rules (which differ between tools) change the session count and therefore the metric, so session RPM is comparable only within one consistent session definition.
This page is educational and not financial advice.
- (Revenue ÷ sessions) × 1,000
- Credits a whole visit, not a single page
- Depends on the session timeout/definition used
How it appears in analytics and logs
A higher session RPM means each visit earns more across all the pages it touches. Unlike page RPM, it does not fall just because visitors view fewer pages — it credits the full visit, so it reflects per-visitor monetization.
Diagnostic use case
Track earnings per visit rather than per page, to value monetization across a whole session and reduce sensitivity to pages-per-session differences.
What WebmasterID can help detect
WebmasterID groups sessions first-party with a documented timeout and classifies bots out, so the session denominator behind session RPM reflects real visits.
Common mistakes
- Comparing session RPM and page RPM as the same metric.
- Ignoring how the session timeout changes the denominator.
- Computing it on bot-inflated session counts.
Privacy and accuracy notes
Session RPM aggregates revenue over session counts and needs no personal identifiers. This page is educational and not financial advice.
Related pages
- 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.
- Sessions: what a session is and when it resets
A session is a group of interactions from one visitor within a bounded time window. It starts on the first event and ends after a period of inactivity (commonly 30 minutes, configurable). The reset rules differ by tool — and historically Universal Analytics also restarted sessions at midnight and on a new campaign — so the same traffic produces different session counts in different products.
- 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
Group human sessions first-party behind RPM.
Sources and verification notes
- Google AdSense Help — What is RPM?Defines RPM as revenue per thousand units; session RPM applies the same formula to sessions, a publisher convention.
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.