Product analytics vs revenue analytics
SaaS teams often track product analytics and revenue analytics in different tools. SaaS Tracker focuses on organization-level product usage, and can incorporate revenue data so you can prioritize based on both activity and value.
This page explains the difference between product analytics and revenue analytics, and what changes when you combine them.
Product analytics
Product analytics focuses on what people do in your product:
- which pages and features they use
- how many events occur per day
- how active your users and organizations are
- where users drop off in key flows
Typical outputs include:
- dashboards for activity, top pages, and feature adoption
- organization health scores based on usage patterns
- funnels and event streams to debug behavior
In SaaS Tracker, these are primarily powered by events sent to the Ingest API with event, user_hash, customer_org_id, and path.
Revenue analytics
Revenue analytics focuses on who pays and how much:
- subscriptions and contracts per customer organization
- MRR, ARR, and ARPA
- new vs churned revenue by month
- revenue concentration across customers and products
In SaaS Tracker, revenue analytics is based on imported subscription data per customer organization. It powers:
- Revenue (MRR, ARR, paying orgs, ARPA)
- Revenue by health
- Revenue × Health matrix
- Top revenue organizations
Revenue analytics is separate from SaaS Tracker’s own billing – the data comes from your customer organization subscriptions, not from your workspace subscription.
Comparison
| Product analytics | Revenue analytics |
|---|---|
| Events and usage behavior | Subscriptions and MRR/ARR |
| What users and orgs do | What customers pay and how much |
| Health scores and activity trends | Revenue trends and composition |
| Helps improve product and engagement | Helps understand commercial impact |
Both views are important. Product analytics tells you what is happening, revenue analytics tells you how much it matters financially.
When you combine them
When you combine product analytics and revenue analytics at the customer organization level, you can answer questions like:
- Which high-MRR organizations have low health or usage drop?
- Which healthy organizations could be expansion candidates?
- How much of your MRR is concentrated in a small number of orgs?
In SaaS Tracker, these ideas show up as:
- Revenue at risk – MRR from organizations whose health is low
- Inactive paying customers – paying orgs with no recent activity
- Expansion candidates – healthy orgs with growing usage
- Revenue × Health segments – champion, expansion, at-risk, low value
This makes it easier for customer success, product, and revenue teams to prioritize the right organizations, not just the noisiest ones.