Release Notes

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.

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

September 2025

We have added a new table, JOURNEY. We are gradually rolling out this change to all existing connections starting September 17, 2025.

We no longer support historicSyncTimeFrame when creating connections using REST API configuration.

August 2025

We have updated the Quickstart packages for the following connectors:

• Amazon Ads to version 1.0.0.
• Asana to version 1.0.0.
• Facebook Pages to version 1.0.0.
• Fivetran Platform to version 2.3.0.
• GitHub to version 1.0.0.
• Greenhouse to version 1.0.0.
• Instagram Business to version 1.0.0.
• Intercom to version 1.0.0.
• Iterable to version 1.0.0.
• Jira to version 1.0.0.
• Klaviyo to version 1.0.0.
• Lever to version 1.0.0.
• LinkedIn Ad Analytics to version 1.0.0.
• LinkedIn Company Pages to version 1.0.0.
• Mailchimp to version 1.0.0.
• Marketo to version 1.0.0.
• Microsoft Advertising to version 1.0.0.
• Mixpanel to version 0.14.0.
• NetSuite SuiteAnalytics to version 1.0.0.
• Pardot to version 1.0.0.
• Pendo to version 1.0.0.
• Pinterest Ads to version 1.0.0.
• Qualtrics to version 1.0.0.
• QuickBooks to version 0.21.0.
• Recharge to version 1.0.0.
• Recurly to version 1.0.0.
• Reddit Ads to version 1.0.0.
• Sage Intacct to version 1.0.0.
• Salesforce Marketing Cloud to version 0.3.0.
• ServiceNow to version 0.5.0.
• Shopify to version 0.21.0.

We have added a new table, LIST_USER. We are gradually rolling out this change to all existing connections.

We will discontinue the email_list_ids column from the USER_HISTORY table on October 13, 2025, because the LIST_USER table contains the same data.

July 2025

We have updated the Quickstart packages for the following connectors:

• Connectors supporting the Ad Reporting data model to version 1.17.0.
• Fivetran Platform Connector to version 2.2.2.
• GitHub to version 0.9.1.
• HubSpot to version 0.26.0.
• Iterable to version 0.14.0.
• Microsoft Dynamics 365 CRM to version 0.1.0-b2.
• Qualtrics to version 0.4.0.
• QuickBooks to version 0.20.1.
• Recharge to version 0.5.0.
• Reddit Ads to version 0.7.0.
• SAP ERP on HANA to version 0.2.1.
• Shopify to version 0.19.1.
• Stripe to version 0.19.2.
• Zendesk Support to version 0.25.0.

February 2025

We have added a new field, Sync data from selected date, under the Historical Sync Time Frame dropdown in the setup form. This allows you to select the exact date up to which the backward sync will occur. The default value is Sync all historical data. You can edit the connection details and update the time frame for an existing connector.

Historical sync time frame limits the amount of data synced for the EVENT table.

We are gradually rolling out this feature to all connections.

November 2024

We have updated the Quickstart packages for the following connectors:

• Amplitude to version 0.5.0
• Apple Search Ads to version 0.4.1
• Facebook Ads to version 0.8.0
• HubSpot to version 0.20.0
• Iterable to version 0.13.0
• Jira to version 0.19.0
• LinkedIn Ad Analytics to version 0.9.1
• Recurly to version 0.5.1
• Reddit Ads to version 0.3.1
• Zendesk Support to version 0.18.1

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

September 2024

We have added a new field, Historical Sync Time Frame, to the connection setup form. This allows you to select how many months' worth of historical data you want to sync. The default value is ALL_TIME. You can edit the connection details and set the time frame value for an existing connection.

We have also added support for the historic_sync_time_frame parameter for connections created using the Create a connection endpoint. For more information, see our REST API config.

The historical sync limit only applies to the EVENT table.

March 2024

We have added support for EU-based Iterable accounts. For more information, see our setup instructions.

February 2024

We now capture deletes for the TEMPLATES_HISTORY table.

December 2023

We have updated the Quickstart package for the Iterable connector to version 0.11.0.

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

September 2023

We have added new Quickstart packages for the following connectors:

• Greenhouse
• Iterable
• Klaviyo
• Marketo
• Mixpanel
• Twitter Organic

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

August 2023

We now support the following types of Iterable projects for connections created on or after August 10, 2023:

• Email-based
• Hybrid
• UserID-based

We have made the following schema changes for the connections created before August 10, 2023:

• We have added a new table, SMS_LINK_PARAM_HISTORY.

• We have added the following new columns to the CAMPAIGN_HISTORY table:

  • message_medium
  • updated_by_user_id

• We have added the following new columns to the EMAIL_TEMPLATE_HISTORY table:

  • cache_data_feed
  • data_feed_id
  • data_feed_ids
  • is_default_locale
  • merge_data_feed_context

• We have added the following new columns to the EVENT_EXTENSION table:

  • browser_token
  • catalog_collection_count
  • catalog_lookup_count
  • city
  • clicked_url
  • country
  • error_code
  • expires_at
  • from_phone_number
  • in_app_body
  • is_sms_estimation
  • labels
  • message_context
  • message_status
  • mms_send_count
  • product_recommendation_count
  • proxy_source
  • reason
  • sms_send_count
  • web_push_body
  • web_push_click_action
  • web_push_icon
  • web_push_message

