Brandable/Mixpanel

Mixpanel: measuring what users really do

Which features keep customers and where do they drop off? What Mixpanel does, when to choose it and how to set it up.

Brandable·Eindhoven

Mixpanel is an analytics tool that measures what users do in your product, app or website: which features they use, where they drop off in a process and whether they come back. Where GA4 mainly looks at traffic and channels, Mixpanel looks at behaviour and users over time, regardless of where they came from. It's popular with SaaS companies, apps and platforms with a login, where the question isn't "how many visitors" but "do people actually use this product, and do they keep using it".

The idea behind Mixpanel is event-based tracking: not pages and sessions as the unit, but actions. A user clicks "Create project", sends an invite, exports a report. Each action is an event, with properties attached (who, when, on which plan, from which device). That structure lets you answer questions a traffic report never can: what percentage of new users does something specific within the first week, and do they stay customers longer than people who didn't?

What Mixpanel does

Mixpanel is built from several report types that all work on the same events, but answer a different question.

ReportQuestion it answers
InsightsHow often does something happen, per day, segment or property?
FunnelsWhere do users drop off in a series of steps, like onboarding or checkout?
FlowsWhich paths do users take before and after an action?
RetentionDo users return after week 1, 4, 12?
CohortsHow does a group behave that started in the same period or did the same thing?
Impact (formerly Signal)What effect does a feature or action have on later retention or revenue?
Session replayWhat a session looks like on screen (in newer plans)

A concrete example: a SaaS company selling project management software builds a funnel of "account created" → "first project created" → "team member invited" → "first task completed". If a lot of people drop off between step two and three, it's worth checking whether inviting is unclear, or people don't yet see the point. That's different from knowing the onboarding page has a high bounce rate: you see the behaviour, not just the page visit.

When to choose Mixpanel (and when GA4)

The answer depends on the question you're trying to answer: is it about who comes in, or about what they do once they're inside?

SituationBetter
Marketing site, you want to know which channels bring leadsGA4
Web shop, focus on traffic, campaigns and revenue per channelGA4 (possibly with Triple Whale)
SaaS or app, you want to know which features keep customersMixpanel
Improving onboarding and activationMixpanel
Churn and retention per user groupMixpanel
A/B testing a new flow inside the productMixpanel (with experimentation features)

Many companies use both: GA4 for marketing and acquisition, Mixpanel for the product itself, after the first login. A web shop typically gets little out of Mixpanel, unless there's an account-driven part like a subscription service or customer portal. A local service business without a login-based product usually doesn't need Mixpanel: GA4 and a well set up measuring online marketing approach are enough.

Free vs. paid: what's where

Mixpanel offers a free plan up to a certain number of "tracked users" or events per month, and paid plans (Growth, Enterprise) above that.

Plan (roughly, check current terms)Suited for
FreeSmall projects, testing whether Mixpanel fits, early-stage products with few users
GrowthGrowing products needing more volume, longer data retention and more reports
EnterpriseLarger organisations needing SSO, more admin controls, support and guarantees

What's usually included for free: the core reports (Insights, Funnels, Retention), a limited number of monthly tracked users, and limited data retention. What you typically get with paid plans: longer retention periods, more users, more advanced analysis such as Impact reports, group analytics and more admin and permission structure for larger teams. Check the current pricing and limits on mixpanel.com, since they scale with the number of users or events and change regularly.

Setting it up well

  1. Start with questions, not events. What do you want to know about activation, usage and retention? Without that question you track randomly and end up with a pile of data and no answer.
  2. Write a tracking plan. A document listing events ("Account created", "Project shared", "Export downloaded") and properties (plan, source, team size, role). Don't leave this to a developer alone: marketing and product should help decide what matters.
  3. Name consistently. Pick one style (for example "Verb + Object", like "Project Created") and stick to it. Without agreement you'll end up with five variants of the same event within months, like "project_created", "Project Created" and "New project", side by side.
  4. Identify users. Identify users after login with a stable ID, so you can link their behaviour across laptop and phone instead of seeing two separate anonymous visitors.
  5. Find your 'aha moment'. Which action in the first few days predicts that someone stays a customer? For a project tool that might be: inviting a second team member within 48 hours. Point onboarding communication at it.
  6. Build funnels around real decision points, not every possible click. A twenty-step funnel is unreadable; pick the steps that actually matter.
  7. Watch retention, not just counts. Lots of sign-ups without returning usage is a vanity metric: it looks good in a report but says little about the health of your product.
  8. Set up access and permissions properly. Not everyone on the team needs to see raw user data; decide who can view and edit which reports.

