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.
Scenario
Your Mixpanel project has thousands of user profiles with demographic and behavioral properties — plan type, company size, role, signup source, total events fired. You query the Engage API to pull profiles, cluster them by usage patterns (power users vs. casual vs. dormant), and create a Mavera Custom Persona for each cluster. The result is a persona library built from actual product behavior.Architecture
Code
Example Output
Error Handling
Engage API rate limit (60/hour)
Engage API rate limit (60/hour)
The Engage API shares the 60 queries/hour limit. Each page request counts as one query. For 5,000+ profiles, this takes multiple pages — budget 1 query per 1,000 users. Add a 60s sleep on 429.
Session ID for pagination
Session ID for pagination
The Engage API returns a
session_id on the first response. You must pass it on subsequent pages to maintain cursor position. If omitted, results may overlap.Missing profile properties
Missing profile properties
Not all users have every property set. The clustering code handles
None/0 defaults. Custom properties must be set via $set in your tracking code.What’s Next
Mixpanel Integration
Back to Mixpanel integration overview
Funnel Drop-off → Focus Group
Investigate funnel abandonment with focus groups
Personas API
Full reference for POST /api/v1/personas
Mave Agent
Full reference for POST /api/v1/mave/chat