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.
We have added a new column,
status, to the
AUTOMATION_RECIPIENT tables. The column stores the status of a member:
hardfor a hard bounce
softfor a soft bounce
We are gradually rolling out this change to all existing connectors.
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.
We have added two new columns,
unsubscribe_reason, to the
If you’d like to sync your historical data from the
unsubscribe_reason columns, contact our support team.
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*.
* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.
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 now support the
archived value in the
status field of the