Mixpanel + AI: Use Mixpanel Through Juma's AI Workspace
Connect Mixpanel to Juma so the team can pull funnels and retention from chat, build executive dashboards, design and ship A/B experiments end-to-end (with built-in best-practice guidance), manage feature flag rollouts, and pull session replays for the qualitative context behind funnel drops.
.png){kind=icon}
Key takeaways
Yes, Mixpanel works with AI through Juma
Connection runs through Mixpanel's MCP server with the team's API credentials, per teammate. Juma sees the projects, events, dashboards, and experiments your Mixpanel account already accesses.
Pull funnels, retention, and flows from chat
Run the canonical product-analytics queries through Run-Query. Results come back as charts, scorecards, and sortable tables.
Design and ship A/B experiments end-to-end with built-in best-practice guidance
Mixpanel ships setup-guidance and results-interpretation-guidance helpers. Juma calls both at the right moments so the team runs the test correctly without first reading a book about it.
Build executive dashboards in chat
Create, update, duplicate dashboards. The CMO Monday-morning dashboard becomes a recurring Flow that refreshes itself.
Manage feature flag rollouts for growth experiments
Full lifecycle: setup, staged rollout, kill-switch, archival. Gate new pricing pages, signup flows, or activation paths.
400+ marketing teams
Use Juma, including Salesforce, Maersk, Costa Coffee, Wavemaker, and House of Growth. 4.9/5 on G2. House of Growth ships 160 articles a month, saving 85+ hours. Enterprise-grade. SOC 2 Type II, ISO/IEC 27001, GDPR, HIPAA. Unlimited seats on every plan.
Can I access Mixpanel through AI?
MCP is an open standard that lets AI assistants call external tools; Mixpanel joined OpenAI, Anthropic, and others in adopting it. When Mixpanel is connected to Juma, the team uses the same authenticated API access available in Mixpanel's own product. The full Mixpanel surface is reachable: queries (insights, funnels, flows, retention), dashboards, saved metrics, experiments with built-in setup and interpretation guidance, feature flags with lifecycle guidance, session replays, and Lexicon data governance.
The connection runs at the user level. Each teammate authorizes Juma with their own Mixpanel credentials; Juma sees only what that account accesses. Mixpanel data pulled into a Project as persistent knowledge (key funnels, success metrics, prior experiment learnings) lives inside the team's Juma workspace, encrypted AES-256, with zero data retention from any AI provider. Strategy, taste, and judgment stay human: the team reviews every output before it ships, especially for live experiments and customer-facing rollouts.
What can Juma do with Mixpanel?
Through Juma, the team can run the canonical product-analytics queries from chat, build and update executive dashboards, design and ship A/B experiments end-to-end with built-in guidance, manage feature flag rollouts, and pull session replays for qualitative context. Each capability returns a chat response that links back to the underlying entity in Mixpanel, ready to open or share.
01 · Pull funnels, retention
Pull funnels, retention, flows, and insights from chat
Ask Juma to "show me the signup-to-activation funnel for the last 30 days, broken out by acquisition channel." Juma calls Get-Query-Schema to confirm the shape, runs the funnel through Run-Query, and returns an interactive chart with the drop-off per step plus a sortable cohort table. Retention curves, flow visualizations, insights breakdowns: the canonical product-analytics queries that take 15 minutes in the Mixpanel UI land in chat in seconds. Pull saved reports by ID through Get-Report and re-render them when a stakeholder asks.
02 · Build and update
Build and update executive dashboards from chat
Ask Juma to "build a CMO dashboard with weekly active users, signup-to-activation conversion, MRR retention, and top-of-funnel traffic by channel; refresh every Monday at 8am." Juma runs each query, calls Create-Dashboard, and ships a structured dashboard with rows and cells laid out. Use Update-Dashboard to add cards as the team's questions evolve, Duplicate-Dashboard to fork a template for a new client, and List-Dashboards to discover what already exists. The CMO Monday dashboard becomes a recurring Flow that refreshes itself.
03 · Design and ship
Design and ship A/B experiments end-to-end with built-in guidance
The distinctive Mixpanel surface. Before creating an experiment, Juma calls Get-Experiment-Setup-Guidance so the design is sound: variant count, sample size, power, the right primary metric. Then Create-Experiment ships it in DRAFT for review; the team launches through Update-Experiment. When it's time to decide, Juma calls Get-Experiment-Results-Interpretation-Guidance to read results correctly: significance, effect size, segment behavior, the ship/iterate/kill recommendation. Teams without an in-house experimentation expert get a Mixpanel-vetted process baked into chat.
04 · Manage feature flag
Manage feature flag rollouts for marketing experiments
Modern PLG marketing gates new pricing pages, signup flows, and activation paths behind feature flags. Through Juma, the team pulls Get-Feature-Flag-Setup-Guidance before creating a flag, ships it through Create-Feature-Flag, manages staged rollout through Update-Feature-Flag, and calls Get-Feature-Flag-Lifecycle-Guidance to decide when to graduate, archive, or kill it. Feature flag hygiene (especially the archival side, where flags pile up) becomes a chat habit instead of a backlog.
05 · Pull session replays
Pull session replays for qualitative context behind funnel drops
When a funnel shows a drop, the next question is "what are users actually doing on that step?" Ask Juma to "pull session replays for users who dropped at signup step 3 in the last 7 days." Get-User-Replays-Data returns replay metadata for up to 20 sessions, summarized in chat with shared patterns surfaced. The team scans the structured summary and opens specific replays in Mixpanel when they want the recording. Qual context arrives alongside the quant chart in one conversation.
How does Juma + Mixpanel replace your product-analytics stack?
Most B2B SaaS and PLG teams stack Mixpanel for data, plus a product analyst running ad-hoc queries, plus a growth ops person designing experiments, plus a separate dashboard tool (Hex, Mode, Looker) for CMO reporting, plus a session replay tool. With Juma + Mixpanel, Mixpanel stays as the data and experimentation source; Juma replaces most of the analyst, ops, and dashboard layers.
What disappears is the layer between Mixpanel's data and a finished decision: the analyst ticket queue, the dashboard tool the team paid $200 a month for, the meeting where someone explains what experiment results mean. Mixpanel stays as the data source. Juma augments the team on top, with human review on every output. The Crew runs workflows 2x faster with 90% adoption; the same compression lands on Mixpanel-driven growth work.
Funnel events trigger CRM lifecycle and email workflows
Mixpanel tracks the product funnel (signup, activation, engagement, paid, expansion). HubSpot ships lifecycle workflows and email automations. With Juma in between, Mixpanel funnel events trigger HubSpot lifecycle updates and campaigns: when a user crosses an activation threshold, the contact moves to "Activated" and the nurture sequence stops; when a user disengages, they enter a re-engagement campaign; when paid conversion lands, the upsell sequence starts. Mixpanel answers what did the user do? HubSpot answers what message do they get next? The pair answers the weekly PLG question: "what's the right next message based on where this user is in the product?"
Diagnose low-converting pages and ship the fix
Mixpanel funnel and flow data surfaces the pages and steps where users leak: the pricing page that drops 40% of visitors, the signup form where step 3 fails. With Juma, the team pulls the diagnosis from Mixpanel (drop percentage, segment breakdown, session-replay patterns), drafts copy and structural fixes in the project's brand voice (Project Knowledge feeds in the brand guide), runs an AEO/GEO check, and pushes the edit to Webflow CMS as a draft for editorial review. After ship, watch Mixpanel for the change to compound (or not), and iterate. Diagnose, fix, ship in one chat; strategy, taste, and judgment stay human.
How to connect Mixpanel to Juma
Open Integrations
Click your name in the bottom-left corner of Juma, then Integrations.
Find Mixpanel
Under product analytics integrations.
Connect
Paste your Mixpanel API credentials (service account credentials from your Mixpanel project settings). The connection runs at the user level: the projects, events, dashboards, and experiments Juma can see match the access your Mixpanel account already has.
Start using Mixpanel
The integration is now available across every Juma project and chat. Juma will prompt you to use Mixpanel when relevant, or ask directly: "Use Mixpanel to pull the signup-to-activation funnel for the last 30 days, broken out by channel."
Trusted by marketing teams that ship
Customer outcomes
240+ teams
Security & compliance
Questions, answered
Can I use Mixpanel with ChatGPT or Claude instead of Juma?
Yes. Mixpanel's MCP server works with any MCP-compatible AI assistant. What Juma adds for marketing teams: persistent Project Knowledge (brand voice, key funnels, prior experiment learnings remembered per client), multi-tool orchestration across the marketing stack (Mixpanel plus HubSpot, Webflow, GA4, and 700+ Flows), finished marketing deliverables instead of chat responses, and platform-level controls (audit logs, SSO/SAML, SOC 2 Type II). For one user occasionally querying Mixpanel, generic AI works. For a PLG growth team running funnels, experiments, and rollouts across many projects, Project context and tool composition matter.
Does Juma have access to all our Mixpanel events?
Only what your own Mixpanel account already has access to. The integration runs at the user level: when you connect, you authorize Juma with your Mixpanel credentials, and the projects, events, dashboards, experiments, and feature flags Juma can see match the permissions that account already has in Mixpanel. Sensitive events you don't have access to in Mixpanel stay invisible through your Juma connection. Disconnecting revokes access immediately.
Does Juma store our Mixpanel data?
Juma reads Mixpanel on demand, pulling only what a specific question or task needs. Content pulled into a Project as persistent knowledge (key funnels, success metrics, prior experiment learnings) lives inside the team's Juma workspace, encrypted AES-256 in-transit and at-rest. Juma's zero data retention policy with AI providers means raw Mixpanel event data is never used to train a third-party model. SOC 2 Type II and ISO/IEC 27001 audits are available on request.
How is this different from using Juma + PostHog?
Both cover product analytics, experiments, feature flags, and session replay. The distinctive Mixpanel angle through Juma is the built-in best-practice guidance: setup, results interpretation, feature flag lifecycle. Mixpanel ships those helpers as first-class tools, so teams without an in-house experimentation expert can run a sound A/B test by following the guidance Juma applies in chat. PostHog ships first-party event capture, ad-blocker resistance, and SQL-flexible querying. B2B SaaS PLG teams often use Mixpanel; teams wanting first-party data sovereignty often use PostHog. Both are supported.
Can I cancel Mixpanel and just use Juma?
No. Juma needs Mixpanel's tracked events, funnels, experiments, feature flags, and session replay data to do any of the work on this page. Juma is the AI layer on top of Mixpanel, not a replacement. What Juma can replace is the rest of the product-analytics stack: the dedicated analyst running ad-hoc queries, the separate dashboard tool (Hex, Mode, Looker) for executive reporting, and the meeting cadence where someone explains what experiment results mean. Mixpanel stays as the data source.
How much does it cost to use Mixpanel through Juma?
Juma prices by what gets done, not by which model ran. Tasks consume credits: low-effort tasks like a single funnel query are 1 to 100 credits, high-effort tasks like a full experiment design with setup guidance and stakeholder doc are 100 to 500 credits, failed tasks cost zero. Every Juma plan includes unlimited seats and the Mixpanel connector. The Mixpanel subscription is separate; Juma doesn't resell Mixpanel or mark up Mixpanel's data.
Can Juma actually create experiments and feature flags, or only analyze them?
Both. The integration is bidirectional. Juma can read events, properties, queries, dashboards, experiments, and flags, and create or update them too: build dashboards, create experiments in DRAFT (after Get-Experiment-Setup-Guidance), manage the lifecycle through Update-Experiment, create feature flags after Get-Feature-Flag-Setup-Guidance, and stage rollouts. Every write goes through team review before it ships; for live customer experiments and rollouts, this review is non-negotiable.
What about session replays: can Juma actually see what users do in them?
Juma pulls replay metadata through Get-User-Replays-Data (up to 20 replays per call), surfaces shared patterns across the set, and links back to the recording in Mixpanel for the team to scan visually. Juma doesn't transcribe video; it returns structured summaries and lets the team open specific recordings in Mixpanel when they want to see the actual user behavior. For funnel-drop diagnosis, the structured summary plus a quick visual scan usually spots the friction.
Ask AI about us
400+ marketing teams trust Juma. ChatGPT, Claude, and Perplexity know why. Ask them.
Ready when you are
What's on your plate today?
Start typing a task and Juma will figure out the rest.