“A teammate asked how they managed build funnels that accurately capture user journeys from signup to activation to retention. They started explaining and realized every step ran through mixpanel. Specifically, custom event properties for behavioral segmentation had become load-bearing.”
When I'm the pm asks: "what percentage of users who complete onboarding become weekly act, I want to build funnels that accurately capture user journeys from signup to activation to retention, so I can create retention analyses that identify which behaviors predict long-term engagement.
A product analyst or data analyst embedded in a product team who uses Mixpanel as their primary tool for understanding user behavior. They build funnels, analyze retention, and create the dashboards that PMs reference in every planning meeting. They know SQL but prefer Mixpanel's UI for speed. They've named every event in the tracking plan and written documentation for each one. They are the person the PM turns to and asks "are users actually using this feature?" — and they always have the answer.
To build funnels that accurately capture user journeys from signup to activation to retention — reliably, without workarounds, and without becoming the team's single point of failure for mixpanel, leveraging funnel analysis with step-by-step conversion tracking.
A product analyst or data analyst embedded in a product team who trusts their setup. Build funnels that accurately capture user journeys from signup to activation to retention is reliable enough that they've stopped checking. Event governance tools that flag naming inconsistencies and undocumented properties at ingestion time prevent data quality issues. They've moved from configuring mixpanel to using it.
The PM asks: "What percentage of users who complete onboarding become weekly active users within 30 days?" The analyst opens Mixpanel, builds a funnel from signup to onboarding completion, then creates a retention chart cohorted by onboarding completion week. The data shows 45% retention — but they notice the "onboarding_completed" event was being fired on a page load, not on actual completion. One engineering team shipped a change two weeks ago. The analyst now needs to re-define the event, coordinate with engineering, backfill the data, and re-run the analysis. The PM's question took 3 hours to answer correctly instead of 15 minutes.
Uses Mixpanel 4–8 hours per day as their primary analytics tool. Maintains 10–30 saved reports and dashboards. Manages a tracking plan with 50–200 events and 100–500 properties. Works closely with 2–5 product managers and coordinates with engineering on tracking implementation. Creates ad-hoc analyses 3–5 times per week in addition to maintaining standard dashboards. Has a Mixpanel governance process for adding new events. Uses Mixpanel's JQL or custom queries for complex analyses that the UI can't handle.
Two things you'd notice: they reference mixpanel in conversation without being asked, and they've built workflows on top of it that weren't in the original plan. funnel analysis with step-by-step conversion tracking has become part of their muscle memory. They're now focused on create retention analyses that identify which behaviors predict long-term engagement — a sign the basics are solved.
It's not one thing — it's the accumulation. Data accuracy issues — duplicate users created despite identity merge being enabled that they've reported, worked around, and accepted. Then a competitor demo shows the same workflow without the friction, and the sunk cost argument collapses. Their worldview — data without context is just numbers — the analyst's job is to turn data into a story — makes them unwilling to compromise once a better option is visible.
Pairs with mixpanel-primary-user for the PM-using-analytics vs. analyst-driving-analytics perspective. Contrast with amplitude-primary-user for the product analytics platform comparison. Use with posthog-primary-user for the open-source analytics alternative.