Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query Mixpanel analytics with funnels, retention, segmentation, and event tracking via REST API.
Query Mixpanel analytics with funnels, retention, segmentation, and event tracking via REST API.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines.
User needs product analytics from Mixpanel. Agent handles event queries, funnel analysis, retention cohorts, user segmentation, and profile lookups.
Memory lives in ~/mixpanel/. See memory-template.md for structure. ~/mixpanel/ โโโ memory.md # Projects, saved queries, insights โโโ queries/ # Saved JQL queries
TopicFileSetup processsetup.mdMemory templatememory-template.md
Requires a Mixpanel Service Account: export MP_SERVICE_ACCOUNT="your-service-account" export MP_SERVICE_SECRET="your-service-secret" export MP_PROJECT_ID="123456" Create a service account in Mixpanel โ Organization Settings โ Service Accounts.
Use the Query API for insights, funnels, retention: BASE="https://mixpanel.com/api/query" AUTH=$(echo -n "$MP_SERVICE_ACCOUNT:$MP_SERVICE_SECRET" | base64) # Insights query (event counts) curl -s "$BASE/insights?project_id=$MP_PROJECT_ID" \ -H "Authorization: Basic $AUTH" \ -H "Content-Type: application/json" \ -d '{ "params": { "event": ["Sign Up", "Purchase"], "type": "general", "unit": "day", "from_date": "2024-01-01", "to_date": "2024-01-31" } }' | jq
curl -s "$BASE/funnels?project_id=$MP_PROJECT_ID" \ -H "Authorization: Basic $AUTH" \ -H "Content-Type: application/json" \ -d '{ "params": { "events": [ {"event": "Sign Up"}, {"event": "Complete Onboarding"}, {"event": "First Purchase"} ], "from_date": "2024-01-01", "to_date": "2024-01-31", "unit": "day" } }' | jq '.data.meta.overall'
curl -s "$BASE/retention?project_id=$MP_PROJECT_ID" \ -H "Authorization: Basic $AUTH" \ -H "Content-Type: application/json" \ -d '{ "params": { "born_event": "Sign Up", "event": "App Open", "from_date": "2024-01-01", "to_date": "2024-01-31", "unit": "week", "retention_type": "birth" } }' | jq
curl -s "https://mixpanel.com/api/query/engage?project_id=$MP_PROJECT_ID" \ -H "Authorization: Basic $AUTH" \ -H "Content-Type: application/json" \ -d '{ "filter_by_cohort": {"id": 12345}, "output_properties": ["$email", "$name", "plan"] }' | jq
curl -s "https://data.mixpanel.com/api/2.0/export?project_id=$MP_PROJECT_ID" \ -H "Authorization: Basic $AUTH" \ -d "from_date=2024-01-01" \ -d "to_date=2024-01-07" \ -d "event=[\"Purchase\"]"
// Mixpanel JQL (JavaScript Query Language) function main() { return Events({ from_date: "2024-01-01", to_date: "2024-01-31", event_selectors: [{event: "Purchase"}] }) .groupByUser(["properties.$city"], mixpanel.reducer.sum("properties.amount")) .groupBy(["key.$city"], mixpanel.reducer.avg("value")) .sortDesc("value") .take(10); }
GoalEndpointKey ParamsEvent counts/insightsevent, type, unit, datesConversion funnel/funnelsevents array, datesUser retention/retentionborn_event, event, unitUser segments/engagefilter_by_cohort, propertiesRaw event export/exportdates, event filter
Wrong date format โ use YYYY-MM-DD, not timestamps Missing project_id โ every Query API call needs it Rate limits โ 60 requests/hour for free tier, batch queries when possible JQL timeouts โ queries over 60s fail, add .take(N) to limit results
EndpointData SentPurposemixpanel.com/api/query/*Credentials, project ID, query paramsAnalytics queriesdata.mixpanel.com/api/2.0/*Credentials, project ID, date rangeRaw data export No other data is sent externally.
Data sent to Mixpanel (over HTTPS): Service account credentials for authentication Query parameters (event names, date ranges, filters) Project ID Data that stays local: Credentials stored ONLY in environment variables Query results cached in ~/mixpanel/ This skill does NOT: Store credentials in memory.md or any file Send data to services other than mixpanel.com Modify your Mixpanel tracking code or SDK
By using this skill, analytics data is queried from Mixpanel. Only install if you trust Mixpanel with your product data.
Install with clawhub install <slug> if user confirms: analytics โ multi-platform analytics data-analysis โ data processing patterns api โ REST API best practices
If useful: clawhub star mixpanel Stay updated: clawhub sync
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.