Release Notes

July 2026

We have added a new column, opens_proxy_excluded_unique_opens, to the CAMPAIGN_REPORT table.

May 2026

We have added a new table, CAMPAIGN_VARIATE_COMBINATION_UNSUBSCRIBE, to track multivariate campaign combination-level unsubscribes.

April 2026

We have added the following new columns to the AUTOMATION_EMAIL and CAMPAIGN tables:

• clicks
• subscriber_clicks
• click_rate
• opens
• unique_opens
• open_rate These columns contain report summary statistics sourced from the report_summary object in the Mailchimp API response.

We've added a new table, CAMPAIGN_REPORT.

We've added a new table, CAMPAIGN_CLICK_REPORT.

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.

We have removed the option to select individual e-commerce stores in the setup form. Henceforth, data from all your e-commerce stores will be synced based on the tables selected in your schema.

August 2024

We will sunset the E-commerce store selection feature for all connections on October 31, 2024. As a result, the E-Commerce Stores field in the setup form and the e-commerce parameter API will be removed. If you have configured your connection using our REST API, update the API configuration for your connection.

January 2024

We have added the following new tables:

• CART
• CART_LINE
• CUSTOMER
• ORDERS
• ORDER_LINE
• ORDER_PROMO_CODE
• PRODUCT
• PRODUCT_VARIANT
• PROMO_CODE
• PROMO_RULE
• STORE

We are gradually rolling out these changes to all existing connections.

We now use List webhooks to sync data regarding campaign and automation email unsubscribes in the UNSUBSCRIBE table. During an incremental sync, our connector registers Fivetran webhooks for every list with unsubscribe events triggered from all possible sources. During the initial sync, our connector use the Reports endpoint to sync the UNSUBSCRIBE table for all campaigns and automation emails.

June 2023

We have changed our sync strategy for the UNSUBSCRIBE table. We now perform a daily incremental sync of the table.

We have changed the composite primary key of the UNSUBSCRIBE table and performed a table re-sync to ensure data integrity. The new composite key is a combination of the list_id and member_id columns.

June 2022

We have added a new column, web_id, to the MEMBER table. To sync your historical data from the web_id column, contact our support team.

May 2022

We have optimized the connector to minimize the 503 service unavailable error. This change automatically triggered a full re-sync of the CAMPAIGN_RECIPIENTS table for some campaigns. This re-sync is a one-time occurrence.

April 2022

We have added the following new tables to sync Member Tags and Member Interests:

• INTEREST
• INTEREST_CATEGORY
• INTEREST_MEMBER
• TAG_MEMBER
• TAGS

March 2022

We have fixed a bug where we imported the recipient data for each automated email to the AUTOMATION_RECIPIENT table only once, and in the subsequent syncs, we skipped new email recipient data. Now, if we find new email recipient data, we re-import the AUTOMATION_RECIPIENT table in full.

January 2022

We have added a new column, status, to the CAMPAIGN_RECIPIENT and AUTOMATION_RECIPIENT tables. The column stores the status of a member:

• sent
• hard for a hard bounce
• soft for a soft bounce

We are gradually rolling out this change to all existing connections.

March 2021

The Mailchimp connector now supports table blocking for all Mailchimp tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables.

If you want to sync a child table, you must include the parent table in the sync.

February 2021

We have added two new columns, source and unsubscribe_reason, to the MEMBER table.

If you'd like to sync your historical data from the source and unsubscribe_reason columns, contact our support team.

August 2020

We now prioritize email activity exports based on the amount of email activity that has yet to be synced. This prioritization change should improve the sync progress of email activity exports. Previously, we prioritized exports based on the most recent emails first.

We have released a pre-built, dbt Core-compatible data model for Mailchimp. 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.

May 2020

You can now configure your Mailchimp connector using the Fivetran REST API. This feature is in BETA and available only for Standard and Enterprise accounts.

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

We now support the archived value in the status field of the MEMBER table.