Revenue per Session (RPS)

What is revenue per session?

Revenue per session (RPS) is the average revenue a publisher generates from each consumer session on their site or app. It is calculated by dividing total revenue over a period by the number of sessions in that period. RPS is a comprehensive monetization efficiency metric — it reflects not just the value of ad inventory, but the combined impact of traffic quality, placement optimization, and advertiser demand.

How does revenue per session work?

RPS combines two crucial metrics: total revenue and the number of user sessions. Sessions are defined as a group of user interactions with your website (e.g., page views, events, ecommerce transactions, etc.) that take place within a given time frame.

Marketers can segment RPS by various factors including traffic source, device type, user demographics, or product category for deeper insights. It’s important to evaluate RPS in conjunction with other metrics like conversion rate and average order value for a comprehensive understanding of user behavior and revenue generation.

How to measure revenue per session:

You can calculate RPS by dividing your total revenue in a specific timeframe by the total number of user sessions during the same period. For example, if your website generated $10,000 in revenue and had 1,000 user sessions in a month, your RPS would be $10 per session.

Why is revenue per session important to marketers?

Tracking RPS allows marketers to:

• Measure overall website/app performance - Example: High RPS indicates efficient user engagement and revenue generation.
• Identify areas for improvement - Example: Declining RPS suggests potential issues with user experience, marketing strategy, or product offerings.
• Analyze marketing campaign effectiveness - Example: Compare RPS across different campaigns to gauge which ones drive the best performance.
• Inform future strategies - Example: Optimize website design, product pricing, and marketing efforts based on RPS insights.

Who needs to know what revenue per session is:

• Retail marketing manager
• Ecommerce manager
• Performance marketer
• Digital marketer
• Marketing manager
• App developer

RPS as a post-transaction monetization benchmark

For publishers evaluating post-transaction monetization strategies, RPS is a useful benchmark for comparing the incremental revenue impact of adding a commerce media layer to their confirmation pages. Because post-transaction placements reach only a subset of sessions — those that result in a completed transaction — they should be evaluated on revenue per converting session rather than across all sessions.