Mixpanel + Kite

Kite reads your Mixpanel funnels, flows, retention, and saved reports to find where users drop out and which campaigns bring people who stay, then builds the cohorts, experiments, dashboards, and tracking fixes that act on what it finds.

mixpanel.com · analytics · OAuth

Key Takeaways

  1. Kite reads your Mixpanel project to find where users drop out of your funnels, which paths they take instead, and which campaigns bring in people who keep coming back.
  2. Kite also works inside Mixpanel. It saves cohorts, sets up and reads experiments, builds dashboards, and cleans up messy event names and descriptions so your reports stay accurate.
  3. Kite works from the definitions your team already trusts. It reads your saved reports, saved metrics, and the notes your team wrote in Mixpanel about what your events mean.
  4. You connect your own Mixpanel account through OAuth and choose the project Kite works in. Websites that Kite builds and hosts come with their own analytics, so they don't need Mixpanel.

Capabilities verified October 9, 2026.

On this page

What Mixpanel is and how Kite uses it

Mixpanel is a product analytics platform that records what people do in your app or on your website as events, such as a signup, a trial started, or a project created. Teams use it to answer questions about behavior over time: which steps of a journey people complete, where they go instead, and whether they come back next week. An AI marketing agent uses Mixpanel to connect marketing to those answers. It finds the step where new users stall, works out which campaigns bring in users who stick, and then measures whether the change it made moved the number.

Kite does that work in your own Mixpanel project. It queries your funnels and retention, saves the audiences and dashboards your team needs, and runs experiments when a fix needs testing. You connect your Mixpanel account through OAuth.

Marketing jobs Kite can do with Mixpanel

Mixpanel holds the record of what people do after they arrive, so Kite's work with it runs from reading that record to acting on it. The jobs below start with your current numbers, move through diagnosing a drop-off and judging which channels pay off, and end with testing fixes and keeping the data clean enough to trust.

Read your growth numbers the way your team already defines them

Kite starts with the reports and definitions your team has already built in Mixpanel. It searches your project for saved reports, dashboards, and metrics, and it reads the results of the ones that matter, such as a weekly active users chart or a signup report someone pinned months ago. It also reads the business context your team saved in Mixpanel, the short notes that explain what an event like "Activated" means at your company.

That context matters because event names are rarely self-explanatory. If your team counts an account as activated once it invites a second teammate, Kite uses that definition instead of guessing from the name. From there it runs fresh queries on the same events, such as signups by week broken down by UTM source, and writes up what changed and why it matters in Slack. You can ask for that readout once or have Kite deliver it every Monday.

Find the step where users drop out of a funnel

Kite builds funnels from the events you already track to find the exact step where people give up. A typical funnel might run from a pricing page view, to a "Start free trial" click, to a completed signup, to a first project created. Kite reads the conversion rate at each step and splits it by properties such as device, plan, country, or campaign, so it can tell you that the drop is mostly mobile visitors from one paid campaign rather than everyone.

Flows show where people go instead. Kite reads the most common paths before and after a step, such as the pages people visit right before they cancel or where they wander when they leave a signup form half finished. When session replay is on in your project, Kite also reads the replays recorded for specific people, along with the events that happened during each one. That combination usually turns "signups dropped" into a specific cause Kite can propose fixing.

See which campaigns bring in users who stay

A campaign that brings in signups who never return costs more than it looks like, and Mixpanel's retention data is where that shows up. Kite runs retention queries grouped by acquisition source or campaign to see what share of each channel's signups come back in the weeks that follow. It also measures how long people take to get from first visit to activation for each campaign.

Here's how that plays out. Say a LinkedIn campaign and a Google search campaign each brought in 200 signups last month. If 40 percent of the search signups are still active four weeks later and only 10 percent of the LinkedIn signups are, Kite flags that gap. It then recommends where to shift effort, and it can turn that finding into a landing page, an email, or a change to the campaign itself through your other connected tools.

