I like how easy it is to use and how intuitive the interface is. Even if you’ve just onboarded, it’s fairly easy to create reports, and there are so many customization options for how the data visualized and ways to get more granular with the data. I’ve been using it for over four years now and I feel like I’ve barely scratched the surface of what’s possible with this tool. Review collected by and hosted on G2.com.

Some parts of the UI can be confusing or disorienting which is partly due to the fact that this system has so many different features. I sometimes get a little lost trying to find my way around, so navigation stands to be improved in my opinion. Review collected by and hosted on G2.com.

I like Mixpanel because the UI is clean and easy to use, which makes it straightforward to track app events and user activity. The dashboard provides useful real-time insights that are especially helpful during testing. Performance is solid, and the data becomes available quickly when I’m checking expected results. The integrations are useful for analytics workflows, and onboarding feels manageable for new users. The AI-based insights also help us understand trends more clearly. Overall, it offers good value by helping us spot issues faster and improve the quality of our testing. Review collected by and hosted on G2.com.

Sometimes Mixpanel can be challenging for new users, since some of the more advanced features take time to learn. The UI is solid overall, but certain reports and filters can still feel confusing at first and require a bit of trial and error to understand. In some cases, performance also feels slow when loading larger reports, which can interrupt the workflow. Pricing may also feel expensive for smaller teams. Better onboarding, along with faster support for technical questions, would make the experience smoother. The AI features are useful, but they could offer more detailed suggestions to help guide next steps. Review collected by and hosted on G2.com.

Mixpanel is always a go-to tool for tracking user analytics. Actions can be customized on the client side, and Mixpanel also takes care of additional data such as device details, the user’s network, and location information. Apart from that the UI is cool and easy conversion to JSON for code level checking of the events is also provided. Review collected by and hosted on G2.com.

The time it takes for event updates to appear isn’t consistent. Sometimes an event reflects within about a minute, and other times it takes more than 2–3 minutes. Review collected by and hosted on G2.com.

I use Mixpanel for product event tracking across our web and mobile apps. The SDKs are lightweight and easy to integrate, and the tracking API is simple: one call with an event name and properties. Funnels, retention, and cohort reports are quick to build without SQL, so PMs and developers can answer questions themselves and spend less time on ad hoc queries. Live View and the event debugger let me check event names and properties from a local build in seconds during development or QA. That shortens our feedback loop, keeps tracking data clean, and helps make the funnels and reports PMs rely on accurate. I also get quick post-release visibility, can isolate drop-offs by properties like app version or platform, and can validate A/B experiments. The data export and raw API let us pull data into our own pipelines when needed. Setup was fairly easy: installing the SDK and sending the first events took under a day, and the docs and quickstart guides are clear. Once we had identity management set up, it was stable. Mixpanel is a strong, developer-friendly product analytics tool with easy SDKs and fast self-serve reporting. Review collected by and hosted on G2.com.

I find event governance gets messy at scale: duplicate or inconsistently named events pile up, and Lexicon cleanup is manual. Pricing climbs quickly as event volume grows. Complex analysis beyond standard reports still needs a data warehouse export. When I pull large date ranges through the export or query APIs, I have to add my own batching and retry logic to stay within rate limits. Some advanced endpoint docs lack full request and response examples for edge cases. Planning a clean tracking plan took effort, and getting ID merge right took some testing. Review collected by and hosted on G2.com.

What I like best about Mixpanel is how it lets us dig into our lead and policyholder behavior without leaning on our outside dev contractor every single time. I’m Hans Isip, Operations & Business Systems Coordinator at Mountain Peak Insurance Advisors out in Denver. We’re an independent insurance agency with 11–50 people, and I spend most days testing tools, building workflows, locking down permissions, troubleshooting integrations, and walking our agents, service staff, and accounting team through new systems. We use Mixpanel mainly to track how people move through our website, our self-service quote flow, and the supplemental insurance storefront we run for add-on policies. Before Mixpanel, all we really had was basic Google Analytics data. It could tell us how many people landed on our quote page, but it couldn’t tell us where they dropped off inside that multi-step quoting process, or whether someone who started a quote later picked up a policy renewal email from our marketing sequence.

The cohort analysis is the standout feature for our agency work. A couple months ago, our sales team noticed a lot of people starting auto insurance quotes but never finishing them. We had no clue which step was scaring them off. I built a cohort in Mixpanel grouped by quote start date, then tracked them through each form stage: entering vehicle info, adding driver details, reviewing coverage options, submitting for agent follow-up. It quickly showed the majority were bailing on the coverage selection screen. It turned out the page was showing way too many optional endorsements all at once, which overwhelmed shoppers new to insurance terminology. We simplified that view, trimmed down the add-on options shown by default, and added a short plain-language tooltip for the critical coverages. Within a month, our quote completion rate ticked up nicely, and our agents got fewer calls from confused prospects asking to walk them through every single optional add-on. That change came straight from what I found in Mixpanel.

