Sources

Mixpanel

Connect one Mixpanel project with a service account, choose the event history window, and sync events, people, cohorts, funnels, and annotations.

Connect a Mixpanel project in about five minutes. Embrasure authenticates with a Mixpanel service account, so you do not create a marketplace OAuth app, wait for approval, or expose a project API secret.

Have an agent set it up instead:

Before you start

You need:

  • An Embrasure workspace administrator
  • A Mixpanel organization member who can create service accounts and grant the account Analyst or higher access to the target project
  • The project's numeric ID and its data residency region, both shown in Mixpanel project settings

US, EU, and India data residency clusters are supported.

Connect Mixpanel

Create a service account

Open Mixpanel service accounts and select Add Service Account. Add it to only the project you want to sync with Analyst or higher access. Consumer access is not enough. Copy the username and the secret; Mixpanel shows the secret once. If Mixpanel redirects the link, open Organization SettingsService Accounts manually.

See Mixpanel's service account reference and role permissions.

Find the project ID and region

Open Project SettingsOverview. Copy the numeric Project ID and note the Data Residency region (US, EU, or India). Embrasure reads from the residency-matched API clusters, for example data-eu.mixpanel.com for EU projects.

Open the Mixpanel source

In Embrasure, open WarehouseIngestion. Select Connect warehouse source for the first source, or New sync if the workspace already has ingestion syncs. Find Mixpanel under Add a warehouse source, then paste the service account username, secret, and project ID, and pick the region.

Choose the event history

Initial history controls how far back the raw event export begins.

ChoiceUse it when
Last 90 daysRecommended default for a fast, useful first sync.
Last 365 daysYou need annual comparisons or seasonality.
Full historyYou need every exportable event and can wait for the larger first sync.

The history choice affects events only. People, cohorts, cohort membership, funnels, and annotations are always synced as complete snapshots.

Verify and start syncing

Select Connect. Embrasure verifies the service account against the project, discovers the tables below, and starts the initial sync.

What is synced

TableContentsHow it updates
mixpanel.eventsRaw events from the Raw Export API, keyed by insert ID with the full property payload.Incremental day windows with a trailing re-export overlap, so late and attributed events are captured.
mixpanel.peopleEngage user profiles with promoted email, name, and last-seen columns plus the full property payload.Full snapshot rescan on every sync.
mixpanel.cohortsCohort definitions with size and visibility.Full snapshot rescan.
mixpanel.cohort_membersOne row per cohort and member distinct ID.Full snapshot rescan per cohort.
mixpanel.funnelsSaved funnel definitions. Funnel measurements can be computed in the warehouse from mixpanel.events.Full snapshot rescan.
mixpanel.annotationsProject annotations with date and description.Full snapshot rescan.

Rows deleted in Mixpanel stop appearing in later snapshots but are not tombstoned in the warehouse; hard deletes are not detected for this source.

Troubleshooting

  • Verification fails with an authentication error. The service account username or secret is wrong, or the secret was regenerated. Paste the current pair.
  • Verification fails with a permission error. Add the service account to the project with Analyst or higher access, then retry. Consumer access is not enough.
  • Tables verify but events stay empty. Check the region: a project on the EU or India cluster returns no export rows through the US endpoints.