To make those reports readable, Kite can build a lookup table in Mixpanel that maps campaign IDs to campaign names. It can also create formula-based custom properties, such as a plan tier calculated from raw billing fields, so a breakdown reads in the terms your team uses.

Save the audiences your team wants to reach

Kite builds Mixpanel cohorts, which are saved groups of users defined by what they did or who they are. One example is everyone who viewed the pricing page at least twice in the last 14 days without starting a trial. Another is everyone who activated last quarter and hasn't logged in for 30 days. Kite can also update a cohort's definition as your criteria change, or remove one your team no longer uses.

A cohort gives the rest of the work a precise audience. Kite uses it to break down funnels and retention, so it can compare the people who stalled with the people who didn't. Your team can also use the cohort anywhere Mixpanel lets you use one, including cohort syncs you've already set up to your email or ad tools.

Test a fix with a Mixpanel experiment

Once Kite knows which step to fix, it can test the fix as a Mixpanel experiment. Before it sets anything up, it searches your project for earlier experiments on the same feature or metric, so your team learns from the last test instead of repeating it. Then it writes the hypothesis, picks the primary metric, and creates the experiment as a draft. Before launch, it checks the setup against Mixpanel's pre-launch checks, including whether your expected traffic can reach the sample size the test needs.

Kite brings that setup to you in Slack, and launches the experiment once you approve. While the test runs, it reads the lift, confidence interval, and significance for each metric. It also checks whether the traffic split has drifted from what was configured, which would make the results unreliable. When the test ends, Kite recommends shipping the winner or ending without shipping, and it records the decision in Mixpanel.

Mixpanel decides who sees which version, and your product shows that version by checking the experiment's feature flag. Kite can create and update those flags too, including rolling a feature out to a growing percentage of users or switching it off.

Keep your event data clean enough to trust

Tracking plans get messy as teams grow, and a funnel built on the wrong event gives the wrong answer. Kite reads the data quality issues Mixpanel finds in your project, such as a property that suddenly arrives as the wrong type. It also finds groups of near-duplicate names, like "Add to Cart," "add_to_cart," and "addToCart," and proposes merging them into one. A merge can be undone from Mixpanel if your team changes its mind.

Kite also maintains Lexicon, Mixpanel's data dictionary. It writes descriptions and display names for events that have none, marks the events your team should rely on as verified, hides or deprecates ones that are no longer used, and flags properties that hold personal information. It organizes events with tags and can update up to 50 events or properties at a time. Kite can also save a shared metric, such as "Marketing qualified signup," so every later report and experiment uses one definition.

Build the dashboards your team checks

Kite builds Mixpanel dashboards that combine reports with short text explanations, so your team can open one board and understand the numbers. It can create a dashboard from scratch, add or remove reports on an existing one, or copy a dashboard as the starting point for a new launch. A launch dashboard might hold the signup funnel, retention for users who arrived that week, and a note on what Kite changed and when.

Kite can also bring Mixpanel numbers into a dashboard it publishes itself. That dashboard can combine live Mixpanel charts with research and results from your other tools at one stable link, and it refreshes the data when someone opens it.

What Kite reads and changes in Mixpanel

Information Kite can read

  • Projects and business contextThe projects your account can see and the notes your team saved about what your events and terms mean. Kite reads these first so it queries the right project with the right definitions.
  • Events and propertiesEvent names, descriptions, tags, property values, and which events are verified or hidden. These give Kite the exact names it needs for an accurate query.
  • Insights, funnels, flows, and retentionEvent trends, step-by-step conversion, common paths, and how many users return over time, broken down by any property you track. These tell Kite where to focus.
  • Saved reports, metrics, and dashboardsThe reports and metric definitions your team already uses. Kite builds on these rather than redefining your numbers.
  • CohortsEach cohort's definition and description. Kite uses them to compare groups of users.
  • Session replay dataThe replays recorded for a person and the events during each one. Kite uses these to explain a drop-off.
  • Experiments and feature flagsEach experiment's setup, metrics, live results, and health checks, plus each flag's rollout rules. Kite reads these to recommend what to ship.
  • Data quality issuesProblems Mixpanel has detected in your incoming events and groups of duplicate names. Kite checks these before trusting a sudden change in a chart.

