Analytics for SaaS: what to track beyond signups

I work with a lot of SaaS companies, and almost all of them have the same blind spot. They track signups religiously. They know exactly how many people registered, which channel they came from, and what the cost per signup is. Then there’s a black hole. The next metric they track is monthly recurring revenue. Everything between signup and revenue is invisible.

That’s a problem, because the gap between “someone signed up” and “someone pays us money every month” is where SaaS businesses actually succeed or fail. A SaaS company can double its signups and still shrink if activation and retention are broken. I’ve seen it happen.

SaaS analytics is fundamentally different from e-commerce analytics. In e-commerce, the funnel ends at purchase. In SaaS, the funnel starts at signup. The interesting data comes after.

The SaaS measurement framework

I use a six-stage framework for SaaS measurement. It’s not original (it’s inspired by pirate metrics, AARRR), but I’ve refined it based on what actually works in practice. Here are the stages:

Acquisition is how users find you. Website visits, landing page performance, channel attribution. Standard stuff that any analytics setup covers.

Activation is the moment a user gets real value from your product for the first time. This is the most important stage and the one most companies define poorly.

Engagement measures ongoing usage. Are activated users coming back? Are they using core features? How deeply are they embedded in your product?

Retention is whether users stick around over time. Weekly, monthly, quarterly. Cohort-based, not aggregate.

Revenue connects usage to money. Trial conversions, plan upgrades, expansion revenue, churn.

Referral tracks organic growth. Do users invite others? Do they share your product?

Each stage requires different events, different metrics, and often different tools. Let me break each one down.

Acquisition: what to track and what to skip

Acquisition analytics for SaaS is similar to any other business, but with a few SaaS-specific considerations.

Track: visits by channel, landing page conversion rates, signup conversion rate by channel, cost per signup by channel, content engagement (for content-led growth).

Skip (or deprioritize): vanity metrics like total pageviews, bounce rate in isolation, social media followers. These feel good but don’t correlate with revenue for most SaaS products. GA4 has powerful audience features that most SaaS teams overlook entirely — I cover them in GA4 audiences nobody uses.

The metric I focus on here is cost per activated user by channel, not cost per signup. A channel that delivers cheap signups but low activation is worse than an expensive channel with high activation. You won’t know this unless you connect acquisition data to activation data, which requires passing identifiers from your marketing analytics into your product analytics.

Practical implementation: when a user signs up, capture the UTM parameters and GA4 client ID in your backend. Store them with the user record. Now you can join marketing data with product data later.

Activation: the metric most SaaS companies get wrong

Activation is the single most important metric in SaaS analytics, and it’s the one I spend the most time defining with clients.

The activation event should represent the moment a user experienced your product’s core value. Not when they completed onboarding. Not when they logged in the second time. The moment they got the “aha.”

For a project management tool, it might be: created a project AND invited a team member AND completed a task. For an email marketing tool: imported contacts AND sent a first campaign. For a data analytics tool: connected a data source AND created a dashboard.

Notice that activation is usually a combination of actions, not a single event. This makes it harder to track but more meaningful to measure.

What to track:

• Activation rate: percentage of signups who reach the activation milestone
• Time to activation: how long it takes from signup to activation
• Activation funnel: conversion rate at each step of the activation sequence
• Activation by cohort: is your activation rate improving over time as you refine onboarding?

How to implement: Define your activation criteria as a composite event. In your product backend, check after each relevant user action whether the activation criteria are met. When they are, fire an “activated” event with a timestamp. Push this to both your product analytics (Mixpanel, Amplitude) and your marketing analytics (GA4) so you can analyze it from both sides.

Time to activation is my favorite diagnostic metric. If it takes 14 days for users to activate, you have an onboarding problem. If it takes 14 minutes, you’ve nailed it. I worked with a SaaS client where we discovered their average time to activation was 9 days. We identified three friction points in the setup flow, removed them, and dropped it to 2 days. Trial-to-paid conversion jumped 40% in the next quarter.

Engagement: beyond DAU/MAU

Daily active users divided by monthly active users. The classic engagement metric. It’s useful as a top-level health indicator, but it tells you nothing about what users are doing or whether they’re getting value.

I prefer tracking engagement through feature adoption and usage depth.

Feature adoption rate for each core feature: what percentage of activated users use this feature in a given period? This tells you which features drive value and which ones you built for nothing. I once audited a B2B SaaS product with 47 features. Only 6 had adoption rates above 20%. The team was spending engineering time on features that 95% of users never touched.

Usage frequency by feature: how often do users perform key actions? Daily? Weekly? This tells you whether users are forming habits around your product.

Usage depth: are users doing more over time? More projects, more team members, more integrations? Growing usage within an account is the strongest predictor of retention I’ve found.

Session duration and session count are secondary metrics. They’re easy to track but hard to interpret. A user spending 45 minutes in your app might be deeply engaged, or might be confused and struggling. Context matters.

What to track technically: fire events for every meaningful user action. Not button clicks (that’s too granular). Actions that represent value: “created_report,” “invited_member,” “connected_integration,” “exported_data.” I lay out the full approach to choosing which events matter in my GA4 event tracking strategy guide. Attach properties: which plan the user is on, how long they’ve been a customer, how many team members they have. This context turns raw event data into actionable insight.

Retention: cohorts or nothing

Aggregate retention metrics are misleading. If your total user count is growing, your overall retention rate can look stable even while individual cohorts are churning badly. New signups mask the losses.

