Release Notes

April 2026

We have added a new table, PUSH_TOKEN.

We have added the following new mobile push subscription columns to the PERSON table:

• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_CONSENT
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_TIMESTAMP
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHOD
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_METHOD_DETAIL
• SUBSCRIPTIONS_MOBILE_PUSH_MARKETING_CAN_RECEIVE_PUSH_MARKETING

We have added a new toggle, Sync predictive analytics for PERSON table, to the connection setup form to enable or disable syncing all columns with the prefix predictive_analytics_* to the PERSON table. For more information, see our setup instructions.

We have added a new column, predictive_analytics_ranked_channel_affinity, to the PERSON table.

We have added two new options, FORM and SEGMENT to select the custom report type in the connection setup form. You can now select the FORM and SEGMENT custom reports from the Type drop-down menu while configuring your connection in Pack Mode. For more information, see the setup instructions and the REST API Configuration.

March 2026

We have added a new table, ACCOUNT_HISTORY, to store account-level details of Klaviyo accounts for auditing and tracking purposes.

You can now configure a rollback window of 2–90 days for custom reports in Klaviyo connections.

For more information, see our setup guide.

February 2026

We have added two new tables, FORM and FORM_VERSION, to capture form and form version history data for our Klaviyo connector. We are gradually rolling out these changes to all existing connections.

We now sync both active and archived flows for the FLOW table during full syncs. Previously, only active flows were included, which could result in missing data when flows were archived.

December 2025

Our Klaviyo connector now supports source naming feature. For more information, see our setup instructions.

You can now create custom reports using the Klaviyo Reporting API. For more information, see our documentation. For instructions on creating custom reports, see our setup guide.

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.

September 2025

We have updated our connector and will start using the Klaviyo API Revision 2025-04-15 on October 15, 2025. We will be gradually rolling out the changes to all connections. As part of this upgrade, we have made the following schema changes:

CAMPAIGN table

The new API revision supports mobile push campaigns. We will sync these campaigns to the CAMPAIGN table.

• CAMPAIGN_TRACKING_UTM_PARAM table: We have added a new column, type.
• SEGMENT table: We have added a new column, definition.
• EVENT table: We have changed the structure of the property_attribution column. See the comparison between the old structure and the new structure, along with an example below:

{
  "$attributed_event_id": "string",
  "$send_ts": 0.0,
  "$message": "string",
  "$flow": "string",
  "$group_ids": []
}
        

{
  "type": "attribution",
  "id": "string",
  "relationships": {
    "event": {
      "data": {
        "type": "event",
        "id": "string"
      }
    },
    "attributed-event": {
      "data": {
        "type": "event",
        "id": "string"
      }
    },
    "campaign": {
      "data": {
        "type": "campaign",
        "id": "string"
      }
    },
    "campaign-message": {
      "data": {
        "type": "campaign-message",
        "id": "string"
      }
    },
    "flow": {
      "data": {
        "type": "flow",
        "id": "string"
      }
    },
    "flow-message": {
      "data": {
        "type": "flow-message",
        "id": "string"
      }
    },
    "flow-message-variation": {
      "data": {
        "type": "flow-message",
        "id": "string"
      }
    }
  }
}
        

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

July 2025

We now perform rollback syncs with a one-day window for the EVENT table to capture late-arriving records and ensure data accuracy.

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.

July 2024

You can set the limit on how much of the historical data you want to pull for the EVENT table. To do that, select the preferred range from the drop-down menu in the setup form.

Learn more in our Klaviyo documentation.

May 2024

We have added the following new tables and associated child tables:

• COUPON
  • COUPON_CODE
• TAGS
  • CAMPAIGN_TAG
  • FLOW_TAG
  • LIST_TAG
  • SEGMENT_TAG
• TAG_GROUP

We have added the following child tables to the FLOW table:

• FLOW_ACTIONS
• FLOW_ACTION_UTM_PARAMS
• FLOW_MESSAGE

We re-import these tables in every sync. We are gradually rolling out these changes to all existing connections.

We can now pack all the custom fields for the EVENT and PERSON tables into a single JSON file and upsert it into a single column. We have added a new field, Pack Mode, to the connector setup form. The field provides you the option to choose how Fivetran should handle your custom fields. For more information, see our Klaviyo connector documentation.

March 2024

We have added a new column, joined_group_at, to the LIST_PERSON table to store the dates when a person is added to the list.

January 2024

We have migrated all Klaviyo connections created before December 19, 2023, to Klaviyo API v2023-10-15. For more information, see our December 2023 changelog.

We have introduced a new option in our connector setup form that allows you to sync only events associated with active profiles in Klaviyo. By default, we sync events associated with both active and deleted profiles.

December 2023

We have upgraded our Klaviyo connector to Klaviyo API v2023-10-15. Klaviyo connections created on or after December 19, 2023, will use the new API version.

As a part of the upgrade, we have added the following new columns to the PERSON table:

• ip
• subscriptions_email_marketing_can_receive_email_marketing
• subscriptions_email_marketing_can_receive_sms_marketing
• subscriptions_email_marketing_last_updated
• subscriptions_sms_marketing_last_updated

November 2023

We have completed the migration of the Klaviyo connections 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 2023

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 the EVENT table. To learn more, see our priority-first sync documentation.

We have upgraded our connector to Klaviyo API v2023-07-15. New Klaviyo connections created on or after August 22, 2023, will use the new API version. As a part of the upgrade, we have made the following schema changes:

• 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 and text, to the EMAIL_TEMPLATE table.

• We have added two new columns, archived and trigger_type, to the FLOW 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 the CAMPAIGN table.
  • is_writeable from the EMAIL_TEMPLATE table.
  • folder_name from the LIST table.
  • email from the LIST_EXCLUSION table.
  • customer_filter and trigger from the FLOW table.

• We have deprecated the INTEGRATION table. We will now sync the data from this table to the METRIC table.

• We now sync the message-related columns to the CAMPAIGN_MESSAGE table instead of the CAMPAIGN table to support the Klaviyo API changes.

• We have added the list_id column as a primary key for the LIST_EXCLUSION table.

• The id column in the LIST_EXCLUSION table now has a foreign key relationship to the PERSON table.

We are gradually migrating all existing connections to the new API version.

November 2022

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 2022

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

January 2022

We have released a pre-built, dbt Core-compatible data model to combine Shopify ecommerce 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.

May 2021

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.

December 2018

We have migrated to the Lists API V2 because Klaviyo will be deleting their v1/lists endpoint in January.