Mixpanel
Analytics & DataConnect AI agents to Mixpanel product analytics across US, EU, and India residencies. Agents ingest events and profiles, stitch identities, run segmentation, funnel, and retention queries, export raw events, and sync Lexicon schemas across 36 actions.
What This Integration Enables
Mixpanel is only as trustworthy as two things almost nobody maintains: the identity graph and the tracking plan. This integration covers the full surface, with US, EU, and India data residency support. On ingestion, agents stream events through Track Event, backfill history with strict per-record validation through Import Events, and manage user and group profiles with the complete set of set, set-once, increment, append, union, remove, and unset operations. On the query side, agents run segmentation, funnel, and retention analyses, pull saved Insights reports, query profiles and cohorts, and export raw events into FlowRunner file storage for warehousing. Then there is the layer that makes the numbers mean something: identity management and Lexicon governance. Merging identities and rewriting schema definitions are the two operations where a wrong automated write corrupts every metric downstream, which is why this connector pairs them with [human-in-the-loop](/concepts/human-in-the-loop/) review instead of running them open loop. Connector capabilities are built and verified against Mixpanel's official APIs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Identity stitching with a person at the merge
A nightly agent queries profiles that share an email or external key across distinct IDs, pulls Get Activity Stream for each candidate pair, and scores whether the histories look like one person on two devices or two people sharing an address. High-confidence pairs go to the data owner with the evidence: the shared key, the event timelines, the device signatures. Only approved pairs get Merge Identities. Duplicate users stop inflating the counts, and no merge ever has to be explained after the fact.
The metrics digest that runs the growth standup
On a schedule, an agent runs Run Funnel Query on the saved activation funnel, Run Retention Query on the same population, and Run Segmentation Query for the week's key events. Results append to a running dashboard with [Google Sheets](/integrations/google-sheets) and a summary posts to the growth channel in [Slack](/integrations/slack), with movements against the prior period called out. The standup starts from numbers nobody had to fetch.
Backfill and tracking-plan sync from the source of truth
When events flow through [Segment](/integrations/segment), an agent mirrors historical activity into Mixpanel with Import Events, which validates each record on the way in. When the internal tracking plan changes, the agent stages Upload Lexicon Schemas to sync event and property definitions into Mixpanel's data dictionary, and posts the diff for review first, because uploading replaces existing schema metadata for the entities it covers. The dictionary analysts rely on stays aligned with the spec engineers actually implemented.
Human-in-Loop Highlight
Merge Identities collapses two distinct IDs into a single identity cluster, and there is no clean way back: once merged, every downstream query treats them as one person forever. A wrong merge does not just miscount one user, it quietly corrupts funnels, retention cohorts, and revenue attribution for both histories. So the stitching agent never merges on its own score. It posts each candidate to the data owner: "distinct_id app_7f31 and web_c209 share the email [email protected]. App history starts 2 March, web history ends 1 March, no overlapping sessions. Merge as one user, or keep separate?" The agent finds and documents the candidates at a scale no analyst would attempt by hand. The human makes the only decision the identity graph cannot take back.
Agent Capabilities
36 actionsEvent Ingestion
2- Track Event Sends a single real-time event through the /track endpoint using the Project Token. Used for events from the last few days; historical data goes through Import Events.
- Import Events Imports batches of historical events with strict per-record validation, authenticated by Service Account. The backbone of backfills and migrations.
User Profiles
9- Set Profile Properties Sets profile properties, overwriting existing values and creating the profile if needed. Used to keep user attributes current.
- Set Profile Properties Once Sets properties only if not already set. Used for first-touch attribution that must never be overwritten.
- Increment Profile Properties Increments numeric properties by a given amount, negative to decrement. Used for counters like logins or orders.
- Append To Profile List Properties Appends values to list properties, allowing duplicates. Used for chronological logs on a profile.
- Union Profile List Properties Merges values into list properties with duplicates removed. Used for tag-like sets.
- Remove From Profile List Properties Removes a specific value from list properties. Used for opt-outs and set maintenance.
- Unset Profile Properties Permanently removes named properties from a profile. Used in data hygiene and privacy workflows.
- Delete Profile Permanently deletes a user profile; historical events remain. Runs only in reviewed privacy and cleanup workflows.
- Batch Update Profiles Sends up to 2,000 raw profile update objects in one request. Used for large-scale profile sync jobs.
Group Profiles
7- Set Group Properties Sets properties on a group profile, such as a company or account, creating it if needed. Used for B2B account analytics.
- Set Group Properties Once Sets group properties only if not already set.
- Union Group List Properties Merges values into group list properties with duplicates removed.
- Remove From Group List Properties Removes a value from group list properties.
- Unset Group Properties Permanently removes named properties from a group profile.
- Delete Group Profile Permanently deletes a group profile; attributed events remain. Reviewed cleanup only.
- Batch Update Group Profiles Sends up to 200 raw group update objects in one request. Used for account-level sync jobs.
Identity Management
3- Create Alias Links a new alias to an existing distinct ID on Legacy or Original ID Merge projects.
- Create Identity Connects an anonymous ID to an identified user ID on Original ID Merge projects. Used at the signup boundary.
- Merge Identities Merges two distinct IDs into a single identity cluster. The gated action in this connector: every merge is human-approved with evidence attached.
Analytics Queries
5- Run Segmentation Query Runs a segmentation report for an event over a date range with property expressions and filters. The workhorse for scheduled metric pulls.
- Query Event Counts Returns aggregated counts for events bucketed by time unit. Used in volume monitoring.
- Get Today's Top Events Returns today's top events with counts and change from yesterday. Used in daily anomaly checks.
- List Top Event Names Returns the most common event names over the last 31 days. Used to discover what a project actually tracks.
- Query Insights Report Returns the saved data of an existing Insights report by bookmark ID. Used to reuse analyses the team already trusts.
Funnels and Retention
3- Run Funnel Query Runs a saved funnel and returns per-step counts and conversion ratios. Used for the scheduled activation report.
- List Saved Funnels Lists saved funnels with IDs. Used to resolve targets for Run Funnel Query.
- Run Retention Query Runs cohort retention analysis in birth or compounded mode. Used to confirm whether funnel movements reflect real behavior change.
Profiles and Cohorts
3- Query Profiles Queries user profiles by expression, distinct IDs, or saved cohort. Used to find identity-merge candidates and build audiences.
- List Cohorts Lists saved cohorts with size and description. Used to hand populations to downstream workflows.
- Get Activity Stream Returns the chronological event feed for specific users. The evidence source for identity review and support investigations.
Data Export
1- Export Events Exports raw event data for a date range, inline or saved to FlowRunner file storage as JSONL for large exports. Used for warehousing and downstream processing.
Lexicon
3- List Lexicon Schemas Lists the project's data dictionary schemas by entity type. Used to audit the tracking plan as deployed.
- Get Lexicon Schema Retrieves a single schema by entity type and name.
- Upload Lexicon Schemas Creates or replaces data dictionary schemas, syncing an internal tracking plan into Mixpanel. Replacement semantics mean the diff is reviewed before upload.
Frequently Asked Questions
What can FlowRunner do with Mixpanel?
FlowRunner agents can run Track Event, Import Events, and Set Profile Properties in Mixpanel, plus 33 more actions.
Does connecting Mixpanel to FlowRunner require OAuth?
No. Mixpanel connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Mixpanel trigger a FlowRunner workflow automatically?
Mixpanel doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mixpanel
$100 in credits. No card required. Connect in minutes.