I also like how flexible the event setup is. I can tag custom events for things like downloading our coverage guide, booking an agent consultation, opening a renewal reminder link, or visiting our supplemental product shop. Since we’re heavy on compliance, it helps us separate casual browsers from serious shoppers who are actively engaging with policy-related tools. The dashboards are easy enough for me to build and share. I create a simple weekly view for our sales and marketing lead so they can see which ad sources bring people all the way through to quote submission, not just those who click the ad once and leave immediately.

We rely on role permissions too. I can share read-only dashboards with our marketing lead without letting them edit or delete our tracked events. That keeps our tracking setup consistent and avoids accidental changes that would mess up our trend data, which matters because we use these insights to plan renewal outreach for hundreds of policyholders. Review collected by and hosted on G2.com.

One of the more frustrating roadblocks I deal with regularly in Mixpanel is its limited support for the custom identity logic we need as an insurance agency. I’m Hans Isip, Operations & Business Systems Coordinator at Mountain Peak Insurance Advisors in Denver. My typical workload covers tool rollouts, permission tuning, CSV imports, integration testing, and supporting our agents, client service team and back-office staff. We track prospects moving through our online quote flow, visitors browsing our supplemental insurance store, and existing policyholders engaging with renewal content. A really common scenario for us is that a prospect starts filling out a quote on their cell phone, leaves it unfinished, then returns a few days later from a desktop computer — sometimes entering a different email, or just using their phone number as the main point of contact.

Mixpanel doesn’t handle this cross-device matching cleanly. It defaults to creating separate user profiles for each session unless we have perfect consistent IDs from the start. Not long ago, I was putting together a funnel report for our home insurance quoting flow, and the conversion metrics looked off compared against our CRM records. After digging through dozens of individual profiles, I found that many finished quotes belonged to users who already had an earlier abandoned quote session under a different anonymous ID. There’s no straightforward native rule to auto-match users by phone number, which is our most reliable unique identifier for leads. Manually merging those duplicate records takes forever, and it’s easy to miss a handful of them, which skews our funnel and cohort analysis.

Bulk data uploads bring their own set of headaches too. Each month I export a list of active policyholders from our CRM to enrich Mixpanel profiles with policy details: coverage line, assigned agent, policy effective date, and renewal timeline. Date fields often get misinterpreted during CSV mapping, and multi-value custom attributes like discount eligibility or prior claims history frequently fail to import properly. This matters a lot because we use this linked behavioral data to time our renewal nurture emails. If renewal dates import incorrectly, we risk reaching out to policyholders at the wrong time, which creates confusion and compliance risk for our agency. I’m forced to run a full line-by-line validation on every upload before I can use the dataset. Review collected by and hosted on G2.com.

The ability to investigate user behaviour at a more detailed level is what I find most useful. Instead of treating usage as one overall number, we can look at particular actions and get a better sense of how the product is being used. Review collected by and hosted on G2.com.

There is a fair amount of information available, which means we have to be disciplined about what we choose to examine. Without a clear question in mind, it would be easy to spend time looking at data that doesn't lead anywhere useful. Review collected by and hosted on G2.com.

The most helpful feature was the new Mixpanel AI agent, which allows me to quickly gain valuable insights simply by using prompts. The user experience is very intuitive, and the ability to connect with other analytics platforms makes it even more powerful. The performance is impressively fast. The pricing is also reasonable, offering great value and plenty of benefits. Additionally, the onboarding process was seamless, and the UI is visually appealing. Review collected by and hosted on G2.com.

When the Mixpanel agent generates answers, the webpage sometimes crashes when it’s working with larger datasets. I then have to reload the page, and it becomes very slow afterward. The processing could be optimized to improve stability and performance. Review collected by and hosted on G2.com.

The ability to explore user interactions in more detail is useful. Looking beyond general traffic figures can help teams ask more specific questions about how people engage with a website. Review collected by and hosted on G2.com.

Getting meaningful insights requires some thought upfront. Event tracking needs to be planned carefully, and collecting data alone does not automatically tell you what changes to make. Review collected by and hosted on G2.com.

Nothing new that I like, no new major feature that I use so nothing Review collected by and hosted on G2.com.

AI There is no AI in Mixpanel, for use case like "how do I do that?" nothing. You need to ask Claude or search on the internet. Also no AI to gather information from reports like "What happened yesterday on this dashboard" No AI generated reports Nothing Mixpanel is absolutely not AI enabled. Also Mixpanel MCP is bad with Claude Review collected by and hosted on G2.com.

I really like the new design of dashboard and new brand design overall. Also I started using session replies and those have proven to be very useful in pinpointing circumstances when users are having problems in my projects, and how to resolve them. Review collected by and hosted on G2.com.

From the beginning I have an issue with opening dashboard, not much of an issue, more like small 'error'. The screen for short second displays that I do not have access to the selected dashboard. The first few times I thought this was real issue, but now I know this is just some display issues, hope in the future this could get fixed, for more smooth experience. Review collected by and hosted on G2.com.