Mixpanel
Mixpanel is a business analytics service that tracks user interactions with web and mobile applications. The data collected is used to build custom reports and measure user engagement and retention.
Features
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | ||
History mode | check | |
Custom data | check | |
Data blocking | check | |
Column hashing | ||
Re-sync | check | |
API configurable | check | API configuration |
Priority-first sync | check | EVENT |
Fivetran data models | check | |
Private networking | ||
Authorization via API | check |
Setup guide
Follow our step-by-step Mixpanel setup guide to connect Mixpanel with your destination using Fivetran connectors.
Sync overview
During the initial sync, our system pulls all events from the last 30 days. After the initial sync has completed, we start pulling historical events at regular intervals. It might take a few days for all historical events to end up in your destination.
Schema information
This schema applies to all Mixpanel connectors.
To zoom, open the ERD in a new window.Schema notes
We use the _fivetran_id
and time
columns as the schema's primary keys. We select the _fivetran_id
value based on the following conditions:
For connectors created before November 20, 2020, we select the
_fivetran_id
value based on the following conditions:- If the record's
event.time
value is before July 1, 2021, we calculate the_fivetran_id
value by generating the hash for the entire record. - If the record's
event.time
value is after July 1, 2021, we use the record'sinsert_id
value as the_fivetran_id
value.
- If the record's
For connectors created after November 20, 2020, we use the record's
insert_id
value as the_fivetran_id
value.
Sync note
Mixpanel has disabled the Campaigns feature for new Mixpanel projects. If you are on a new Mixpanel project and include the CAMPAIGN
table in your syncs, your syncs may fail.
Ensure that $ignore_time
is set to false
for records in the PEOPLE
table. If it is set to true
for these records, we cannot sync them to the destination because we use the time field to incrementally update this table.