> ## Documentation Index
> Fetch the complete documentation index at: https://help.emaillove.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Klaviyo

> Connect Klaviyo to Builder, export emails, and understand its reporting support and limits.

Builder exports HTML, hybrid editable regions, or native drag-and-drop templates. Verified exports support safe updates.

## Connect Klaviyo

Workspace owners and admins connect this integration.

1. Open **Integrations** in Builder and choose **Klaviyo** under **Email service providers**.
2. Give the connection an **Account name** your team will recognize, then enter the details below.
3. Save the connection. For another account on the same platform, choose **Connect another account** and give it a recognizable name.

![Builder connection form for Klaviyo](https://mintcdn.com/emaillove/qYrzRKTscc4O0qPw/images/builder/guides/connect-klaviyo.jpg?fit=max\&auto=format\&n=qYrzRKTscc4O0qPw\&q=85\&s=ffaddd3a7ac1e75632cee6010feed5a5)

The Klaviyo connection form in Builder. Enter your own account details; no credentials are shown in this example.

| Field | What to enter |
| - | - |
| **Private API key** | A private key with template read/write permissions for exports. Reporting needs separate read permissions. |

Saved secrets are not shown again. Leave a saved secret blank to keep it, or enter a new value to replace it. Credentials saved only in the Figma plugin do not connect the Builder account.

Use **Where to find these** in the connection panel for [the provider’s setup guidance](https://help.klaviyo.com/hc/en-us/articles/115005062267).

## Export from Builder

Open an email, click **Export**, choose **Klaviyo** and the account, then review the format and destination options. The [detailed Klaviyo export guide](https://help.emaillove.com/builder/sending/klaviyo.md) covers formats, provider previews where available, verified updates and limitations.

Builder checks the destination against its last verified export before updating it. If it has changed, review it in the platform or create a new copy. There is no force-overwrite option.

Check the destination after export and finish your sending setup in the platform. An export does not send a campaign. If Builder says **Check your ESP before retrying**, inspect the destination before exporting again. See [Exporting and plans](https://help.emaillove.com/builder/sending/esps.md).

## Email reporting in Builder

Email campaign totals for a fixed UTC range based on when messages were sent. Flow reporting and revenue are not included.

1. Open **Reports** → **Email performance**, choose a design system and click **Manage insight settings**.
2. Choose this **ESP account**. Its reporting options load automatically.
3. Choose a campaign from the source picker.
4. Click **Save and load results** to save your selection and queue the import. The account needs reporting permission separately from export access.
5. Click **Update now** in the report for a manual refresh, or enable **Sync ESP results** and save for refreshes every six hours.

**Use results in AI assistance** is a separate, default-off switch. Reporting does not access or change contacts, recipient events or clicked destinations. Reports remain scoped to the authorized workspace and design system.

See [Email insights and reporting](https://help.emaillove.com/builder/reports/email-insights.md) for date windows, unknown metrics, AI use, privacy and deletion controls.

## Troubleshooting

* **Connection rejected:** check the credentials and any region or endpoint against the account you want to use. Update saved secrets in Integrations if they have changed.
* **Wrong destination:** check the selected account before exporting or choosing a report source.
* **Exports work but reporting fails:** save your source selection and run **Check reporting access**. Check reporting permissions and the source ID. Do not grant contact access to work around a reporting limitation.

[All Builder integrations](https://help.emaillove.com/builder/integrations/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.