For many publishers, page RPM is one of the first metrics they check when evaluating monetization performance.
And for good reason: it quickly shows how much revenue a website generates per 1,000 pageviews.
But there is a problem.
Optimizing only for page RPM can sometimes lead publishers toward decisions that improve short-term ad revenue while damaging the user experience, reducing page depth, and ultimately lowering the amount of money generated from each visitor.
That is why revenue per session deserves much more attention.
Page RPM vs. Revenue per Session
The two metrics answer different questions.
| Metric | What it tells you | Best used for |
| Page RPM | Revenue generated per 1,000 pageviews | Comparing page layouts, ad units and monetization efficiency |
| Revenue per Session | Average revenue generated during one complete user visit | Understanding the total value of a visitor |
| Pages per Session | How many pages a visitor views | Measuring engagement and content discovery |
| Session Duration | How long users stay | Understanding overall engagement and UX quality |
Page RPM is calculated as:
Page RPM = Ad Revenue / Pageviews × 1,000
Revenue per session is even simpler:
Revenue per Session = Total Ad Revenue / Total Sessions
The important difference is perspective.
Page RPM focuses on the page.
Revenue per session focuses on the user.
Why Page RPM Can Be Misleading
Imagine a publisher redesigns an article page and adds more advertising:
- another sticky unit;
- additional in-content placements;
- a larger ad above the fold;
- more frequent ad refreshes.
As a result, page RPM increases from $8 to $11.
At first glance, this looks like a successful optimization.
But users may now find the page slower and more difficult to read. Instead of visiting three articles during a session, they leave after the first page.
Consider the numbers:
| Scenario | Page RPM | Pages per Session | Approx. Revenue per Session |
| Better UX | $8 | 3.0 | $0.024 |
| Aggressive monetization | $11 | 1.6 | $0.0176 |
The second setup generates significantly more money per pageview, yet less money per visitor session.
This is the danger of optimizing a single metric in isolation.
The Hidden Cost of Aggressive Monetization
Increasing ad density can certainly improve revenue, but only until it starts affecting user behavior.
Common side effects include:
- higher bounce rates;
- fewer pages viewed per visitor;
- slower page load times;
- lower return visitor rates;
- weaker organic search performance;
- increased ad-block usage.
A page with an impressive RPM is not necessarily a well-monetized page if users immediately leave afterward.
Publishers should therefore think about monetization as a balance between ad value and audience engagement.
Revenue per Session Gives a Bigger Picture
Revenue per session helps answer a more useful business question:
How much money does an average visitor generate before leaving the website?
That makes it particularly valuable when evaluating changes affecting the overall user journey.
For example, publishers can compare:
- different ad densities;
- sticky vs. non-sticky placements;
- autoplay video implementations;
- pagination vs. infinite scroll;
- recommendation widgets;
- internal linking strategies;
- ad refresh rules.
A change that slightly reduces page RPM may still be extremely valuable if it encourages visitors to consume more content.
For example:
Before optimization
Page RPM: $10
Pages/session: 1.8
Revenue/session: approximately $0.018
After UX improvement
Page RPM: $9
Pages/session: 2.6
Revenue/session: approximately $0.023
Page RPM dropped by 10%, but total monetization per session increased by almost 28%.
That is a much healthier outcome.
So Which Metric Should Publishers Optimize?
The answer is: both — but at different levels.
Page RPM remains extremely useful for evaluating the performance of individual pages, placements, formats and demand sources.
Revenue per session should be used to understand whether those optimizations actually increase the value generated from users.
A practical publisher dashboard should therefore monitor at least:
- Page RPM
- Revenue per session
- Pages per session
- Bounce or engagement rate
- Average session duration
- Viewability
- Core Web Vitals / page speed
The relationship between these metrics matters more than any single number.
Optimize the User Journey, Not Just the Ad Slot
Modern publisher monetization is no longer simply about fitting the maximum number of ads onto a page.
The strongest monetization strategies increase revenue without giving users a reason to leave.
A higher page RPM might look great in a weekly report. But if the same optimization shortens sessions and reduces page depth, the website may ultimately earn less.
The better question is therefore not:
“How much revenue does this page generate?”
It is:
“How much revenue does this visitor generate during the entire session?”
This is also where the right monetization partner can make a real difference. Instead of simply increasing ad pressure, publishers need formats and optimization strategies that improve yield while keeping the user experience healthy.
With Clickaine, publishers can test and optimize monetization setups across multiple ad formats while paying attention not only to immediate RPM, but also to how those choices affect the broader user journey.
The goal should not be to extract the maximum value from a single pageview. It should be to build a monetization setup that keeps users engaged, creates more opportunities to serve valuable ads, and generates more revenue over the entire session.
For publishers looking for sustainable growth, that is a much stronger metric to optimize around.