> 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/faq.md).

# FAQ

<details>

<summary>Where do I find my Klaviyo API key?</summary>

In Klaviyo, go to **Settings → API Keys**. Click **Create Private API Key**, give it a name, and set the appropriate read permissions for the data you want to export (e.g., Campaigns, Profiles, Metrics). Copy the key and paste it into Coupler.io when prompted. Do not use your Public API key — it won't work for data exports.

</details>

<details>

<summary>What's the difference between Campaigns and the Campaign performance report?</summary>

The **Campaigns** entity returns metadata about your campaigns — name, channel, status, send time, target lists — but no performance numbers. The **Campaign performance report** returns performance metrics (opens, clicks, conversions, revenue, etc.) grouped by campaign and message. Use Campaigns to audit your campaign setup, and Campaign performance report to measure results.

</details>

<details>

<summary>What's the difference between Campaign performance report, Flow performance report, and Metrics analytics?</summary>

They serve different reporting needs and use different Klaviyo APIs:

* **Campaign performance report** — aggregated stats per campaign (delivery, engagement, conversions). Always returns totals, no time series. Uses the Klaviyo Reporting API — numbers match what you see in the Klaviyo UI.
* **Flow performance report** — same stats but for automated flows, with time-series support (hourly, daily, weekly, monthly). Also uses the Reporting API — UI-aligned.
* **Metrics analytics** — account-wide event aggregation for any standard or custom metric. Uses the metric aggregates API, which processes raw events differently from Klaviyo's reporting engine — results will not match the Klaviyo UI. Use this when you need event-level trends not tied to a specific campaign or flow.

</details>

<details>

<summary>How do conversion metrics work in the Campaign and Flow performance reports?</summary>

You select one or more Klaviyo events (e.g., Placed Order) as your conversion metric. For each event you select, the report adds four columns: `[Metric name] - total` (count), `[Metric name] - rate` (conversions ÷ recipients), `[Metric name] - unique` (unique converters), and `[Metric name] - value` (attributed revenue, only if the event tracks a dollar value). If the value column is empty, the metric doesn't have a $value property in Klaviyo.

</details>

<details>

<summary>Why is my revenue or "Placed Orders" column empty?</summary>

Revenue and order data in Klaviyo only appears when the Placed Order event is actively tracked in your account and attributed to a message. Check that your Klaviyo integration with your store (e.g., Shopify) is enabled and that the Placed Order metric exists under **Analytics → Metrics**. If the metric isn't there, the column will always be empty.

</details>

<details>

<summary>Can I pull data from multiple Klaviyo accounts into one report?</summary>

Yes. Add each Klaviyo account as a separate source within the same data flow, each with its own API key. Then use Coupler.io's **Append** transformation to merge all the data into a single dataset. This is the recommended approach for agencies managing multiple brands.

</details>

<details>

<summary>Can I export more than one year of Metrics analytics data?</summary>

Yes. Coupler.io automatically splits large date ranges into smaller intervals and reassembles the results, so you can set any date range without hitting the API's per-request limit. The only hard constraint is that data older than 5 years is not available through the Klaviyo API.

</details>

<details>

<summary>Can I use Klaviyo data with AI tools?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can send your Klaviyo Report data directly to these tools for automated analysis, recommendations, or content generation based on your email performance.

</details>

{% hint style="info" %}
For a full breakdown of available metrics and dimensions, see [Data Overview](/sources/category/marketing/klaviyo/data-overview.md). For known issues and errors, see [Common Issues](/sources/category/marketing/klaviyo/common-issues.md). For setup and optimization tips, see [Best Practices](/sources/category/marketing/klaviyo/best-practices.md).
{% endhint %}


---

# 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/faq.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.