Skip to content
Components

MixPanel

Export raw event data from Mixpanel into Storage as a name-value pair table or as raw JSON, for a date range or a rolling window of full days.

Mixpanel analyzes user behavior across websites and apps. The MixPanel data source connector uses the raw data export API to download event data into Storage. The API returns one JSON object per event, and events do not share the same keys, so by default the connector unpivots them into a name-value pair table. It can also store the raw JSON for you to parse in a transformation.

Create a new configuration of the MixPanel data source connector. The connector has no rows; one configuration is one export.

FieldDescription
API secretAPI secret of the project to export. Stored encrypted.
Residency data serverRegion where the project’s data is stored: US (default) or EU.
From date and To dateDate bounds of the export in YYYY-MM-DD format. Leave both empty to export by Throwback instead.
ThrowbackNumber of full days before today to export: -1 exports yesterday, -2 the two days before today, and so on. Default -1. Ignored when both From date and To date are set.
Project timezoneTimezone of the Mixpanel project. Throwback needs it to pick the right days. Default UTC.
EventsOptional list of events to export. Empty exports all events.
WhereOptional segmentation expression that filters the events.
Load typeFull load (default) overwrites the table on every run. Incremental load creates the table with primary keys and upserts new data.
Raw data exportOff: the JSON is parsed into a name-value pair table. On: the raw JSON response is stored in the table for you to parse later, for example in a Snowflake or Python transformation.

Screenshot - MixPanel configuration

With raw data export off, the connector returns one table with three columns:

idparametervalue
149883e1c6000df0f5dc4d521725679beventView Payslip Page
149883e1c6000df0f5dc4d521725679bproperties__time1561420800
149883e1c6000df0f5dc4d521725679bproperties__distinct_id0051o000009eqc1AAA
149883e1c6000df0f5dc4d521725679bproperties__$cityEvesham

id is the MD5 hash of the unprocessed row, so it is unique per exported event and lets you pivot the parameters of one event back together.

With raw data export on, the table has two columns, id and raw, where raw holds the unprocessed JSON.

Large exports can run for hours. For a full history, split the export into several runs with From date and To date. In a nightly flow, use Throwback instead, so each run picks up the latest full days.

Ask Kai

Hi, I'm Kai — Keboola's AI assistant for the docs. Ask me anything and I'll answer from the documentation and cite the pages I use.

Kai is an AI and can make mistakes. Check the sources it links.