This integration is certified by Stitch. For support, contact Stitch support.
Mixpanel feature snapshot
A high-level look at Stitch's Mixpanel integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release Status |
Released |
Supported By | |
| Stitch Plan |
Free |
||
| DATA SELECTION | |||
| Table Selection |
Supported |
Column Selection |
Unsupported |
| REPLICATION SETTINGS | |||
| Anchor Scheduling |
Supported |
Advanced Scheduling |
Unsupported |
| Table-level Reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
| TRANSPARENCY | |||
| Extraction Logs |
Unsupported |
Loading Reports |
Supported |
Connecting Mixpanel
Connecting your Mixpanel data to Stitch is a five-step process:
- Retrieve your Mixpanel API credentials
- Add Mixpanel as a Stitch data source
- Define the Historical Sync
- Define the Replication Frequency
- Select tables to sync
Retrieve Your Mixpanel API Credentials
- Sign into your Mixpanel account.
- Click Account, which is located in the upper right portion of the screen.
-
In the modal that displays, click Projects.
Note that this window is different than the Project Settings window, which is accessed using the gear icon in the lower left corner. The window you need is accessed only by clicking Account > Projects.
-
Your API credentials will display:
Leave this page open - you’ll need it to complete the setup in Stitch.
Add Mixpanel as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Mixpanel icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Mixpanel” would create a schema called
stitch_mixpanelin the destination. Note: Schema names cannot be changed after you save the integration. - Paste your API credentials in the the API Key and Secret fields, respectively.
Define the Historical Sync
The Sync Historical Data setting will define the starting date for your Mixpanel integration. This means that:
- For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Mixpanel’s default setting of 7 days. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Important: Historical replication and Mixpanel limitations
Mixpanel limits the queryable time range for some of its endpoints to either 60 or 90 days to prevent poor loading times for their customers. We’ve found if the Start Date is greater than this, some historical replication may not complete successfully.
If you notice issues with the historical replication of a Mixpanel integration, check that the Start Date is set to no more than 60 days in the past. Changing this setting can sometimes resolve the issue.
Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Mixpanel integrations support the following replication scheduling methods:
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Set tables to replicate
To complete the setup, you’ll need to select the tables you want to replicate to your data warehouse.
Check out the Schema section to learn more about the available tables in Mixpanel and how they replicate.
- In the Integration Details page, click the Tables to Replicate tab.
- Locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.
- Repeat this process for all the tables you want to replicate.
Initial and historical replication jobs
After you finish setting up Mixpanel, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Replicating Mixpanel Data
Because of how Mixpanel’s API is designed, two of the three tables in our Mixpanel integration - the mixpanel_export and mixpanel_funnels tables - can only be queried by day. This means that every time Stitch runs a replication job for a Mixpanel integration, the past day’s worth of data will be replicated for each of these tables.
To prevent the re-replication of data that will count against your row count, we recommend setting the Replication Frequency to something less frequent.
Mixpanel Schema
Note that these tables won't automatically be created in your data warehouse. You must set them to sync in the Integration Details page first.
Stitch's Mixpanel integration includes these tables:
mixpanel_engage
Replication Method: Full Table
Primary Key: distinct_id
Contains Nested Structures?:
Yes
mixpanel_engage table contains info from People Analytics, which will enable you to do user-level analysis. This data is only available to Mixpanel customers with a People Plan.mixpanel_engage & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
mixpanel_engage Attributes
While we try to include everything Mixpanel has here, this may not be a full list of attributes. Refer to Mixpanel's documentation for a full list and description of each attribute.
distinct_id
created
email
first_name
last_name
last_seen
mixpanel_export
Replication Method: Key-based Incremental
Primary Key: event:time:distinct_id:_rjm_record_hash
Contains Nested Structures?:
No
mixpanel_export table contains raw event data.Replication
Because of how Mixpanel’s API is designed, this table can only be queried by day. This means that every time Stitch runs a replication job for a Mixpanel integration, the past day’s worth of data will be replicated for this table.
mixpanel_export Attributes
While we try to include everything Mixpanel has here, this may not be a full list of attributes. Refer to Mixpanel's documentation for a full list and description of each attribute.
distinct_id
event
mp_country_code
mp_lib
mp_reserved_browser
mp_reserved_browser_version
mp_reserved_city
mp_reserved_current_url
mp_reserved_initial_referrer
mp_reserved_initial_referring_domain
mp_reserved_lib_version
mp_reserved_os
mp_reserved_region
mp_reserved_screen_height
mp_reserved_screen_width
time
_rjm_record_hash
mixpanel_funnels
Replication Method: Key-based Incremental
Primary Key: funnel_id:date
Contains Nested Structures?:
Yes
mixpanel_funnels table contains contains info about your Mixpanel funnels.mixpanel_funnels & Nested Structures
This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.
These items are marked with a *
Replication
Because of how Mixpanel’s API is designed, this table can only be queried by day. This means that every time Stitch runs a replication job for a Mixpanel integration, the past day’s worth of data will be replicated for this table.
mixpanel_funnels Attributes
While we try to include everything Mixpanel has here, this may not be a full list of attributes. Refer to Mixpanel's documentation for a full list and description of each attribute.
funnel_id
date
steps
*: count, step_conv_ratio, goal, overall_conv_ratio, avg_time, eventanalysis__completion
analysis__starting_amount
analysis__steps
analysis__worst
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.