Release Noteslink
November 2023link
We have completed the migration of the Klaviyo connectors created before August 22, 2023, to the Klaviyo API v2023-07-15. For more information, see our September 2023 changelog.
We have added a new column, integration_object
, to the METRIC
table.
September 2023link
The Klaviyo 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. Klaviyo's priority-first syncs fetch the most recent 7 days' worth of data from EVENT
table. To learn more, see our priority-first sync documentation.
We have upgraded our connector to the Klaviyo API v2023-07-15. New Klaviyo connectors created on or after August 22, 2023, will use the new API version. We have made the following schema changes as part of the upgrade:
We have added the following new tables:
CAMPAIGN_MESSAGE
CAMPAIGN_MESSAGE_SEND_TIME
CAMPAIGN_TRACKING_UTM_PARAM
GLOBAL_EXCLUSION
SEGMENT
SEGMENT_PERSON
We have added the following new columns to the
CAMPAIGN
table:archived
scheduled
send_option_*
tracking_options_is_*
We have added two new columns,
editor_type
andtext
, to theEMAIL_TEMPLATE
table.We have added two new columns,
archived
andtrigger_type
, to theFLOW
table.We have added the following new columns to the
PERSON
table:last_event_date
predictive_analysis_*
subscriptions_*
We have deprecated the following columns from the tables below:
is_segmented
from theCAMPAIGN
table.is_writeable
from theEMAIL_TEMPLATE
table.folder_name
from theLIST
table.email
from theLIST_EXCLUSION
table.customer_filter
andtrigger
from theFLOW
table.
We have deprecated the
INTEGRATION
table. We will sync the data from this table to theMETRIC
table.We now sync the message-related columns to the
CAMPAIGN_MESSAGE
table instead of theCAMPAIGN
table to support the Klaviyo API changes.We have added the
list_id
column as a primary key for theLIST_EXCLUSION
table.The
id
column in theLIST_EXCLUSION
table now has a foreign key relationship to thePERSON
table.
We are gradually migrating all existing connectors to the new API version.
We have added new Quickstart packages for the following connectors:
* 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.
November 2022link
Now, if we persistently receive the 500 Internal Server Error for the Events endpoint from Klaviyo, we only skip the relevant period that returns this error and continue syncing data for the EVENT
table. Previously, the entire sync failed.
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.
January 2022link
We have released a pre-built, dbt Core-compatible data model to combine Shopify e-commerce data with data from marketing connectors. The Shopify Holistic model supports combining Shopify data with email and SMS marketing data from Fivetran's Klaviyo data model. 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.
May 2021link
We have released pre-built, dbt Core-compatible data models for Klaviyo. 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.
December 2018link
Because Klaviyo will be deleting their v1/lists
endpoint in January, we have migrated to the Lists API V2.