> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/technical-integration-guides/integrate-with-klaviyo.md).

# 与 Klaviyo 集成

Klaviyo 是一个品牌用于电子邮件和短信营销的平台。通过此集成，你可以将 impact.com 联盟驱动的操作回传到你的 Klaviyo 账户，作为 Klaviyo 事件。然后，通过在 Klaviyo 中汇总这些事件及其关联的用户资料，你可以利用 Klaviyo 工具来优化电子邮件/SMS 消息工作流。

查看 [面向 Advocate 的 Klaviyo](https://integrations.impact.com/integration-guides/for-brands/advocate/advocate-plugin-integration/klaviyo-for-advocate) 在集成门户中。


---

# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/technical-integration-guides/integrate-with-klaviyo.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.