• We have added the following new columns to the IN_APP_TEMPLATE_HISTORY table:

  • expiration_date_time
  • expiration_duration
  • in_app_display_settings
  • inbox_metadata
  • is_default_locale
  • locale
  • payload
  • web_in_app_display_settings

• We have added a new column, description, to the LIST table.

• We have added the following new columns to the MESSAGE_TYPE table:

  • created_at
  • frequency_cap
  • rate_limit_per_minute
  • subscription_policy
  • updated_at

• We have added the following new columns to the PUSH_TEMPLATE_HISTORY table:

  • buttons
  • cache_data_feed
  • data_feed_ids
  • interruption_level
  • is_default_locale
  • is_silent_push
  • merge_data_feed_context
  • relevance_score
  • rich_media_andriod
  • rich_media_ios
  • title
  • wake

• We have added the following new columns to the SMS_TEMPLATE_HISTORY table:

  • google_analytics_campaign_name
  • is_default_locale
  • tracking_domain

• We have added a new column, iterable_user_id, to the USER_HISTORY table.

• We have deprecated the following columns from the IN_APP_TEMPLATE_HISTORY table:

  • buttons
  • client_template_id
  • content
  • content_version
  • dismissible
  • frequency_cap
  • locale_code
  • message_backend_content_id
  • message_class
  • message_format_id
  • message_format
  • message_id
  • message_name
  • message_type_id
  • messages
  • metadata
  • name
  • state

Iterable connections created on or after August 10, 2023 use a new schema. Find more information about the new schema in our connector overview documentation.

You can now specify the events and custom events that you want to sync when you configure the Iterable connector using our REST API.

May 2023

We have added options to select Events and Custom Event in the connector setup form. You can now select the Events that you want to sync from the list. You can also select specific Custom Event that you want to sync in EVENT table. For more information, see our Sync events documentation.

April 2023

We now sync transactional_data for events. To sync historical data for this column, contact our support team.

December 2022

We now sync the additional_properties column to the EVENT table for all Iterable connections. If you want to sync the historical data for this column, contact our support team.

November 2022

We have added a new column, additional_properties, to the USER_DEVICE_HISTORY table. If you want to sync the historical data for this column, contact our support team.

October 2022

We now sync the following events into the EVENT table:

• emailSendSkip
• inAppSend
• inAppClose
• inAppDelete
• inAppDelivery
• inAppSendSkip
• pushSendSkip
• pushUninstall
• smsSendSkip
• webPushClick
• webPushSendSkip

If you want to sync historical data for these events, contact our support team.

May 2022

You can now select and deselect tables to be synced on the Schema tab of the Connector Details page in your Fivetran dashboard.

We have renamed the unique_emails_opens column to unique_email_opens because Iterable renamed the metric. This change affects the CAMPAIGN_METRICS and EXPERIMENT_METRICS tables. For more information, see Iterable's Unique Email Opens metric release note. We now sync new data into the new unique_email_opens column in the destination tables. Contact our support team if you want to backfill older data in the column. You may experience slow sync speeds when you backfill the older data into the column.

We now sync smsClick events into the EVENT table.

December 2021

We have added a new table, EXPERIMENT_METRICS, that stores the metrics generated for a given experiment on a particular day.

October 2021

We now support the inboxMessageImpression, inboxSession, and purchase events. We sync the data into the EVENT table.

August 2021

We have fixed a bug where Iterable connections created before June 14, 2021, synced the CAMPAIGN_SUPPRESSION_LIST_HISTORY table as CAMPAIGN_SUPRESSION_LIST_HISTORY in the destination. We now sync data to both versions of the table in your destination. Be sure to update your queries.

July 2021

We have released pre-built, dbt Core-compatible data models for Iterable. Find the models 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.

February 2021

We have added a new column, email_list_ids, to the USER_HISTORY table. The email_list_ids column stores details of all the lists (an array of all the List IDs) that a user is subscribed to.

January 2021

You can now exclude the LIST_USER_HISTORY table from your syncs to reduce your MAR usage. On your Connector Details page, go to the Schema tab and deselect the table.

By default, we include the LIST_USER_HISTORY table in your syncs. You may observe data discrepancies if you exclude this table.

March 2020

We now sync custom fields and objects received from the Iterable API and webhooks.

We have added a new field, additional_properties, to the EVENT table. This field stores the custom data (fields and objects) as a JSON object.

January 2020

We have added a new table, IN_APP_TEMPLATE_HISTORY. This table supports In-App templates.

November 2019

The Iterable 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. Iterable's priority-first syncs fetch the most recent seven days' worth of data from the EVENT table.

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

August 2019

We will now be using both webhooks and API connections to perform incremental syncs. This ensures that you will no longer experience missing event data due to webhook timeouts.

March 2019

We no longer sync the previously-deprecated USER_MESSAGE table. You can access the same information from the EVENT table.

February 2019

We have deprecated the USER_MESSAGE table. We will stop syncing this table after March 15, 2019.

We have added a new column, workflow_id, to the CAMPAIGN_HISTORY table.

November 2018

We have replaced the locale_name column with locale in the following tables:

• EMAIL_TEMPLATE_HISTORY
• EVENT_EXTENSION
• PUSH_TEMPLATE_HISTORY
• SMS_TEMPLATE_HISTORY

October 2018

Iterable is a growth marketing and customer engagement platform. It enables brands to create, execute and optimize campaigns across email, push, SMS, in-app and more with unparalleled data flexibility.

Read our Iterable connector documentation.