Klaviyo is a powerful ecommerce platform that lets you boost your business revenue. It offers features like trend reports, cohort analysis, and various options for boosting customer engagement.
This document guides you in setting up Klaviyo as a source in RudderStack. Once configured, RudderStack automatically ingests your Klaviyo data and routes it to your specified data warehouse destination.
To set up Klaviyo as a source in RudderStack, follow these steps:
- Log into your RudderStack dashboard.
- Go to Sources > New source > Cloud Extract and select Klaviyo from the list of sources.
- Assign a name to your source and click Next.
Enter the following connection settings to set up the Klaviyo source:
The connection settings are described below:
- API Key : Enter your Klaviyo Private API key. You can find it in your Klaviyo dashboard by clicking your organization name and going to Account & billing > Settings > API Keys.
- Start Date: Select the date from when RudderStack ingests your Klaviyo data.
The following settings specify how RudderStack sends the data ingested from Klaviyo to the connected warehouse destination:
- Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Klaviyo data into it.
- Schedule Settings: RudderStack gives you three options to ingest the data from Klaviyo:
- Basic: Runs the syncs at the specified time interval.
- CRON: Runs the syncs based on the user-defined CRON expression.
- Manual: You are required to run the syncs manually.
You can choose the Klaviyo data you want to ingest by selecting the required resources:
The below table mentions the syncs and API endpoints supported by these resources from Klaviyo to your warehouse destination:
|Resource||Full Refresh sync||Incremental sync||Primary key||Klaviyo API endpoint|
Klaviyo is now configured as a source. RudderStack will start ingesting data from Klaviyo as per your specified schedule and frequency.
You can further connect this source to your data warehouse by clicking on Add Destination, as shown:
You can connect only one data warehouse destination per Cloud Extract source. If you wish to send data to multiple warehouses, you can configure multiple Cloud Extract sources with the same settings and connect them to each data warehouse.
Yes, it is.
RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.