Klaviyo v2 (Edge)

Configure Klaviyo as a Source in your Pipeline

Perform the following steps to configure your Klaviyo Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Klaviyo v2.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   This page appears only if the selected Destination type is supported in Edge and your Team has an existing Klaviyo v2 Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, Klaviyo v2 Source.

   • In the Connect to your Klaviyo account section, specify the following:

     • Private API Key: The Private API Key with Read access to the required scopes that you obtained from your Klaviyo account.

     • Historical Sync Duration: The duration for which you want to ingest existing data from the Source. From the drop-down, select one of the following:

       • All Time: Hevo fetches all historical data in your Klaviyo account, from January 1, 1970, to the current date.

       • Sync data from a specific date: Hevo fetches historical data starting from the date you specify in the Historical Sync Start Date field.

         

     • Pack Mode: The format in which custom fields from the Person and Event objects are replicated to the Destination. From the drop-down, select one of the following:

       • Unpacked: Each custom field is replicated to a separate column in the Destination.

       • Packed: All custom fields are combined into a single JSON column in the Destination, rather than separate columns for each field. Use this option if the number of custom fields may exceed the Destination’s column limit.

     • Sync Predictive Analytics for Person Object: Enable this option to sync predictive analytics data for the Person object.

       Note: Enabling this option reduces the Klaviyo Profiles API rate limit from 750 to 150 requests per minute.

     • Sync Events for Deleted Profiles: Enable this option to sync Events for profiles that have been deleted from Klaviyo.

   • (Optional) In the Custom Reports section, define one or more custom reports. Each report you define is replicated into its own table in the Destination. To add a report, specify the following:

     

     • Report Name: A unique name for the Destination table where Hevo loads the data for this report.

     • Report Type: The type of Klaviyo data you want to include in the report.

     • Conversion Metric: The metric used to determine the success of a Flow. Applicable only to the Flow report type.

     • Time Interval: The time interval used to group the report data. Default value: Daily.

     • Report Metrics: The metrics you want to include in this report. The available metrics depend on the selected Report Type value.

     • Rollback Window (days): The number of days for which Hevo re-fetches previously ingested report data to capture updated report data. Min: 2 days. Max: 90 days. Default value: 5 days.

   Note:

   • Click Save after configuring each report. Reports that are not saved before you click Test & Continue are not included in the Pipeline.

   • If you add a new custom report or edit an existing one after the Pipeline is created, resync the corresponding object to apply the changes and load the data using the updated configuration.

7. Click Test & Continue to test the connection to your Klaviyo Source. Once the test is successful, you can proceed to set up your Destination.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests historical data for the selected objects based on the Historical Sync Duration specified when creating the Pipeline, and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:

• Campaign

• Campaign List

• Campaign Message

• Campaign Message Send Time

• Campaign Recipient Estimation

• Campaign Tracking UTM Param

• Event

• Flow

• Flow Action

• Flow Action Tracking UTM Param

• Form

• Form Version

• Global Exclusion

• List

• List Exclusion

• List Person

• Person

• Segment

• Segment Person

For all other objects, Hevo ingests the entire data during each Pipeline run.

During each sync, Hevo also re-fetches the custom reports data for the number of days specified in the Rollback Window (days) field to capture any revisions to previously ingested report data. This ensures that your Destination stays up to date.

Klaviyo enforces a rate limit on the number of calls that can be made to its API in a given time period. If this limit is exceeded, a rate limit exception occurs. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---