Source connector

Mixpanel connector

Mixpanel integration for databases, warehouses and BI tools

Product analytics for events, funnels, and retention. Datrise captures Mixpanel entities such as events, user profiles, cohorts, funnels, and retention metrics, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Mixpanel Raw Data Export API authenticates with HTTP Basic, service account, incremental runs key on from_date/to_date (UTC day range; events are immutable once ingested), and Mixpanel caps calls at 60 queries/hour, 3 queries/second, and up to 100 concurrent queries per project.

Of the 5 objects, 3 sync as upserts keyed on the primary key and 2 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `mixpanel_events`) with a schema derived from the Mixpanel API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Mixpanel pipeline page, and join the waitlist to get the Mixpanel connector (Product analytics) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Mixpanel data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
events	mixpanel_events	Append-only, incremental by timestamp
user profiles	mixpanel_user_profiles	Upsert by primary key, incremental on updated-at
cohorts	mixpanel_cohorts	Upsert by primary key, incremental on updated-at
funnels	mixpanel_funnels	Upsert by primary key, incremental on updated-at
retention metrics	mixpanel_retention_metrics	Append-only, incremental by timestamp

Mixpanel API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Mixpanel Raw Data Export API
Authentication	HTTP Basic, service account — HTTP Basic Auth using either the project's Service Account username/secret (recommended, project-scoped and rotatable) or the legacy Project Secret.
Pagination	none — There is no cursor or page token; a single call streams JSONL for the whole `from_date`-`to_date` range (each response event is one line), capped by an optional `limit` of at most 100,000 events.
Rate limit	60 queries/hour, 3 queries/second, and up to 100 concurrent queries per project
Incremental cursor	from_date/to_date (UTC day range; events are immutable once ingested) — Dates are interpreted as UTC for projects created after 2023-01-01 and as the project's configured timezone for older projects, so the day boundary a connector uses must match the project's own convention.
Webhooks	No
Bulk export	Yes — Raw Data Export API (JSONL, no row cap on the date range)
Deletes detectable	No

Official API reference

What bites when replicating Mixpanel

There is no public API to delete or detect deletion of individual events; the only deletion path is the GDPR/CCPA Data Deletions API, which removes all events and profile data for up to 2,000 `distinct_id`s per request and can take multiple weeks to complete, with no corresponding change surfaced in the Export API.
The Export endpoint enforces 60 queries/hour and 3/second per project, so a connector backfilling many small daily windows instead of fewer wide-range calls will hit HTTP 429 quickly.
`from_date`/`to_date` day boundaries are UTC only for projects created on or after 2023-01-01; older projects still bucket by the project's configured timezone, so the same date parameter can select a different 24-hour window depending on project age.
The optional `limit` parameter caps a single response at 100,000 events; a high-volume project must split by narrower date ranges or the `event`/`where` filters rather than relying on `limit` to paginate.

Compare this against every other documented API

Popular destinations for Mixpanel

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Mixpanel connector FAQ

What Mixpanel data does the connector extract?: 5 objects: events, user profiles, cohorts, funnels and retention metrics. Each lands in its own table with types preserved; history-style objects (2: events and retention metrics) load as append-only streams.
Is the Mixpanel integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Mixpanel data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Mixpanel → destination pair has its own page with the object-to-table mapping.

Related Product analytics sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Mixpanel pipeline with guided onboarding

Join the waitlist to get priority access for Mixpanel integrations with guided setup, schema-aware mapping, and production-grade incremental sync.