How to Choose Your SaaS Value Metric: Why Mixpanel Switched from Users to Events (and Why It Matters for Your Pricing)

The Wrong Metric Will Tank Your Net Revenue Retention

Every SaaS pricing decision comes down to one question: what are you charging for? The answer shapes everything—whether customers feel cheated on renewals, whether you hit your quota, whether your best users stay or leave.

The metric you pick is not your pricing model. It's not whether you charge per month or per year. It's not your tier structure. It's the specific thing your customer sees on the invoice and thinks: That makes sense, or it doesn't.

Mixpanel switched from monthly tracked users (MTU) to event-based pricing in February 2026, and the move illustrates why choosing the right value metric is a strategic decision that most SaaS companies get wrong on the first try.

What Mixpanel Was Doing Before (And Why It Failed)

For years, Mixpanel charged based on monthly tracked users—the number of unique users who trigger events in your product each month. This sounds rational: users are easy to count, stable to forecast, and predictable for customers.

The problem is mathematical.

A startup with 50,000 monthly active users triggers millions of events depending on how much you're tracking. A competitor with 100,000 users but lighter tracking might trigger far fewer. Under MTU pricing, the lighter user paid more because they had more accounts. The model taxed headcount while ignoring the actual consumption that drove infrastructure costs.

This created a mismatch. Behavioral economics research documents what practitioners call the pain of paying: when the price is visibly tied to each unit of consumption, buyers ration usage to manage the bill. Customers were incentivized to limit their event tracking to keep bills down—exactly the opposite of what Mixpanel's product was designed to do.

The core value proposition of Mixpanel is comprehensive event instrumentation: track everything, understand user behavior in granular detail. But under MTU pricing, customers heard: "Every new event you track costs you more. Be careful what you measure."

The Switch: From Users to Events

Mixpanel's new event-based pricing includes 20 million events per month free and the most affordable Growth plan on the market, going up to 300M events a month. Pricing is free up to 1M events, then $2,520/month at 10M and $5,320 at 20M—plus paid add-ons for session replay, feature flags, and account analytics.

The shift is elegant because it reframes what Mixpanel is selling. The company isn't selling "access for 50,000 users." It's selling "the ability to instrument and analyze 20 million events per month." A team that wants comprehensive product analytics can now scale their instrumentation without penalty. The metric moved closer to actual value: how much behavioral data are you capturing and analyzing?

More importantly, Mixpanel unveiled the most generous free plan on the market, including 20M events per month, and the most affordable Growth plan on the market, going up to 300M events a month, signaling a deliberate choice to reduce friction at entry and scale. When the pricing metric aligns with how customers actually use the product, expansion revenue follows naturally. Mixpanel's model rewards intentional tracking: the fewer redundant events you fire, the lower your bill—which pushes customers toward smarter instrumentation practices.

The Three Value Metrics Most SaaS Companies Choose (And When They Break)

Before you redesign your pricing, understand the landscape. Common SaaS pricing models include per-user (e.g., charging for each active editor in a collaboration tool), usage-based (such as the number of invoices processed monthly in billing software), per-feature (like workflows executed in automation platforms), and tiered pricing.

The question is: which one makes your customer's value transfer visible without suppressing adoption?

Per-User Pricing (The Default That Often Doesn't Work)

Per-user pricing is the most common model because it is simple to implement, not because it is optimal. It works if each additional user consistently increases the value delivered. For a communication tool like Slack, it makes sense: more users = more messages, more collaboration, more value.

It breaks when users don't add proportional value. A CRM where 80% of users are read-only viewers, not editors, doesn't benefit from per-user pricing—those read-only seats are overhead, and you've just created an incentive to consolidate access.

Unless each additional user meaningfully increases the value your product delivers, you are capping your revenue growth and giving customers a reason to consolidate seats.

Event-Based or Usage Pricing (Mixpanel's Path)

A mobile app analytics company charged per event tracked. Customers responded rationally: they didn't instrument all their in-app events, even though comprehensive instrumentation was the core value of the technology. The per-event price made full deployment feel expensive relative to the insight each marginal event delivered. The pricing architecture prevented customers from using the product the way it was designed to be used.

This is the trap: event-based pricing can work, but only if the metric sits at the right level of abstraction. Raw event counts feel like taxation. But when you bundle events into tiers—"20M included, then $X per million after"—you smooth out the pain of paying and let customers budget around it.

Outcome-Based Metrics (The Ideal, Rarely Executed)

Outcome-based metrics are the "holy grail" of value-based pricing because they perfectly align your incentives with the customer's. When they make more money, you make more money. However, they can be harder to track and may lead to disputes if the "outcome" is influenced by factors outside your software's control.

A recruitment SaaS that charges per successful hire is outcome-based. A sales platform that charges per deal closed is outcome-based. But attribution is messy, and disputes erode trust fast.

Three Rules for Choosing Your Metric (Before You Ship It)

Criterion	What It Means	Red Flag
Value Alignment	Does the metric grow as customer outcomes improve?	Metric grows from system activity you can't control or customer doesn't perceive as value.
Predictability	Can a prospect estimate their bill before committing?	Customers cannot predict their monthly bill before they commit; metrics like "per API call" or "per event" can feel unpredictable to buyers.
Simplicity	Can a customer point at the invoice and say: "I understand why this number went up"?	Multiple metrics, complex bundling, or hidden add-ons trigger support tickets and churn.

The Metric Matters More Than the Model

Choosing a pricing model is the wrong starting point. The model is downstream of three harder decisions: what metric you charge on (licensing), how you structure what's included (packaging), and what price points hold up in real deals (pricing). Companies that start with the model end up retrofitting everything else to justify the choice they already made.

Mixpanel didn't switch from "per-user" to "usage-based" as abstract models. It switched from a metric that penalized full product adoption (unique users) to one that rewarded it (event volume), and wrapped it in tiers that smooth out customer pain.

For IT and finance decision-makers, the lesson is this: when you're evaluating a new SaaS tool, scrutinize the value metric before you sign. Ask:

• What grows when I get more value? If the metric that matters (events, API calls, storage) is hidden behind a per-seat facade, you're not seeing the real cost curve.
• Can I estimate next year's bill today? If you can't plug in projected usage and get a number, the vendor is avoiding transparency for a reason.
• Does the metric reward or punish adoption? If heavier use of the core feature triggers exponential cost growth, you'll eventually ration usage and lose the tool's value.

Why This Matters Now

Usage-based pricing has become the most common approach for businesses that deliver software via public or private cloud or embedded deployments. As of 2026, 74% of suppliers had adopted usage-based models, and 56% expected usage-based revenue to grow by 2027.

But adoption doesn't mean optimization. Most SaaS companies still choose metrics reactively—"we'll charge per user because everyone else does"—then wonder why renewal conversations are painful.

The companies that get this right know that the metric you select should directly reflect the value your customers derive from your product. Mixpanel's switch to event-based pricing is one example of a vendor course-correcting after realizing the old metric was fighting the product design.

When you're choosing SaaS tools or rethinking your own pricing, start with the metric. Not the list price. Not the tier names. The metric. Because that's what lives on the invoice, and it's what shapes whether customers feel they're getting a deal or being nickeled-and-dimed.