> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/zap-post-integrations/klaviyo.md).
# Klaviyo
Summary functionality:
* Collect recipient data from Klaviyo Lists and Segments.
* Map to ZAP-POST Campaign.
* Map any custom fields you have set up in the ZAP-POST Campaign.
* Events are added to Klaviyo profiles.
Integration to Klaviyo is directly available from your ZAP-POST account, once signed in.
When a campaign is created, connect Recipient data via “Data Sources” from within the app, you will be directed to Klaviyo to authorise the integration.
Set up is self-service whilst ZAP-POST’s “Tech-Sherpas” will assist and manage the set up where required, at no additional cost. Alternatively, watch the [video](https://zappost.com/academy/lessons/how-to-use-our-klaviyo-integration/).
{% hint style="info" %}
Integration to Klaviyo can be self-service but if you need any help, ZAP-POST support will assist and manage the setup where required, at no additional cost. Start a web chat from within the app, or send an email to support\@zappost. Alternatively, watch the instructional [video](https://zappost.com/academy/lessons/how-to-use-our-klaviyo-integration/).
{% 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://userguide.zappost.com/zap-integrations/zap-post-integrations/klaviyo.md?ask=&goal=
```
`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.