Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mavera.io/llms.txt

Use this file to discover all available pages before exploring further.

Mixpanel holds your product’s behavioral truth — who your users are, what they do, where they drop off, and which features they adopt. These five jobs pull that data through Mavera’s surfaces (Custom Personas, Focus Groups, Mave Agent, Generate) so your personas, messaging, and campaigns are grounded in real product usage, not survey data.

API Reference Card

DetailValue
Base URLhttps://mixpanel.com/api/query
AuthService Accounts via HTTP Basic Auth (service_account:secret)
Rate limits60 queries/hour; 5 concurrent requests
Export APIhttps://data.mixpanel.com/api/2.0/export (raw events)
Mavera basehttps://app.mavera.io/api/v1
Mavera authAuthorization: Bearer mvra_live_...
All examples use four environment variables: MIXPANEL_SERVICE_ACCOUNT (service account username), MIXPANEL_SECRET (service account secret), MIXPANEL_PROJECT_ID, and MAVERA_API_KEY. Python examples use requests with Basic Auth; JavaScript examples use fetch with the same auth pattern.

Prerequisites

1

Mixpanel project with data

You need an active Mixpanel project with at least 30 days of tracked events and user profiles. Find your project ID in Mixpanel → Settings → Project Settings.
2

Service account

Create a Service Account in Mixpanel → Organization Settings → Service Accounts. Grant it Analyst role on your project.
3

Mavera API key

Get your key from Mavera dashboard.
4

Environment variables

export MIXPANEL_SERVICE_ACCOUNT="your-service-account.abc123.mp-service-account"
export MIXPANEL_SECRET="your-secret-here"
export MIXPANEL_PROJECT_ID="1234567"
export MAVERA_API_KEY="mvra_live_xxxxx"

Jobs

#JobMixpanel DataMavera SurfaceOutput
1User Profile Clustering → PersonasEngage API (profiles)Custom PersonasBehavior-based persona set
2Funnel Drop-off → Focus Group InvestigationFunnels APIFocus GroupsStep-by-step abandonment insights
3Cohort Analysis → Content StrategyCohort dataMave AgentRetention strategies from behavior
4Event-Based Persona EnrichmentExport API (raw events)Custom PersonasPower-user vs casual patterns
5Feature Adoption → Messaging PrioritiesFeature usage metricsFocus Groups + GenerateFeature awareness campaigns

Rate Limits & Production Notes

Mixpanel EndpointLimitStrategy
Query APIs (Insights, Funnels, Engage)60 queries/hour; 5 concurrentQueue queries; 60s retry on 429
Export API (/api/2.0/export)Separate from query limitsStream large exports; process line-by-line
Engage API pagination1,000 profiles/pageTrack session_id; each page = 1 query
Mixpanel’s 60 queries/hour limit is strict and applies across all query APIs. If you run all 5 jobs sequentially, budget ~20 queries total. Spread jobs across hours or cache results locally for exploratory analysis.
Production checklist:
ConcernRecommendation
Service account rotationRotate secrets quarterly in Mixpanel → Organization Settings → Service Accounts.
Basic Auth securityNever log or expose the service account credentials. Use environment variables or a secrets manager.
Export API volumeThe Export API returns all events matching the date range. For high-volume projects (1M+ events/day), filter by specific event names or use shorter date ranges.
Mixpanel EU residencyIf your project is EU-hosted, use eu.mixpanel.com instead of mixpanel.com for all API endpoints.
Mavera creditsMonitor at Dashboard. Focus Groups with 3+ personas consume more credits than single Mave calls.
CachingCache Engage profiles and funnel data locally — they rarely change more than daily. Re-export events weekly for enrichment jobs.

What’s Next

All Integrations

50+ API integrations with full code

Mixpanel API Docs

Official Mixpanel API reference

Personas API

Full reference for POST /api/v1/personas

Focus Groups API

Full reference for POST /api/v1/focus-groups

Mave Agent

Full reference for POST /api/v1/mave/chat

Generate API

Full reference for POST /api/v1/generations