Cohort retention is the only honest way to measure stickiness. Group users by their signup month (or week). Track what percentage of each cohort is still active in month 1, month 2, month 3, and so on.

What you’re looking for: a curve that flattens. If your month-3 retention is 40% and your month-6 retention is 38%, you’ve found your stable base. If the curve keeps dropping and never flattens, you have a fundamental product-market fit problem that no amount of marketing will fix.

Track:

• Cohort retention by week and month
• Retention by activation status (activated users vs. non-activated)
• Retention by acquisition channel (does one channel produce stickier users?)
• Retention by plan tier
• Churn reasons (exit surveys, cancel flow data)

The most revealing analysis I run for SaaS clients: retention by activation status. The gap is always dramatic. Activated users retain at 60-80% after 6 months. Non-activated users retain at 5-15%. This single chart justifies every investment in improving activation.

Revenue: connecting usage to money

SaaS revenue analytics goes beyond “how much MRR do we have.”

Trial-to-paid conversion rate by cohort, by channel, by plan. If you have a free trial, this is the metric that connects your entire funnel. Low trial-to-paid despite good activation? Your pricing might be wrong, or your trial length might be off, or you’re not communicating value at the right moment.

Expansion revenue from existing customers. Upgrades, additional seats, add-on features. For mature SaaS products, expansion revenue should exceed 30% of new MRR. Track the events that precede expansion: hitting usage limits, adding team members, using premium features.

Contraction and churn revenue. Downgrades and cancellations. Track which plan changes happen and when. If users consistently downgrade at month 4, something happens at month 4 that reduces perceived value.

Net Revenue Retention (NRR). The gold standard SaaS metric. Above 100% means your existing customers are growing faster than they’re churning. Track this monthly and by cohort.

Connecting this to analytics: your billing system (Stripe, Chargebee, Paddle) has the revenue data. Your product analytics has the usage data. Your marketing analytics has the acquisition data. The power is in connecting them. I typically build this connection through a data warehouse (BigQuery or Snowflake) that ingests data from all three sources and joins them on user ID.

Connecting marketing analytics to product analytics

This is where most SaaS analytics setups fall apart. Marketing lives in GA4. Product lives in Mixpanel or Amplitude. Revenue lives in Stripe. Nobody can answer the question: “Which marketing channel produces users with the highest lifetime value?”

The connection point is the user identifier. When a user signs up:

1. Capture their GA4 client ID (from the _ga cookie or via the Measurement API)
2. Store it with their user record in your database
3. When you send product events to Mixpanel/Amplitude, include a property linking to the GA4 identifier
4. Export everything to BigQuery where you can join across sources

This sounds like a lot of plumbing. It is. But it’s the plumbing that separates SaaS companies that make data-driven decisions from ones that make gut-driven decisions with a data dashboard on the wall.

An alternative approach: use GA4 for both acquisition AND product analytics by sending product events via the Measurement Protocol. This works for simpler products but breaks down when you need advanced product analytics features like funnel analysis, path analysis, and behavioral cohorting that Mixpanel and Amplitude handle better.

The tools

My typical SaaS analytics stack:

GA4 for acquisition analytics. Website traffic, channel attribution, landing page performance, signup conversion. GA4 is good at this.

Mixpanel or Amplitude for product analytics. Feature adoption, user flows, retention cohorts, behavioral analysis. These tools are purpose-built for product analytics and do it much better than GA4. Mixpanel is my go-to for most clients because the pricing is more predictable and the query interface is faster.

Stripe/billing platform for revenue data. MRR, churn, LTV, expansion revenue.

BigQuery as the data warehouse. Ingests data from all sources. This is where cross-functional analysis happens. Where you answer “what’s the LTV of users acquired through organic search who activated within 48 hours?”

Looker Studio or Metabase for dashboards. I prefer Metabase for SaaS dashboards because it connects directly to your data warehouse and supports SQL-based metrics that Looker Studio can’t handle easily. That said, most dashboards I encounter are beautiful but useless because they show vanity metrics instead of actionable ones.

The dashboard SaaS founders actually need

I’ve built many SaaS dashboards. Most of them had too many metrics. The dashboard that founders actually check daily has five sections:

Today: new signups, activations, trial conversions, MRR change. Four numbers. That’s it.

This week vs. last week: the same four metrics, compared. Are things trending up or down?

Funnel: signup > activation > trial conversion > paid retention. Conversion rates at each stage, current month vs. previous month.

Cohort retention: a heatmap showing monthly cohorts and their retention rates over time. One glance tells you if retention is improving.

Revenue: MRR, net new MRR (expansion minus contraction minus churn), and NRR. Three numbers that tell you whether the business is healthy.

Everything else goes in a secondary dashboard that product managers and growth teams use for deeper analysis. The founder dashboard is a health check, not an investigation tool.

Getting started

If your SaaS analytics currently stops at signups, here’s the order I’d tackle things:

First, define your activation event. Get your team in a room and agree on what “activated” means. Be specific. Write it down.

Second, implement activation tracking. Fire the event when users hit the criteria. This alone will transform your understanding of your funnel.

Third, set up cohort retention reporting. Even a simple spreadsheet that tracks weekly cohort retention gives you more insight than months of aggregate metrics.

Fourth, connect acquisition to activation. Store UTM parameters with user records. Now you know which channels produce users who actually activate.

Fifth, add revenue data. Connect Stripe to your data warehouse. Join it with product data.

Each step builds on the previous one. Don’t try to do everything at once. Start with activation. That single metric will change how your team thinks about growth.