Session RPM (Revenue Per Mille Sessions)

Session RPM = (estimated earnings / number of sessions) × 1,000. A session is a group of user interactions within a given time frame — typically 30 minutes of inactivity resets it.

Where RPM looks at individual pageviews, Session RPM accounts for the full visit. A user who reads three articles in one session counts as one session but three pageviews. If your site drives deep engagement, Session RPM can be a truer measure of content value than page RPM.

When it matters most

• Content sites with high pages-per-session (e.g., recipe blogs, news outlets, tutorials)
• Sites using infinite scroll or single-page apps where a session spans many ad refreshes
• Any publisher trying to optimize for visit-level yield rather than per-page yield

Google AdSense Help defines Session RPM as “estimated earnings per thousand sessions,” reinforcing that it is a session-level metric, not a page-level one.

Session RPM = (Estimated earnings / Number of sessions) × 1,000

Example: If a site earns $500 from 50,000 sessions, Session RPM = ($500 / 50,000) × 1,000 = $10.00.

Important caveats

• Session definition varies by platform. Google Analytics uses a 30-minute timeout by default; some ad servers use their own session window. Always check the vendor’s definition.
• Estimated earnings are gross revenue before platform fees (unless otherwise noted).
• Cross-device sessions are usually counted separately — a user on phone and later on desktop creates two sessions.
• Session RPM is not additive across pages. You cannot sum page RPMs to get Session RPM because the denominator (sessions vs. pageviews) differs.

A rising Session RPM generally means you are earning more per visit — either because each page earns more, or because users view more pages per session, or both.

A flat or falling Session RPM while page RPM is stable suggests that session depth (pages per session) is declining. Users are leaving sooner, so each visit generates less total revenue even though per-page rates haven’t changed.

What to pair it with

• Pages per session — the main driver of Session RPM independent of ad rates
• Page RPM — to isolate whether changes come from ad pricing or session depth
• Bounce rate — a high bounce rate often drags Session RPM down because single-page sessions contribute little earnings

Easy mistake: A publisher sees Session RPM drop and immediately blames ad rates. But if page RPM is flat and pages per session fell from 2.5 to 1.8, the real issue is engagement, not CPM.

Increase session depth

• Internal linking — related articles, “you might also like” widgets
• Content series — multi-part guides that naturally lead to the next page
• Infinite scroll — keeps the session alive without a new page load (but watch ad refresh rules)

Improve per-page yield

• Ad layout & density — test ad placements without harming UX
• Header bidding — increase competition for each impression
• Direct deals — premium CPMs for high-value audiences

Reduce session fragmentation

• Page load speed — slow pages increase bounce rate and shorten sessions
• Mobile optimization — poor mobile UX kills session depth

Tradeoffs

Pushing session depth too aggressively can backfire. If you force users through multiple pages with low-value content, they may churn entirely. Similarly, cramming more ads onto each page can increase page RPM but reduce pages per session if the experience degrades. The best lever is content that naturally invites the next click — then monetize that extra pageview without over-optimizing either metric in isolation.

Session RPM gives a more complete picture of revenue per visit than page RPM, especially for engagement-heavy sites. It rewards both strong ad monetization and content that keeps users reading.

• Always pair Session RPM with pages per session and page RPM to understand what is driving changes.
• Session depth is a powerful lever, but forcing it without genuine user value can backfire.
• Standardize your session definition before comparing across platforms or time periods.