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.

Define the Historical Sync

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 daysto 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

Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the Replication Scheduling documentation for more information.

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.

Stitch offers two methods of creating a replication schedule:

Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.

Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

A Replication Frequency of at least one hour is required to use anchor scheduling.

An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

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.

Replication will continue after the seven days are over. If you’re no longer interested in this source, be sure to pause or delete the integration to prevent unwanted usage.

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.

mixpanel_export

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.

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.