---
title: Understanding the behavior of Klaviyo connector
description: In this article, we will explain everything you need to know to start working properly with our Klaviyo connector.
---
[Skip to content](https://support.dataslayer.ai/understanding-the-behavior-of-klaviyo-connector#main-content)
- [English](https://support.dataslayer.ai/understanding-the-behavior-of-klaviyo-connector)
- [Español](https://support.dataslayer.ai/es/entendiendo-el-comportamiento-del-conector-klaviyo)
English
Show submenu for translations
[](https://www.dataslayer.ai/)
Open main navigation
Close main navigation
- - [English](https://support.dataslayer.ai/understanding-the-behavior-of-klaviyo-connector)
- [Español](https://support.dataslayer.ai/es/entendiendo-el-comportamiento-del-conector-klaviyo)
English
Show submenu for translations
Hello. How can we help you?
- There are no suggestions because the search field is empty.
1. [Knowledge base](https://support.dataslayer.ai/?hsLang=en)
2. [Data Sources](https://support.dataslayer.ai/data-sources?hsLang=en)
July 9, 2025
# Understanding the behavior of Klaviyo connector
## In this article, we will explain everything you need to know to start working properly with our Klaviyo connector.
### How does the Klaviyo connector work?
The Klaviyo connector is designed to give you quick and secure access to your Klaviyo data. Once you've logged into [**Dataslayer**](http://app.dataslayer.ai) and connected your Klaviyo account, you’ll be able to pull key metrics and dimensions directly into your reports.
We'll explain some important details to help you set up your queries correctly from the start.
### Key considerations when using the Klaviyo connector
#### **Multiple account access**
Depending on your Dataslayer plan, you can access multiple Klaviyo accounts using the same email address.
#### **Identifying accounts**
Klaviyo's API only returns the **Public API Key**, so the company name won’t appear during the connection process. However, you will see the account name in the "Your Accounts" section.
You can add the "**Account name**" dimension in your tables to easily differentiate between accounts.
#### Combining metrics and dimensions
Klaviyo’s API restricts how you combine certain metrics and dimensions. Here is what you need to know to avoid errors:
- **Do not mix metrics from different report types**.
For example, you cannot combine *Event metrics* and *Performance metrics* in the same query. This will result in an [**invalid combination error**](https://support.dataslayer.ai/solution-to-incompatible-field-combination-errors?hsLang=en).
- You can combine dimensions from groups like **Account** and **Time** with **one additional group of dimensions**, such as Profile or List.
However, combining *multiple additional groups* in the same query is not supported by the Klaviyo API:
- **Valid combinations**:Account + Time + one group of dimensions.
Example: *Account name* + *Year* + *Profile ID*
- **Invalid combination**: Account + Time + multiple groups of dimensions.
Example: *Account name* + *Year* + *Profile ID* + *List type*
This **behavior** comes from how Klaviyo structures its data and is **external to Dataslayer**.
#### **Query load times**
Some scenarios may significantly increase load times:
1. Including the **"Received Email" metric** if your account has large amounts of data.
2. Using the **"Date" dimension** in the **Campaign/Flow Performance metrics**:Klaviyo's API does not support adding a date segmentation to **Flow** or **Campaign performance reports**. This means that, by default, it is not possible to break down these metrics by Date, Month, or other time-based dimensions in a single query.
However, since some users requested this feature, we implemented a workaround to simulate date segmentation manually. What we do is split your query into multiple API requests.
For example, if you select a *full year* date range and break down by "*Date" dimension*, we will request 365 daily reports one by one to build your result.
This can make the **query take a very long time**, especially because Klaviyo limits the Flow/Performance reports to **2 requests per minute**.
If you find *data discrepancies* when working with **Multi-Metric** or **Flow/Performance reports**, please refer to [**this article**](https://support.dataslayer.ai/understanding-data-discrepancies-on-klaviyo?hsLang=en).
#### How to speed up these queries
If you want to reduce query times when working with Flow or Campaign performance reports:
1. **Remove the date dimensions**, if possible, as it's the simplest way to avoid multiple queries.
2. **Use a larger time dimension**, like “Month”, to reduce the number of requests (for example, 12 instead of 365).
3. **Switch to an Events metrics report**, which allows time dimensions directly in the API, without workarounds.
**If Klaviyo changes its API behavior in the future, we’ll make sure the connector stays up to date.**
As always, please contact us via our live chat on [our website](https://dataslayer.ai/) chat or through our [email](mailto:info@dataslayer.ai) if you still have doubts or questions. We are happy to help!
- [General](https://support.dataslayer.ai/general?hsLang=en)
- [Billing & Pricing](https://support.dataslayer.ai/billing-pricing?hsLang=en)
- [Data Sources](https://support.dataslayer.ai/data-sources?hsLang=en)
- [Blended Connectors](https://support.dataslayer.ai/blended-connectors?hsLang=en)
- [Google Sheets](https://support.dataslayer.ai/google-sheets?hsLang=en)
- [Microsoft Excel](https://support.dataslayer.ai/microsoft-excel?hsLang=en)
- [Spreadsheets](https://support.dataslayer.ai/spreadsheets?hsLang=en)
- [Looker Studio](https://support.dataslayer.ai/looker-studio?hsLang=en)
- [Big Query](https://support.dataslayer.ai/big-query?hsLang=en)
- [API Query Manager](https://support.dataslayer.ai/api-query-manager?hsLang=en)
- [Power BI](https://support.dataslayer.ai/power-bi?hsLang=en)
- [Amazon S3](https://support.dataslayer.ai/amazon-s3?hsLang=en)
- [Amazon Redshift](https://support.dataslayer.ai/amazon-redshift?hsLang=en)
- [Snowflake](https://support.dataslayer.ai/snowflake?hsLang=en#main-content)
- [Marketplace](https://support.dataslayer.ai/snowflake?hsLang=en#marketplace)
- [Google Cloud Storage](https://support.dataslayer.ai/google-cloud-storage?hsLang=en)
- [Database](https://support.dataslayer.ai/database?hsLang=en)
- [Azure SQL](https://support.dataslayer.ai/azure-sql?hsLang=en)
- [Azure Storage](https://support.dataslayer.ai/azure-storage?hsLang=en)
- [Dataslayer Atlas](https://support.dataslayer.ai/dataslayer-atlas?hsLang=en)
- [Morpheus](https://support.dataslayer.ai/morpheus?hsLang=en)
- [AI Looker Studio Analyzer](https://support.dataslayer.ai/ai-looker-studio-analyzer?hsLang=en)
- [Dataslayer MCP](https://support.dataslayer.ai/dataslayer-mcp?hsLang=en)
- [Dataslayer GPT](https://support.dataslayer.ai/dataslayer-gpt?hsLang=en)
- [Dataslayer AI Chat](https://support.dataslayer.ai/dataslayer-ai-chat?hsLang=en)
[](https://dataslayer.ai/)
Dataslayer.ai: Digital Marketing Reporting Made Easy
Copyright © 2026, DATASLAYER SL