> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/latest-news/klaviyo-integration-just-got-deeper.md).

# Klaviyo Integration Just Got Deeper

Announces new Klaviyo integration features, including synced segments, event-based triggers, and OAuth setup.

Power smarter automations with new segmentation and event-based triggers.

The Recart <> Klaviyo integration now supports even more powerful workflows — including synced segments, real-time triggers, and a simplified connection process using secure OAuth.

Whether you’re sending targeted SMS campaigns or building cross-channel flows, this update helps you streamline your strategy while keeping data organized.

### What’s included in this update:

* **OAuth connection** — no more manual API keys
* **Subscriber syncing** — emails and phone numbers flow directly into your Klaviyo list
* **Klaviyo segments in Recart** — use synced segments for SMS targeting and flow logic
* **Daily segment syncs** with manual resync option
* **Event-based triggers (on request)** — trigger Recart flows in real time when Klaviyo emails are received or clicked
* **Integration flow builder** — create Klaviyo-triggered Recart flows from scratch

This update unlocks more advanced use cases, like following up SMS after a Klaviyo abandoned cart email, or triggering real-time messages when a subscriber clicks a product link.

*Last updated: September 2025*


---

# 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://help.recart.com/latest-news/klaviyo-integration-just-got-deeper.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.