Mixpanel tracks how people use your product — events, user profiles, and cohorts. Connecting it as a data source through the Connectors library syncs that product-analytics data into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure activation, engagement, and retention — and tie product usage to revenue. Mixpanel connects with credentials.

Who this is for: Product, growth, and analytics teams who want Mixpanel usage data analyzed alongside revenue and CRM data in Alta.

Before you start

Create a Mixpanel service account and have its username/secret and your project ID ready. Note your data region (US or EU residency).
Think about which events matter — Mixpanel projects often have hundreds; you'll get more value syncing the key ones.
Connect a source only once per workspace. If Mixpanel already shows Connected, edit the existing connection.

Connect Mixpanel

Open Connectors from the sidebar.
Find Mixpanel via the category tabs or the Search data sources box.
Click the Mixpanel card to open the Create connector screen.
Fill in the connection fields shown (such as service account credentials and project ID), then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with Mixpanel's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. Mixpanel brings in tables like events, engage (profiles), and cohorts.
Use the Synced toggle in the Mixpanel tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.

Key tables and fields synced

events — the raw activity stream: event (name), time, distinct_id, plus all event properties (e.g. $browser, $city, custom props)
engage (user profiles) — distinct_id, $email, $name, and profile properties like plan or account
cohorts — saved user segments: id, name, count

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"How many active users did we have last week?" — counts distinct distinct_id in events by time.
"What's the most common event during onboarding?" — groups events.event for new users.
"What's feature adoption by cohort?" — joins events to cohorts.
"How does product usage trend month over month?" — trends event volume over time.
"Which accounts are most active?" — aggregates events by an account property on engage.

Example use cases

Activation & engagement. Track key events (signups, first value, weekly active) and how they trend.
Usage-to-revenue. Join product usage to CRM/billing data to see whether engaged accounts renew and expand.
Adoption by segment. Compare feature usage across cohorts or plans.
Churn-risk signals. Flag accounts whose usage is dropping for CS follow-up.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

Events are high-volume. The events table can be very large — expect the first sync to take a while, and consider focusing on key events.
Match the region. Pointing at the wrong US/EU residency is a common cause of a failed connect test.
Use a property to tie users to accounts. An account/company property on profiles makes usage-to-revenue analysis possible.
Deleting is permanent. Disable instead to pause.