All posts

July 2026 · The Nohmo team

How much does Mixpanel actually cost? A worked calculation

Mixpanel's pricing page opens with "Starts at $0", which is true and tells you almost nothing about what you will pay. The number that matters is further down: $0.28 per 1,000 events beyond the first million each month.

That per-unit price sounds small. The arithmetic is what surprises people.

Figures read from mixpanel.com/pricing in July 2026. Volume discounts are available and Enterprise is negotiated, so treat these as list prices.

The plans

PlanPriceEvents
Free$0Capped at 1M monthly events · 5 saved reports · 10K session replays
GrowthStarts at $01M monthly events free, then $0.28 per 1K events · unlimited reports · 20K replays
EnterpriseCustomUnlimited events, governance, premium support

Mixpanel bills on events, not monthly tracked users. This matters more than it sounds, and it is the crux of the whole thing.

The arithmetic

Monthly eventsBillable eventsList cost
1M0$0
2M1M$280
5M4M$1,120
10M9M$2,520
25M24M$6,720

The jump from free to 2M events is a jump from $0 to $280/month. There is no gentle middle.

What counts as an event

An event is any tracked action. That includes the ones you wrote deliberately — signup_completed, checkout_started — and the ones an SDK sends for you: page views, screen views, session start and end, and in some setups autocaptured clicks and form interactions.

Two things reliably inflate this number without anyone deciding to:

Autocapture. Turn it on and every click becomes an event. It is genuinely useful — it is why you can answer questions you did not plan for — but it multiplies volume by whatever your average clicks-per-session is.

Identity resolution. $identify calls and profile updates are events too. A product that reconciles a user's identity on every page load is billing itself for that.

Worth knowing what does not count: user profile properties are stored, not metered, so enriching profiles is free where firing events is not.

Why event counts grow faster than users

Here is the part teams model wrong. Event volume is not proportional to your user count — it is proportional to user count × how much you instrument.

A single engaged session in a well-instrumented product might fire: a page view, four clicks, a form interaction, a search, two API-driven state changes, a scroll milestone and a conversion. That is ten events for one visit. Ten thousand sessions a month is 100,000 events before you have tracked anything unusual.

Then someone does good work. They add tracking to the onboarding flow to find where people drop off. Event volume doubles. The bill doubles. Nothing about the business changed — you just measured it better.

This is the structural problem with per-event pricing: it taxes instrumentation. The rational response is to track less, which is the opposite of why you bought an analytics tool. Teams end up in review meetings deciding which user behaviour they can afford to know about.

What happens when you exceed the free plan

Worth understanding before you rely on it. The Free plan is capped at 1M monthly events rather than metered — so exceeding it does not generate a surprise invoice, it stops ingesting. That is the safer failure mode of the two, but it means data loss rather than a bill, and the events you drop are gone. You cannot backfill them later.

Growth is the opposite: no cap, and the meter runs. Whichever you are on, set a volume alert well below the threshold. Finding out at month end is the expensive way to learn your event volume doubled.

How to reduce a Mixpanel bill

If you are staying — and at under 1M events/month the free tier is genuinely generous — these work:

  1. Audit for dead events. Most products have events nobody has queried in a year. Mixpanel's Lexicon shows usage; delete what nothing reads.
  2. Stop tracking high-frequency, low-value actions. Scroll depth and mouse-move-style events are the usual offenders.
  3. Batch or debounce noisy client events. One search_performed on submit, not one per keystroke.
  4. Check for double-firing. Duplicate SDK initialisation and React strict-mode double-renders quietly inflate volume.
  5. Ask about volume discounts before you hit a tier — the list price is not the only price.

The alternative model

Flat pricing removes the trade-off entirely: you instrument what is useful, and the bill does not move. That is what we built Nohmo on — $49/month per project, unlimited events, with error monitoring included in the same SDK.

Be honest about the comparison, though. Under 1M events a month, Mixpanel's free tier costs nothing and has more mature analysis features than we do — cohort analysis, advanced segmentation and a genuinely deep query builder. If that is you, use it. Flat pricing starts winning when your event volume is real, or when you are also paying separately for error monitoring.

Summary

  • Mixpanel Growth: 1M events free, then $0.28 per 1,000 events.
  • 5M events/month ≈ $1,120. 10M ≈ $2,520. List prices, before discounts.
  • Event volume scales with instrumentation depth, not just users — so the bill grows when you measure more carefully.
  • Under 1M events, the free tier is hard to beat.