Analytics
B2B Product Analytics: What to Track and Why
Mixpanel is the best first pick for most B2B SaaS teams that are starting to track product usage. Its free plan covers up to 1M monthly events, and the Growth plan covers up to 20M monthly events for $140 a month, or $120 a month billed annually. A team can start without a budget decision and move to a paid plan only when event volume grows.
Who this guide is for
This guide is written for B2B SaaS teams that sell to companies rather than to individual consumers. That usually means product managers, growth leads and data-minded founders who need to see how usage looks at the account level, not only per login. If your traffic is mostly marketing-site visits, a web analytics tool may serve you better. The tools below were chosen because they track what happens inside the application.
What makes B2B product analytics different
A B2B contract is usually signed by one buyer, used by several roles and renewed or expanded at the account level. That changes what you need to measure and how you should set up your tracking.
Track users and accounts together
Individual events matter, but renewal decisions are made by the company. Map every user to an account identifier, compare seats in use with seats purchased, and look at account activity side by side for accounts of different sizes.
Separate the roles
Admins configure the product, end users work in it and executives read reports. Track each role as its own segment. An admin who logs in every day is not evidence that end users are getting value.
Use cohort windows that fit the sales cycle
Many business rollouts take weeks, and some take a full quarter. A seven-day retention view will mislead you about an account that is still in its first rollout phase. Set cohort windows that match how long your customers take to adopt the product.
Tie usage to revenue
Feature adoption is useful when it changes a conversation: a renewal call, a seat expansion or a pricing decision. If a usage report does not lead to one of those actions, it is decoration.
The metrics to track first
Start with a short list. Most B2B teams get more value from ten well-defined metrics than from a dashboard with fifty charts. The groups below cover the stages of an account's life.
Activation
- Time to first value: the elapsed time from account creation to the first completed core action in your product.
- Activation rate: the share of new accounts that complete the onboarding steps you define.
- Feature adoption in the first seven days: the share of new accounts that use your key features in their first week.
- The aha moment: the action that, in your own cohort data, appears most often before a trial becomes a paying account. Find it by comparing behavior of converted and non-converted accounts, not by guessing.
Engagement and retention
- Active users by account: daily, weekly and monthly active users counted per company, not only across the whole product.
- Stickiness: weekly active users divided by monthly active users, a rough measure of habitual use.
- Feature frequency: how often each core feature is used, and by which roles.
- Cohort retention: retention curves by signup month, compared against your own earlier cohorts.
Compare your retention curves with your own history rather than with a rule of thumb from someone else's business. A fixed threshold can be useful as a starting point, but it should be tested against your own cohorts before you rely on it.
Revenue links
- Trial-to-paid conversion: the share of trial accounts that become paying customers, split by the activation path they took.
- Seat expansion and upgrade rate: how often accounts add seats or move to a higher plan.
- Churn precursors: behaviors that come before cancellation. A common one is falling weekly activity in the weeks before a renewal, but you should confirm the pattern in your own data.
- Power accounts: the accounts that use the most features or the most events, which are often the best candidates for expansion conversations.
Comparison of the main tools
The six tools below cover most B2B SaaS shortlists. Prices are the starting points shown on each vendor's pricing page when we last checked it on 7 October 2026. Where a vendor does not publish a dollar price for a plan, the table says so.
| Tool | Best for | Starting price (plan and billing) | Key limitation |
|---|---|---|---|
| Mixpanel | Event-based product teams that need funnels and cohorts | Free: up to 1M monthly events. Growth: $140 a month, or $120 a month billed annually, for up to 20M monthly events | Paid cost rises with event volume, so a noisy tracking plan costs money |
| Amplitude | Teams that want behavioral cohorts, experimentation and replay | Free: 2M events a month with no time limit. Plus: the first 2M events a month are free, higher volume is pricing on request | Growth and Enterprise are priced on request, so budgeting needs a sales conversation |
| Heap | Small teams with limited engineering time that want retroactive capture | Free: up to 10k monthly sessions and 6 months of data history | Paid tiers are pricing on request, and Session Replay is an add-on on Pro |
| PostHog | Engineering-led teams that want analytics, replay, feature flags and experiments in one tool | Free monthly allowance on every product, then pay-as-you-go | Usage is metered per product, so the bill needs regular review; the free tier allows one project |
| Fullstory | Teams that start from session replay and qualitative debugging | Free: 30,000 monthly sessions, 12 months of analytics retention, up to 10 users | Business, Advanced and Enterprise are priced on request; the free plan caps users at 10 |
| Pendo | Product teams that combine analytics with in-app guides and surveys | Pricing on request, sized by monthly active users; a free trial is offered | No published dollar prices, and surveys and data sync sit in the top tier |
Tool by tool
Mixpanel: event-based analysis for product teams
Mixpanel is built around events. Each action in your product is recorded with properties, and reports such as funnels, retention and flows are built on those events. For B2B SaaS this fits well, because most of the questions you ask are event questions: did this account reach the second workflow, which role invited the second user, how long did the rollout take in accounts of a given size.
What it does well for this audience: funnels and cohort retention are the core of the product, and the account-level views make it easier to move from individual user events to company-level questions. The free plan is a practical place to build a tracking plan before you commit to a paid volume.
Where it falls short: on paid plans, cost follows event volume, so every event you add to the tracking plan has a price. Session replay and experimentation are not its main strengths, so teams that want a single tool for every product task may need another one alongside it.
Price: Free for up to 1M monthly events. Growth is $140 a month, or $120 a month billed annually, for up to 20M monthly events. Enterprise is priced on request. See Mixpanel's pricing page for current terms.
Amplitude: behavioral analysis and experiments
Amplitude is designed for teams that analyze behavior in depth and run experiments against it. Its behavioral cohorts and exploration tools go further than a standard funnel report, and the Plus tier adds alerts, heatmaps and two years of data retention.
What it does well for this audience: behavioral cohorts for segmenting accounts by what they do rather than by static attributes, guides and surveys on the free tier, and session replay with monthly allowances on the free and higher plans.
Where it falls short: the features that matter most to larger organizations, such as advanced behavioral exploration, SSO and project permissions, sit in the Growth and Enterprise tiers, which are priced on request. Smaller teams may find the number of tiers harder to navigate than a single event-based plan.
Price: Free for 2M events a month with no time limit. Plus starts with the first 2M events a month free, and scales up to 70M events; higher volume and the Growth and Enterprise tiers are pricing on request. See Amplitude's pricing page.
Heap: retroactive auto-capture
Heap captures user interactions automatically once it is installed, so you can define events after the fact and analyze behavior that happened before you wrote a specific tracking call. For a team with few engineers, that reduces the initial instrumentation work.
What it does well for this audience: quick setup, virtual event definitions that let analysts name events without a developer release, and a free plan with core charts, SSO and six months of data history.
Where it falls short: automatic capture produces more raw data, so the naming discipline you would apply to manual events still matters. Longer data history, unlimited users and reports, account analytics and data warehouse integration all sit in paid tiers that are priced on request. Session Replay is an add-on on the Pro tier.
Price: Free for up to 10k monthly sessions with 6 months of data history. Growth, Pro and Premier are pricing on request. See Heap's pricing page.
PostHog: analytics, replay, flags and experiments in one tool
PostHog combines product analytics, session replay, feature flags, experiments and surveys in one platform. It is open source and can be self-hosted, which matters to teams with strict data residency rules.
What it does well for this audience: a single place to see how a feature performs, what users did in it, and which flag or experiment was active at the time. The free tier includes a monthly allowance on every product, and it has no minimums or annual commitment.
Where it falls short: usage is metered per product, so the total bill depends on how much of each product you use. The free tier allows one project with one year of data retention, while pay-as-you-go includes six projects and seven years of retention. Non-engineers will need developer help to get the most out of it.
Price: a free monthly allowance on every product. Pay-as-you-go pricing is charged per unit used, and the unit rates are on request. See PostHog's pricing page.
Fullstory: replay-first debugging and insight
Fullstory starts from session replay and moves toward analytics. It is most useful when your questions are about why a workflow failed for a particular account, rather than how many accounts reached a step.
What it does well for this audience: the free plan includes session replay, basic analytics and debugging tools for up to 30,000 monthly sessions, with 12 months of analytics retention.
Where it falls short: deep product analytics, trends and funnel improvement at scale are paid features, and the free plan caps users at 10. Teams that need broad cohort analysis may use Fullstory alongside a dedicated analytics tool.
Price: FullstoryFree is free. Business, Advanced and Enterprise are priced on request. See Fullstory's pricing page.
Pendo: analytics with in-app guidance and surveys
Pendo combines product analytics with in-app guides, and its higher tiers add session replay and feedback surveys. It suits product teams that want to act on usage inside the application, not only in reports.
What it does well for this audience: the Base tier covers product analytics and in-app guides, Core adds session replay, and Ultimate adds NPS, product-market fit and CSAT surveys along with data sync.
Where it falls short: Pendo does not publish dollar prices, and plans are sized by monthly active users, so the cost is only known after a quote. The surveys and data sync that many B2B teams want are in the top tier.
Price: pricing on request, sized by monthly active users. A free trial is offered. See Pendo's pricing page.
What each tool costs at realistic volumes
Event and session volumes drive most of the cost of these tools. The table compares the plans that apply at three common sizes. Where a plan has no published dollar price for that volume, the table says pricing on request.
| Monthly volume | Tool and plan | Price | Billing |
|---|---|---|---|
| 500k events | Mixpanel Free (up to 1M monthly events) | $0 | Free |
| 500k events | Amplitude Free (2M events a month) | $0 | Free, no time limit |
| 500k events | PostHog free monthly allowance (1M analytics events per product) | $0 within the allowance | Free, monthly |
| 5M events | Mixpanel Growth (up to 20M monthly events) | $140 a month, or $120 a month | Monthly, or billed annually |
| 5M events | Amplitude Plus (first 2M events free, scales to 70M) | Pricing on request for volume above 2M | Self-serve |
| 5M events | PostHog pay-as-you-go | Pricing on request | Usage-based |
| 10k sessions | Heap Free (up to 10k monthly sessions) | $0 | Free |
| 30k sessions | Fullstory Free (30,000 monthly sessions) | $0 | Free, up to 10 users |
The arithmetic for the Mixpanel Growth plan is simple. Billed monthly, 12 × $140 = $1,680 a year. Billed annually, 12 × $120 = $1,440 a year, a saving of $240 a year. At 20M events, the top of the Growth range, the monthly price stays at $140 a month on the published terms, so teams that expect to grow toward that figure should model the annual option first.
Which tool to pick for your situation
The right tool depends on the question you need answered first. The decision table below starts from that question.
| If you need | Pick | Because |
|---|---|---|
| A zero-cost start with funnels and cohorts | Mixpanel Free | The free plan covers up to 1M monthly events, enough to build and validate a tracking plan |
| Analysis of behavior you did not instrument | Heap | Auto-capture records interactions once installed, and virtual events can be defined afterward |
| Analytics, replay, flags and experiments in one tool | PostHog | The products share one platform, with a free monthly allowance on each and self-hosting available |
| Behavioral cohorts and experimentation at larger scale | Amplitude | Behavioral cohorts and experimentation are its core strengths, and it scales to 70M events on Plus |
| Replay as the first tool that developers and support reach for | Fullstory | Its free plan starts with session replay and debugging for up to 30,000 monthly sessions |
| Analytics that drive in-app guides and surveys | Pendo | Guides, replay and surveys are packaged with analytics, but pricing is on request |
Five questions to settle before you buy
- Who will own the tool? A tool that only an engineer can change will get stale. A tool that analysts can query without help will get used.
- How many events does one active account produce in a month? Multiply that by your expected account count to estimate the volume before you read any price list.
- Do you need replay, experiments or in-app guides in the same tool? Bundling reduces the number of contracts, but it can raise the price of the plan you need.
- How long must data be kept? Retention differs across free and paid plans. Check it against the cohort window you chose earlier.
- How easily can you export your data? Export matters if you ever move tools. Ask the vendor how raw event data can be extracted before you commit.
Setup and migration checklist
Whether you are installing a tool for the first time or moving from one to another, the work is mostly in the plan, not the SDK. The checklist below keeps the migration focused on the events and accounts you will actually use.
| Step | What to do | Done when |
|---|---|---|
| 1. Write the tracking plan | List 10 to 15 core events, the user properties and the account properties they need, with a naming convention | Every event has an owner and a business question it answers |
| 2. Map users to accounts | Choose one account identifier and send it with every identified event | Any event can be traced to a company |
| 3. Estimate volume | Count events per active account per month and multiply by the number of accounts | You know which plan band applies |
| 4. Migrate history deliberately | Export the events you still need from the old tool and decide which historical windows to keep | Cohort history is continuous across the switch, or the break is documented |
| 5. Validate in a staging environment | Fire each event with test accounts and check identity, properties and account mapping | Each core event appears once, with the right account and role |
| 6. Build the first reports | Create one activation funnel, one retention cohort view and one account-level health view | The three reports answer the questions from your tracking plan |
| 7. Set a review cadence | Review event volume and dashboards monthly, and retire events nobody uses | Volume and cost stay within the plan you expected |
Event tracking practices that hold up
Start small and name things consistently
Ten to fifteen core events are enough for the first quarter. Use a consistent verb-object pattern, such as "workflow completed" or "seat invited", and record the feature and role as properties rather than as separate event names. Cleaning up a tracking plan with hundreds of near-duplicate events is slow and expensive, so the discipline pays off early.
Track outcomes, not just activity
Page views, clicks and time in app are easy to count and hard to act on. Prefer events that describe progress: a project created, an integration connected, a report shared with a colleague, a seat added. These events line up with activation and expansion, which are the outcomes a B2B team is paid for.
Segment behavior before you automate
Useful segments are usually simple: accounts that completed onboarding against those that did not, active accounts against accounts whose activity is falling, free accounts that reached a plan limit against accounts that have not. Build these segments in your analytics tool first, check that they make sense, and only then connect them to outreach.
Connecting analytics to account-level messages
Product data is most useful when it changes what a person receives. Most analytics tools can send events or segment membership to an email platform, a CRM or a customer success tool. The messages that tend to work best are specific to what the account did or did not do:
- Trial accounts that have not reached activation receive onboarding steps tied to the first action they skipped.
- Accounts whose weekly activity has dropped receive a check-in addressed to the account owner, with a link to the feature they used most before the drop.
- Accounts approaching a plan limit receive plan information that explains the options, without pressure.
- New accounts that reach the aha moment receive an advanced tip that builds on what they already did.
Send these from the same account-level data you use for reporting, so the reports and the messages agree. Keep the number of triggers small at first and read the replies before you add more.
Related Resources
Frequently Asked Questions
What is the difference between product analytics and web analytics?
Web analytics focuses on page views, traffic sources and conversions on a website. Product analytics focuses on what users do inside the application, such as completing a workflow, adding a seat or using a feature. For a SaaS product, the second set of questions is usually the more useful one.
Which tool should an early-stage B2B SaaS team start with?
Mixpanel is a sensible starting point because its free plan covers up to 1M monthly events and its event model fits most SaaS products. Heap suits teams with limited engineering time, and PostHog suits teams that want analytics, replay and feature flags in one tool, or that need self-hosting.
How many events should I track at the start?
Start with 10 to 15 core events: signup, activation, the key feature actions, upgrade, downgrade and cancellation. Add the events that describe your product's aha moment only after you have checked that they connect to activation or retention.
How do I know if I have product-market fit using analytics?
Look at cohort retention curves and activation rates over time, and compare newer cohorts with older ones. If retention is flattening and newer cohorts activate at a higher rate than earlier ones, the product is moving in the right direction. A fixed retention threshold can be a starting point, but it should be tested against your own history.
How much does product analytics software cost for a B2B SaaS company?
It depends on volume. Mixpanel's free plan covers up to 1M monthly events, and its Growth plan is $140 a month, or $120 a month billed annually, for up to 20M monthly events. Amplitude's free plan covers 2M events a month. Heap's free plan covers up to 10k monthly sessions, and Fullstory's covers 30,000 monthly sessions. Amplitude Plus above 2M events, PostHog's pay-as-you-go usage, and the Fullstory, Heap and Pendo paid tiers are priced on request.
What is the difference between Mixpanel, Amplitude and Heap?
Mixpanel is event-based and strong on funnels and cohorts. Amplitude goes deeper into behavioral cohorts and experiments, and scales to larger volumes. Heap records interactions automatically, so you can analyze behavior you did not instrument in advance, but it needs careful event naming to keep the data usable.
Can product analytics data drive email messages to customers?
Yes. Most analytics tools can send events or segment membership to an email platform, a CRM or a customer success tool. Keep the first triggers simple, such as onboarding messages for accounts that have not activated or check-ins for accounts whose activity has dropped, and review replies before adding more.