Information Kite can create or change

  • CohortsKite creates cohorts, changes their definitions, and deletes ones your team no longer needs.
  • Experiments and feature flagsKite creates draft experiments, launches them after approval, concludes them, and records the decision. It creates flags and changes their rollout.
  • DashboardsKite creates, updates, copies, and deletes dashboards and the text cards on them.
  • Saved metrics, custom properties, and lookup tablesKite saves shared metric definitions, creates formula-based properties, and maps IDs to readable names.
  • Lexicon entries and tagsKite writes descriptions and display names, marks events as verified, hidden, or deprecated, flags sensitive properties, and creates, renames, or deletes tags.
  • Duplicate names and data quality issuesKite merges duplicate events or properties into one name and dismisses issues your team has resolved.
  • Business contextKite updates the notes that explain your events, such as recording what your team counts as a qualified signup.

How Kite connects to Mixpanel

Connect your Mixpanel account through OAuth by signing in to Mixpanel from Kite. Kite then works with the projects and permissions available to that account. If your organization has more than one project, such as one for your marketing site and one for your product, Kite asks which one to use. You can start with a question like "why did trial signups drop last week?" and Kite looks up the project, its business context, and the exact event names, then runs the queries and comes back with what it found.

This connection is separate from the analytics built into Kite. A website Kite builds and hosts records its traffic and conversions in Kite's own analytics. Connect Mixpanel when your product or website already sends its events there.

Playbooks using Mixpanel

  • How to find where users drop out of a Mixpanel funnelKite builds the funnel from your Mixpanel events, splits each step by device, plan, and campaign to find who is dropping out, reads the paths they take instead, and proposes the first change to make.Coming soon

Where Mixpanel fits in Kite's marketing work

Review and approval

Kite proposes work by default. A team approves it with a reply in the Slack thread or the Approve button on a proposed plan. Teams that want Kite to act first can turn that on. In Mixpanel, Kite brings an experiment's setup to you before launch and asks again before it ships a winner. It also confirms with you before it deletes a cohort or dashboard, merges duplicate events, or rewrites your project's business context. Running queries and reports and building new dashboards are part of the analysis, so Kite does those on its own.

Limits and product-specific details

  • Kite reads the events your product sends. Mixpanel holds the data your own app or website records. Kite works with that data and doesn't add new events to your project, so a step your product doesn't track yet needs tracking added in your code first.
  • Some features depend on your Mixpanel plan. Mixpanel's free plan doesn't include saved cohorts, custom properties, or lookup tables. Kite's queries, funnels, and reports work on any plan.

Common questions

Should I connect Mixpanel or Google Analytics?

Connect the one where your conversion events live, and connect both if you use both. Google Analytics is usually where website traffic and sources are measured, while Mixpanel usually holds what people do inside your product after they sign up. Kite can read both, so it can follow a visitor from the campaign that brought them to whether they activated. The Google Analytics + Kite page covers what Kite does there.

How does Kite pick which Mixpanel events to use?

Kite looks up the exact event and property names in your project before it writes a query, so "signup" becomes the "Sign Up Completed" event your product actually sends. When your team has saved metrics, Kite prefers the ones marked as verified. When a chart moves sharply, it checks Mixpanel's data quality issues for that event before reporting the change.

Questions this page answers

  • What can Kite do with Mixpanel?

Related use cases

Related how-tos

1 more coming soon
  • Find where users drop out of a mixpanel funnel

About the author

Devon Wells leads product marketing at Kite, the AI marketer in your Slack. He spent a decade marketing industrial AI, from self-driving trucks to computer vision, but now Kite handles most of the work itself.

Tell me your goal and I’ll get to work.

Add Kite to Slack