May 2022link
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 2021link
We have added a new table, EXPERIMENT_METRICS, that stores the metrics generated for a given experiment on a particular day.
October 2021link
We now support the inboxMessageImpression, inboxSession, and purchase events. We sync the data into the EVENT table.
August 2021link
We have fixed a bug where Iterable connectors 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 2021link
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 2021link
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 2021link
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 2020link
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 2020link
We have added a new table, IN_APP_TEMPLATE_HISTORY. This table supports In-App templates.
November 2019link
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 of data from the EVENT table.
To learn more, see our priority-first sync documentation.
August 2019link
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 2019link
We are no longer syncing the previously-deprecated USER_MESSAGE table. You can access the same information from the EVENT table.
February 2019link
- The
USER_MESSAGEtable is deprecated. We will stop syncing this table after March 15, 2019. - Added new field
workflow_idtoCAMPAIGN_HISTORYtable.
November 2018link
We have replaced the locale_name field with locale in the following tables:
EMAIL_TEMPLATE_HISTORYEVENT_EXTENSIONPUSH_TEMPLATE_HISTORYSMS_TEMPLATE_HISTORY
October 2018link
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.