Mixpanel (v1)

Mixpanel integration summary

Stitch’s Mixpanel integration replicates data using the Mixpanel Event Export API and Mixpanel Query API. Refer to the Schema section for a list of objects available for replication.

Mixpanel feature snapshot

A high-level look at Stitch's Mixpanel (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Mixpanel

Mixpanel setup requirements

To set up Mixpanel in Stitch, you need:

• Admin privileges. These are required to retrieve your API secret in your Mixpanel account.

Step 1: Retrieve your Mixpanel project timezone and API secret

1. Login to your Mixpanel account.
2. In the dropdown menu in the upper left corner of the page, select the project you want to replicate data from.
3. Hover over the Settings icon in the upper right corner. In the PROJECT SETTINGS portion of the dropdown menu, click on the link with the name of your project.
4. Copy the Project Timezone and API Secret, and paste those values someplace safe to use for the next step.

Step 2: 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. In the API Secret field, paste the API Secret you retrieved from Step 1.
6. In the Attribution Window field, enter the number of days you want your tables’ attribution window to be. For more information on attribution windows, refer to the Replication section.

7. In the Date Window Size field, enter the number of days desired for a date looping window for the exports, funnels, and revenues tables.

   Date looping will return records whose from_date and to_date fall between the number of days in the defined window size.

   Note: If your project has large volumes of events, you may want to set the number of days to 14, 7, or even to 1 or 2 days.

8. Optional: To fetch specific events, enter a comma-separated list of events in the Export Events field. For example: Page Viewed, Signed Up.
9. In the Project Timezone field, paste the Project Timezone you retrieved from Step 1.
10. Optional: To capture new properties automatically in the events and engage tables, check the Select Properties By Default box. Otherwise, new properties will be ignored.

Step 3:

The Sync Historical Data setting defines the starting date for your Mixpanel integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Note: Mixpanel limits the number of days historical data may be accessed, depending on your Mixpanel plan. If you select a Start Date greater than what your Mixpanel account has access to, Stitch may encounter issues with Mixpanel’s API.

For example: If you have a Starter Free Mixpanel plan, you have access to 90 days of historical data (as of 06/5/2020). If you select a Start Date greater than 90 days, Mixpanel’s API may return an error.

Additionally, the Start Date must be less than or equal to 365 days. If a Start Date greater than 365 days is selected, Stitch will reset the Start Date to 365 days during Extraction.

Refer to Mixpanel’s documentation for more info and to check your Mixpanel account’s historical data access limit.

Step 4: 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:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

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.

Step 5: Set objects to replicate

The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.

Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.

• Selection options
• Individual tables and columns
• All tables and columns

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.

Mixpanel replication

Attribution windows and data extraction

When Stitch runs a replication job for Mixpanel, it will use the value of the Attribution Window setting to query for and extract data for tables using Key-based Incremental Replication. An attribution window is a period of time for attributing results to ads and the lookback period after those actions occur during which ad results are counted.

For example: If set to 5 days, Stitch will replicate the past five days’ worth of data for applicable tables every time a replication job runs. While Stitch replicates data in this way to account for updates to records made during the attribution window, it can have a substantial impact on your overall row usage.

Note: If the beginning of the attribution window is earlier than the selected Start Date, the replication will start from the Start Date and no data before that date will be fetched. For example, if you set the Start Date to five days ago and the attribution window to ten days, only the past five days’ worth of data will be replicated.

In the sections below are examples of how attribution windows impact how Stitch extracts data during historical and ongoing replication jobs.

• Historical and full re-replications
• Ongoing replications

  SELECT *
    FROM mixpanel.revenue
   WHERE date >= '2017-07-03 00:00:00'   /* Start Date */
ORDER BY date

  SELECT *
    FROM revenue
   WHERE date >= '2017-09-26 00:00:00'
                              /* max Replication Key value - Attribution Window */
     AND date <= '2017-10-01 00:00:00'
                              /* max Replication Key value from previous job */
ORDER BY date

Attribution windows and row count impact

Due to the Attribution Window, a high Replication Frequency may not be necessary. Because Stitch will replicate data from the past N days during every replication job, recent data will be re-replicated and count towards your row quota.

To reduce your row usage and replicating redundant data, consider setting the integration to replicate less frequently. For example: every 12 or 24 hours.

Hidden fields in Mixpanel

The Stitch Mixpanel integration is not able to discover fields marked as hidden in your Mixpanel account. To ensure the fields you want replicated will be available in Stitch, double-check that they aren’t hidden in your Mixpanel account.

Mixpanel table reference

annotations.project_id = cohorts.project_id

cohort_members.cohort_id = cohorts.id

cohorts.id = cohort_members.cohort_id

cohorts.project_id = annotations.project_id

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.