Release Status Released Supported By Stitch
Availability Free Status Page Mixpanel Status Page
Default Historical Sync 7 days Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting Mixpanel

Connecting your Mixpanel data to Stitch is a five-step process:

  1. Retrieve your Mixpanel API credentials
  2. Add Mixpanel as a Stitch data source
  3. Define the Historical Sync
  4. Define the Replication Frequency
  5. Select tables to sync

Retrieve Your Mixpanel API Credentials

  1. Sign into your Mixpanel account.
  2. Click Account, which is located in the upper right portion of the screen.
  3. 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.

  4. Your API credentials will display:

    Mixpanel API credentials.

Leave this page open - you’ll need it to complete the setup in Stitch.

Add Mixpanel as a Stitch Data Source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Mixpanel icon.

  4. 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_mixpanel in the destination. Note: Schema names cannot be changed after you save the integration.

  5. 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.

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.

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 help prevent overages, 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 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.

  1. In the Integration Details page, click the Tables to Replicate tab.
  2. Locate a table you want to replicate.
  3. To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.

  4. 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.

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

Stitch's Mixpanel integration includes these tables:


mixpanel_engage

Replication Method: Full Table
Primary Key: distinct_id
Contains Nested Structures?: Yes

The 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.

Table Info & Attributes

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

The mixpanel_export table contains raw event data.

Table Info & Attributes

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

The mixpanel_funnels table contains contains info about your Mixpanel funnels.

Table Info & Attributes

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, event

  • analysis__completion

  • analysis__starting_amount

  • analysis__steps

  • analysis__worst



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.