Glossary
What is Revenue per session?
Also called: RPS, session RPM, revenue per 1,000 sessions
Revenue per session is total ad revenue divided by sessions: what one visit earns across every page it views. It is often shown per 1,000 sessions.
हिंदी में पढ़ेंPage RPM tells you what each page view earns. Revenue per session tells you what each visit earns, because it combines page value with pages per visit: revenue per 1,000 sessions equals page RPM × pages per session. At the same page RPM, a visitor who reads three pages earns three times as much as one who reads one page.
That makes it the fairer score for many decisions. Extra ads can lift page RPM but cut pages per session, and revenue per session shows when they start to cost more than they earn. It is also the metric to use in A/B tests, in holdouts for new demand partners and when comparing traffic sources.
It matters more as search changes. In a Pew Research study of browsing in March 2025, people clicked a regular result on 8% of visits when an AI summary appeared, against 15% without one. When search sends fewer visits, the sessions you keep, such as newsletter and direct readers, carry more of your revenue.
Example
A news site has 1,000,000 sessions a month at 1.5 pages each and a $10 page RPM: 1,500,000 page views × $10 ÷ 1,000 = $15,000, or $15 per 1,000 sessions. Lose 10% of sessions and revenue falls to $13,500, though page RPM did not move.
Why it matters to publishers
Optimising page RPM alone can quietly cost visits. Revenue per session keeps ad load, speed and traffic quality in one number.