Common mistakes

  • Tracking everything, without a plan. You end up with hundreds of events nobody fully understands anymore, and a dashboard nobody trusts.
  • No clear owner. A tracking plan without an owner drifts: new features get events with different names, and old events sit unused.
  • Building funnels without a hypothesis. You build a funnel "because you can", with no idea what you'll do once a drop-off point shows up.
  • Forgetting that analysis isn't action. A clear funnel only helps once someone on the team picks up the finding, tests a change and feeds the result back into Mixpanel.
  • Overlooking privacy. User-level tracking quickly touches personal data; without thinking through what you record and why, you run a compliance risk.

How it works with other tools

Mixpanel rarely stands alone. It connects to data sources through a CDP like Segment or RudderStack, so events from multiple places (website, app, backend) come together in one spot. For marketing attribution and ad data it's often combined with GA4 or a tool like Triple Whale. For qualitative insight alongside the numbers, pair it with Hotjar or Microsoft Clarity: Mixpanel shows that people drop off at a step, a session recording shows why. For email and lifecycle marketing, Mixpanel segments are often piped into tools like Customer.io or Braze, so you can automatically trigger relevant emails or in-app messages based on behaviour, such as reaching (or not reaching) an aha moment.

When you don't need Mixpanel

  • You don't have a product with a login or repeat usage: a brochure website or one-off purchase web shop gets little from per-user behaviour analysis.
  • Your team doesn't have the capacity to maintain a tracking plan. Mixpanel without upkeep turns into a messy dataset nobody trusts within a year.
  • You don't yet have a meaningful number of users. With a handful of users a month, you might as well talk to customers directly; a funnel with ten data points says little statistically.
  • You're primarily after marketing attribution and channel reporting. Then GA4, possibly supplemented with server-side tracking, is a more logical starting point.

What to watch

  • Privacy and GDPR. You often measure at user level. Record which data you collect and why, and choose EU data storage (Mixpanel offers EU data residency). This isn't legal advice, but something worth discussing early with a lawyer or privacy officer, especially if you record sensitive user data.
  • Tracking mess. Without a tracking plan and owner, your data gets polluted fast, and you can't fix that with a filter afterwards.
  • Costs as you grow. Pricing scales with events or users. Measure deliberately: not every click needs to be an event.
  • Analysis isn't action. A nice funnel only helps if someone picks up and tests the improvement.
  • Learning curve. Mixpanel is more powerful, but also less plug-and-play than GA4. Budget time for explanation and training for everyone who'll work with it.

Alternatives

Amplitude is similar and strong in product analytics, with a comparable setup around events and funnels. PostHog is open source, can be self-hosted, and combines analytics with feature flags and session replays in one tool. Heap automatically captures all events without requiring you to define everything upfront, which gets you started faster but can get messy just as fast. GA4 remains the obvious choice for marketing questions about traffic and channels. For behaviour on screen, alongside the numbers: Hotjar or Microsoft Clarity.

Frequently asked questions about Mixpanel

What is Mixpanel?

A product analytics tool measuring what users do in your app or website, such as feature usage, drop-off points and return visits, based on events rather than page views.

Is Mixpanel free?

Yes, up to a certain number of users or events per month. Above that and for extra features, such as longer data retention and more advanced reports, you pay. Check current terms on mixpanel.com.

What's the difference between Mixpanel and Google Analytics?

GA4 is strong in traffic, channels and campaigns: where visitors come from. Mixpanel is strong in user behaviour, funnels and retention within a product: what users do once they're inside.

Is Mixpanel GDPR compliant?

Mixpanel offers EU data storage and privacy settings, but you decide which data you collect and whether you need consent. If in doubt, discuss this with a lawyer or privacy officer.

Do I need a developer?

Usually yes for a good implementation: events must be added in code or via an integration (like a CDP) and kept consistent.

Does Mixpanel work for a web shop?

To a limited extent. Mixpanel is stronger when customers log in and do something repeatedly, like with a subscription or customer portal. For a regular web shop, GA4, possibly paired with a tool like Triple Whale, is usually a more logical starting point.

How long before you get useful insights?

That depends on how many users you have and how quickly your tracking plan is in place. With too little data per segment, funnels and cohorts aren't reliable yet; expect several weeks to months of collected data before patterns become clear.

Can I combine Mixpanel with GA4?

Yes, and that's common: GA4 for marketing and acquisition, Mixpanel for behaviour after the first login. They answer different questions and overlap little.

Further reading

Want to know more about measuring and keeping customers? Read measuring online marketing and churn. Want to look at what you should measure together? Book a free strategy session.

Questions, or just want to spar?

We're happy to think along — call, email or drop by in the heart of Eindhoven.

Ask your question →