> For the complete documentation index, see [llms.txt](https://docs.quanti.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quanti.io/connectors/marketing-connectors/klaviyo.md).
# Klaviyo
Prebuilt reports and definition
***
## Prerequisites
Before connecting Klaviyo to QUANTI, ensure you have:
* **Klaviyo Account**: An active Klaviyo account with at least one campaign sent
* **API Key**: A Private API Key with read access — generate it from **Klaviyo > Account > Settings > API Keys**
* **Permissions**: The key must have read permissions on Campaigns, Lists, Segments, Profiles, and Metrics
***
## Setup Instructions
{% stepper %}
{% step %}
**Authorize Klaviyo Connection**
* Click on **Connect to Klaviyo**
* Enter your Klaviyo Private API Key
* Click **Connect** to validate the connection
{% endstep %}
{% step %}
**Select Prebuilt reports**
* Review the available Prebuilt reports (see section below for details)
* All tables are selected by default — you can deselect tables you don't need
* Recommended: Keep all tables enabled for complete email marketing analytics
* Click **Next**
{% endstep %}
{% step %}
**Finish setup**
* Define a sync period and a lookback window — Click save
* For the first sync, you have the following options:
* Activate auto-sync for recurring syncs based on your sync settings by clicking the switch button
* Launch a historical data recovery by choosing your desired dates in the historical data tab
* Launch a manual sync immediately by clicking the Sync now button
* Wait for the sync to complete. Then navigate to your data warehouse to verify that tables are populated
* Check the connector dashboard for sync status and any potential errors
{% endstep %}
{% endstepper %}
***
## Prebuilt reports
### Dimensions
* **Campaign** : Email campaigns with status (Draft, Scheduled, Sending, Sent, Paused, Canceled), channel, send timestamps, targeted audiences, and send/tracking options as JSON.
* **List** : Contact lists used for campaign targeting, with opt-in process type (single or double opt-in).
* **Segment** : Dynamic segments with their segmentation rule definition (JSON), active status, and processing state.
* **Profile** : Contact profiles with email, phone, external ID, demographics, location details, custom properties, and subscription status per channel — all stored as JSON objects.
### Facts
* **Campaign\_performance\_stats** : Aggregated performance metrics per campaign: recipients, deliveries, opens, clicks, unsubscribes, spam complaints, and derived rates (open rate, click rate, bounce rate, unsubscribe rate).
***
Prebuilt reports and definition
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.quanti.io/connectors/marketing-connectors/klaviyo.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.