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

# Common Issues

## Connection issues

<details>

<summary>API key is rejected or returns a permission error</summary>

There are two common causes:

**Wrong key type** — Klaviyo's Public API key is designed for client-side event tracking only and has no read access to account data. Make sure you're using a **Private API key**. In Klaviyo, go to **Settings → API Keys** and create a new Private key.

**Missing scope permissions** — Private API keys in Klaviyo have granular read/write permissions per resource. If the key exists but a specific entity fails, check that read access is enabled for the resources you need (Campaigns, Profiles, Metrics, Flows, Segments, Forms). You can review and update permissions on the key's settings page in Klaviyo.

</details>

## Data discrepancies

<details>

<summary>Metrics analytics numbers don't match what I see in Klaviyo's Reports</summary>

This is expected. Metrics analytics uses Klaviyo's metric aggregates API, which processes raw event counts differently from Klaviyo's own reporting engine. Klaviyo's documentation [explicitly notes](https://developers.klaviyo.com/en/reference/query_metric_aggregates) that metric aggregates are not designed to match the UI. If you need numbers that align with what Klaviyo shows in its Reports section, use the **Campaign performance report**, **Flow performance report**, **Segment performance report**, or **Forms performance report** entities instead — those use the Klaviyo Reporting API and return the same data as the UI.

</details>

## Missing data

<details>

<summary>Placed orders or revenue columns are empty</summary>

Revenue and order metrics are only populated when Klaviyo has attributed those events to a message. If your Klaviyo account hasn't tracked placed order events — or if the attribution window hasn't closed yet — these columns will be blank. Confirm that your Klaviyo account has the **Placed Order** metric configured and that the integration with your store (e.g., Shopify) is active.

</details>


---

# 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/common-issues.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.