Data Pipelines is a paid add-on (opens in a new tab) which continuously exports the events in your Mixpanel project to a cloud storage bucket or data warehouse of your choice. It's useful if you want to analyze Mixpanel events using SQL in your own environment.
Using Data Pipelines requires 2 steps:
- Configuring your destination to allow Mixpanel to write to it.
- Telling Mixpanel to start exporting your data to that destination using the Pipelines API.
We offer a 30-day free trial of the Data Pipelines add-on. See the FAQ for how to enable it.
Configuration depends on the type of Pipeline you want to set up.
Raw Pipelines export events as JSON to a cloud storage bucket. This is the simplest approach.
See our configuration guides for each raw destination:
Upon successful creation of a pipeline, events will be exported to the following locations:
complete file will be written in the finished hour or day prefix to indicate that the export is complete. The absence of this file means there is an ongoing export for that hour or day.
Schematized Pipelines export events into tables with schemas generated by Mixpanel, inferred from your event history. There are two types of schemas, which you can configure:
- Monoschema: A single table for all events in which you have the event name as the column and one column per property.
- Multischema: One table per event name with the properties of that event as columns.
See our configuration guides for each schematized destination:
The Schematized Pipeline reference goes the details of schematization and the output format.
Once you’ve configured your destination, you need to tell Mixpanel to start exporting to that destination.
You can do this with our Create Pipeline API (opens in a new tab). You can create the Pipeline directly from our developer docs UI.
- For event export pipelines (
data_source: events) in each Mixpanel project, we support at most two recurring pipelines (
to_dateis empty) and one non-recurring pipeline (has a
to_datethat is the ending date of the export window).
- Note that
from_datemust also be no more than 6 months from the date the pipeline is created.
This normally happens when you have thousands of unique event names or property names, which is usually an implementation mistake (eg: including a UUID in the event or property name). This causes the export process to exceed table or column limits in the destination. In these cases, we try to identify the bad patterns and exclude them from the export process. We always try to communicate this to the customers through their Customer Success Managers.
Why does the number of events in Mixpanel not match the number of exported events to my destination?
This can happen for a few reasons:
- Data Sync is not enabled or not supported for your pipeline.
- Data Delay: it can take up to 1 day for late arriving data to be synced from Mixpanel to your destination.
- Hidden Events: Mixpanel exports all events to your destination, even ones that are hidden in the UI via Lexicon. We recommend checking whether the count in your destination is mostly due to events that have been hidden in the Mixpanel UI.
Mixpanel offers a 30-day trial version of the Data Pipelines. The trial allows for one data export pipeline per project to be created. Simply pass
trial=true to our API to create a trial pipeline.
- Export scheduling is daily only.
- Data sync is unavailable.
- You can only create one pipeline per project.
- Backfilled data will only include one day prior to the creation date.
- Pipelines will, by default, include both event and user data (not available for raw pipelines).
- The pipeline cannot filter by event name.
- The “Create Pipeline” parameters will default to the values highlighted to list in the parameters table (opens in a new tab).
Was this page useful?