SaaS Product Analytics: The Metrics That Actually Matter

Every SaaS team collects data. Far fewer collect data they trust enough to make decisions with. The difference is rarely the analytics tool — it's how clearly the metrics are defined and how carefully events are recorded.

Each stage should have one clearly defined, countable event.

Start With a Funnel, Not a Dashboard

Before instrumenting anything, write the journey you want customers to take as a sentence. For Nuxused, the launch analytics followed exactly this idea: who came → who downloaded the apps → who became a school. Three days after deployment the live counters showed 35 visitors, 11 app downloads and 5 schools created — small numbers, but each one answered a real question.

A generic SaaS funnel looks like this:

1. Acquisition — a unique visitor arrives.
2. Sign-up — an account is created.
3. Activation — the user completes the first action that delivers value.
4. Retention — they come back and keep using it.
5. Revenue — they convert to a paid plan.

Define Activation Carefully

Activation is the most important and most frequently mis-defined metric. It is not "logged in". It's the moment a customer first experiences the product's core value — creating the first class and marking attendance in a school system, or sending a first invoice in a billing tool.

A good activation event is:

• specific and binary (it happened or it didn't),
• tied to value, not to navigation,
• achievable within the first session or first few days.

Write Counting Rules Down

Numbers become meaningless when nobody agrees how they're counted. Document rules such as:

• a visitor is counted once regardless of pages viewed,
• test and internal accounts are excluded,
• archived or deleted entities are excluded from active totals,
• a retained user performed a key action — not merely opened the app — in the given week.

If you can't explain a metric in one sentence, it's probably inflated.

Instrument Events on the Server

Client-side tracking is blocked by ad blockers and can be spoofed. Record business-critical events — sign-ups, activations, payments — on the server, where they happen.

await analytics.track({
  event: "school_created",
  tenantId: school.id,
  userId: user.id,
  properties: { plan: "trial", source: signup.source },
  timestamp: new Date(),
});

Use a consistent naming convention (object_action, past tense), include the tenant ID on every event, and never put personal data in event names.

Metrics That Matter for B2B SaaS

• Activation rate — sign-ups that reach the activation event.
• Time to value — how long activation takes.
• Weekly active accounts — accounts, not users, for B2B.
• Net revenue retention (NRR) — revenue kept and expanded from existing customers.
• Trial-to-paid conversion — the health check for self-service growth.

Make Metrics Visible

Publishing honest, live numbers — even small ones — builds trust with customers and keeps a team focused. A flat line on a public dashboard is a stronger motivator than any internal slide.

Key Takeaways

• Model the customer journey as a funnel before choosing tools.
• Define activation as the first moment of real value.
• Document counting rules and exclude test data.
• Track critical events server-side with consistent names and tenant IDs.

Sources

• Amplitude — North Star Framework
• PostHog — Product analytics documentation
• Segment — Tracking plan best practices