> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/marketing/klaviyo.md).

# Klaviyo

Klaviyo is an email and SMS marketing platform for customer engagement and automation. It tracks customer behavior, segments audiences, and powers campaigns and automated flows. Connecting Klaviyo to Coupler.io lets you pull that data into your reporting stack automatically — no manual exports needed.

**Why connect Klaviyo to Coupler.io?**

* Export campaigns, flows, profiles, segments, forms, and performance reports on a schedule
* Send data to Google Sheets, BigQuery, Looker Studio, Excel, or AI tools like ChatGPT and Gemini
* Combine Klaviyo data with other sources — ads platforms, CRMs, e-commerce stores, or other sending tools — using Join or Append transformations
* Build live dashboards without writing a single line of code

**Prerequisites**

* A Klaviyo account (any plan)
* A Klaviyo Private API key with read permissions for the entities you want to export
* A Coupler.io account

## Quick start

{% hint style="success" %}
For campaign or flow performance metrics (opens, clicks, revenue), use the **Campaign performance report** or **Flow performance report** entity. For account-wide event trends, use **Metrics analytics**. For a flat list of your campaigns, profiles, or other objects, use the corresponding core entity.
{% endhint %}

{% stepper %}
{% step %}
**Create a new data flow.** In Coupler.io, click **Add data flow**. Search for and select **Klaviyo** as your source.
{% endstep %}

{% step %}
**Enter your Klaviyo API key.** In Klaviyo, go to **Settings → API Keys** and create a new Private API key. Give it at least read access to the data you need, then paste the key into Coupler.io.
{% endstep %}

{% step %}
**Choose an entity.** Select from the available entities. Report entities (Metrics analytics, Campaign performance report, Flow performance report, Segment performance report, Forms performance report) require a date range and metric selection. Core entities (Campaigns, Profiles, Flows, Segments, Forms) are full exports.
{% endstep %}

{% step %}
**Choose a destination.** Connect a destination — Google Sheets, BigQuery, Looker Studio, Excel, or an AI tool like ChatGPT or Claude — and configure where you want the data to land.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to do a manual run and confirm your data loads correctly.
{% endstep %}
{% endstepper %}

## Available entities

| Entity                      | What it contains                                                                              |
| --------------------------- | --------------------------------------------------------------------------------------------- |
| Metrics analytics           | Event aggregates for any standard or custom metric, broken down by dimensions you choose      |
| Campaign performance report | Delivery, engagement, conversion, and revenue stats grouped by campaign                       |
| Flow performance report     | Delivery, engagement, conversion, and revenue stats grouped by flow, with time-series support |
| Segment performance report  | Segment membership stats (total members, adds, removes) over time                             |
| Forms performance report    | Sign-up form funnel stats (views, submits, closures) over time                                |
| Campaigns                   | All campaigns with status, channel, send time, and list/segment info                          |
| Profiles                    | All subscriber profiles with contact info, consent status, and predictive analytics           |
| Flows                       | All automated flows with trigger, status, and channel details                                 |
| Segments                    | All segments with definition, active status, and membership metadata                          |
| Forms                       | All sign-up forms with status and A/B test configuration                                      |


---

# 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.coupler.io/sources/category/marketing/klaviyo.md?ask=<question>&goal=<endgoal>
```

`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.