Release Notes

April 2026

We have added a new column, event_time_ms, to the EVENT table.

October 2025

We unified each connector’s pre-built dbt Core–compatible data models into a single model. It standardizes and documents the Fivetran schemas created in your destination and outputs analytics-ready tables. Previously, most connectors used distinct source and transform models.

July 2025

We have removed the CAMPAIGN table because it is no longer available in the Mixpanel API.

February 2025

We have added a new field, Historical sync time frame, to the connector setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connector, you can edit the connection details and set the time frame value. For more information, see our Historical sync time frame documentation.

We apply the historical sync limit to the EVENT table only.

We are gradually rolling out this feature to all connections.

October 2024

The Mixpanel connector now supports the Hybrid Deployment model. For more information, see our setup instructions.

July 2024

We now support Service Accounts authentication for Mixpanel connections. We support this authentication method to handle Mixpanel's deprecation of the Project Secret authentication method. We recommend that you use the Service Accounts authentication method for both new and existing connections.

April 2024

We now fetch only the historical data for past events until March 1, 2019, for all connections. Connections created after January 2021 already follow this behavior. For connections created before January 2021, we recommend that you trigger a re-sync to backfill the historical data until March 2019.

March 2023

We have changed the primary key of the EVENT table to avoid duplicate events from Mixpanel. We have removed the time column and now use only the _fivetran_id column as the primary key. For event records after July 1, 2021, we calculate the _fivetran_id value as the hash of the insert_id, distinct_id, and name columns. New connections created after March 19, 2023, will support this feature by default. We are gradually rolling out this improvement to all the existing connections.

June 2022

You can now exclude the CAMPAIGNS child table from your syncs. On your Connector Details page, go to the Schema tab and deselect the table.

We now display tables on the Schema tab in a nested parent-child format. If you want to sync a child table, you must include the parent table in the sync.

April 2022

We no longer sync the event_id column to the EVENT table. We now use the system column _fivetran_id to identify unique records. Previously, we used the event_id column to identify unique records.

February 2022

We have added a new optional field, Data Region, to the connector setup form. If your Mixpanel data resides in the European Union, select the Data Region as EU.

September 2021

You can now exclude the following child tables from your syncs:

• ANDROID_INVALID_PUSH_TOKENS
• COLLECTIONS
• DELIVERIES
• JOURNEYS
• MP_INAPP_CAMPAIGNS
• RESPONSES
• SURVEYS
• SURVEY_COLLECTIONS
• SURVEY_RESPONSES

On your Connector Details page, go to the Schema tab and deselect the tables.

August 2021

We have changed our sync strategy and now retrieve events data from Mixpanel using Processing Time event.mp_processing_time_ms. Previously, we used Event Time event.time. During internal performance testing, we observed a reduction in sync time. To ensure data integrity, we have rolled back the EVENT table’s cursor by six days. As a result of this rollback, you may observe a longer sync duration in your next sync.

You can now exclude the following tables from your syncs:

• ANSWER
• ANDROID_DEVICE
• IOS_DEVICE
• TRANSACTION

To exclude these tables, go to the Schema tab of your connector details page and deselect them.

June 2021

We now use the _fivetran_id and time columns as the schema's primary keys to support Mixpanel's deduplication logic. We select the _fivetran_id value based on the following conditions:

• For connections 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's insert_id value as the _fivetran_id value.

• For connections created after November 20, 2020, we use the record's insert_id value as the _fivetran_id value.

We now sync the event.time field as TIMESTAMP_NTZ. Previously, we synced the field as TIMESTAMP_TZ.

January 2021

The Mixpanel connector now supports projects that are hosted in the European Union (EU) region. You can now sync event data from data stores located in the EU.

October 2020

We have released a pre-built, dbt Core-compatible data model for Mixpanel. Find the model in Fivetran's dbt hub or data models documentation. Learn more about our dbt Core integration in our Transformations for dbt Core documentation.

November 2019

The Mixpanel connector now supports priority-first sync. Priority-first syncs fetch your most recent data first so that it's quickly ready for you to use. Mixpanel's priority-first syncs fetch the most recent 15 days' worth of data from the EVENT table.

To learn more, see our priority-first sync documentation.

December 2018

During its initial sync, the Mixpanel connector now syncs 30 days' worth of recent data, followed by alternating syncs of historical and recent data. This ensures that you see your most recent data right away.

June 2018

We have added a new table, CAMPAIGN, which includes campaign names.