> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/klaviyo.md).

# Klaviyo

Use Perkville data in Klaviyo marketing workflows.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

* **Loyalty messages** — Use points earned, points used and balance information in messages.
* **Engagement** — Build reminders about available points, promotions and referral opportunities.
* **Referrals** — Send Perkville referral data to Klaviyo through the configured integration.

## Setup

Contact [Perkville Support](https://docs.perkville.com/overview/support.md) or your Customer Success Representative to confirm access, participating locations, data matching and the workflows for your program. Test the agreed use cases before launch.

## FAQ

### Are campaigns created automatically?

Data sync and campaign configuration are separate. Set the audience, triggers and content in Klaviyo and confirm mapped fields with your CSR.

See the [Klaviyo partner profile](https://partners.perkville.com/partners/klaviyo) for more information.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/integrations/integration-reference/klaviyo.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
