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

# Klaviyo Segmentation

Build Klaviyo segments from Zigpoll survey completions and answers

Create a custom segment in Klaviyo containing all users who have completed a Zigpoll survey. This lets you target survey respondents with specific email campaigns and flows.

#### Prerequisites

Make sure you have the [Klaviyo integration](/integrations/klaviyo.md) set up and data flowing into your Klaviyo account.

#### Creating a Zigpoll Segment

1. Log into **Klaviyo** → Click **Lists & Segments**.
2. Click **Create List/Segment**.
3. Select **Segment**.
4. Give the segment a name, like **Zigpoll Users**.
5. Under Definition, select: **What someone has done (or not done)**.
6. Select **Completed a Zigpoll** from the dropdown.
7. Create the segment.

You now have a custom segment containing all users in Klaviyo who have completed a Zigpoll survey. You can use this segment to:

* Send follow-up campaigns to survey respondents
* Exclude survey respondents from certain flows
* Build lookalike audiences based on respondent profiles


---

# 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.zigpoll.com/tutorials/klaviyo-segmentation.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.