Revenue per session (RPS) is often an overlooked metric in the ecommerce world, yet it holds significant potential for driving business improvements.
We are going to bring RPS to the forefront of your analytics strategy, show how it can be used to measure and enhance the effectiveness of your ecommerce site.
What is Revenue Per Session?
Revenue per session calculates the average revenue generated per session on your websiteβ¦. I know (basically what it says)
It provides a clear picture of how effectively your site converts visits into revenue, making it a valuable tool for assessing overall site performance and guiding optimization efforts.
How to Calculate Revenue Per Session? Formula Included
To calculate Revenue per Session (RPS):
- Determine the total revenue generated during a specific period. This is the total amount of money your website made from sales.
- Find the total number of sessions that occurred on your website during the same period. A session refers to a single visit to your site, regardless of whether a purchase was made.
- Divide the total revenue by the total number of sessions. This will give you the average revenue generated per session.
Suppose your ecommerce store generated $100,000 in revenue from 10,000 sessions in a month. The RPS would be:
SELECT
100000.0 / 10000 AS revenue_per_session; -- Result: 10.0
This means that, on average, each session generated $10 in revenue.
Revenue per Session (RPS) Calculator
Weβve created a free online Revenue Per Session calculator to help you easily measure how much revenue each session on your site generates.
Use the calculator to quickly understand your siteβs efficiency in converting visits into revenue and identify opportunities for improvement!
For those seeking a more comprehensive solution of ecommerce metrics, VisionLabs offers custom dashboards that reveal your profit drivers, backed by expert strategists who turn data into action – all without the hassle of building an in-house team. If you want to know more, check our ecommerce data services
How to analyze Revenue Per Session
- Breakdown by Traffic Source:
- Analyzing RPS by traffic source can reveal which channels are most effective at driving revenue. Hereβs how you can do it in SQL:
SELECT traffic_source, SUM(revenue) / COUNT(session_id) AS revenue_per_session FROM sessions GROUP BY traffic_source;
This query breaks down RPS by traffic source for January 2023, helping you identify the most profitable channels.
- Weekly and Yearly Comparisons:
- Comparing RPS on a weekly or yearly basis helps track performance trends over time. Hereβs an example query:
- Optimizing Marketing Spend:
- By maintaining a consistent RPS, you can ensure that your marketing spend is efficient. For example, if your RPS from Facebook ads is $10, you should aim to keep your cost per click (CPC) below this threshold to ensure profitability.
Revenue Per Session Examples
Revenue Per Session on Shopify
On Shopify, you can monitor your RPS through the analytics dashboard. Suppose your store has a total revenue of $100,000 from 10,000 sessions. By calculating RPS, you determine itβs $10. However, if you isolate traffic from Facebook ads and find that it consistently generates $10 per session, this indicates your ad spend is efficient, helping you gauge the profitability of your campaigns.
Revenue Per Session on Google Analytics 4 (GA4)
You can use GA4 to create custom dashboards that display RPS alongside traffic sources and revenue. For instance, you can analyze how different marketing channels, such as email or paid ads, contribute to RPS.
Revenue Per Session Year-Over-Year Comparisons
You can also analyze RPS over time. For example, by comparing this week's RPS to the same week last year, you might find an increase from $9 to $10, indicating improved site efficiency or marketing effectiveness. Tracking these trends helps you assess whether your strategies are driving revenue growth.
Revenue Per Session Traffic Source Analysis
Breaking down RPS by traffic sources reveals valuable insights. If organic traffic generates $15 per session while paid traffic generates only $8, this could prompt you to reallocate your marketing budget towards organic channels. Additionally, looking at specific landing pages can show which ones convert better and yield higher RPS, guiding your optimization efforts effectively.
How to Improve Revenue Per Session
By understanding and optimizing RPS, you can make informed decisions that enhance profitability of your store as a whole.
Whether you're comparing performance over time, evaluating marketing campaigns, or guiding site improvements, RPS should be a key component of your analytics toolkit.
To improve Revenue Per Session, consider the following strategies:
- Upsells and Cross-Sells: Introduce upsell and cross-sell opportunities to increase the average order value. For example, if a customer is purchasing a pair of shoes, you could suggest complementary items such as socks or shoe care products before they complete their purchase. By presenting these relevant add-ons within the same session, you increase the chances of the customer spending more
- Site Efficiency: Optimize the user experience to make it easier for visitors to complete purchases. This can include improving page load speed, creating an intuitive browsing experience, streamlining the checkout process, etc.
- Targeted Offers: Use personalized promotions, like limited-time discounts or special offers based on browsing history, to encourage immediate purchases within sessions.
Why is Revenue Per Session Important to Marketers?
RPS is particularly useful for:
- Comparing Performance Over Time: Tracking RPS over different periods helps assess whether your site is becoming more effective at generating revenue.
- Evaluating Marketing Campaigns: RPS identifies the most profitable traffic sources, enabling more effective budget allocation.
- Guiding Split Testing and Iterative Improvements: RPS serves as a benchmark for testing new features, layouts, and offers to see if they enhance revenue generation.
Revenue Per Session vs. Average Order Value (AOV)
Revenue Per Session (RPS) and Average Order Value (AOV) are both critical metrics in ecommerce, but they provide different insights into performance.
RPS measures the average revenue generated for each session on your website, providing insight into overall site performance and efficiency in converting traffic into revenue. In contrast, AOV focuses specifically on the average revenue per order, indicating how much customers spend on average during a single transaction.
While RPS gives you a broad view of overall revenue efficiency and the effectiveness of your marketing campaigns, AOV allows you to evaluate the success of your upselling and cross-selling strategies. Understanding both metrics is essential for developing a comprehensive view of your business performance and identifying areas for improvement.
FAQs
How can I track Revenue Per Session?
You can track RPS using analytics tools like Google Analytics or ecommerce platforms such as Shopify, which provide data on total revenue and session counts.
What if my Revenue Per Session is low?
Consider optimizing your site for better user experience, implementing upsells and cross-sells, and analyzing traffic sources to improve performance.
How often should I review my Revenue Per Session?
Regularly review RPSβideally on a weekly or monthly basisβto identify trends and make informed decisions for ongoing optimization.