> 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/integrations/klaviyo.md).

# Klaviyo

#### Step #1: Create your integration

* Get your Public and Private Keys from Klaviyo. You can access your keys by following the steps here: <https://help.klaviyo.com/hc/en-us/articles/115005062267-How-to-Manage-Your-Account-s-API-Keys>

{% hint style="info" %}
Make sure the keys have **Full Access** enabled for **Events** and **Profiles**.\
\
**NOTE:** If you want to **Auto Subscribe** new customers to your list then you will need to also add **Full Access** for **Subscriptions** and **Lists**.
{% endhint %}

* In Zigpoll: Click Settings -> Manage Integrations -> Enable the Klaviyo Integration
* Enter your public and private keys into the input fields and press save.

{% hint style="success" %}
The first time you connect, Zigpoll sends a one-time **Zigpoll Integration Connected** event to your Zigpoll account email. This makes the integration appear in Klaviyo right away — open **Analytics → Metrics** to confirm it's working — instead of waiting for your first survey response to arrive. It's just a setup confirmation; your real survey data flows in as described below.
{% endhint %}

#### Step #2: Collect Your Data

Once your integration has been completed, data will start flowing into your Klaviyo account. If you use our Shopify integration, we will use the user data provided to associate it with the correct email address. If not, but you have an email input field, the results from that field will be used to identify any existing Klaviyo profiles or it will create a new one.

We also capture **phone numbers** from survey responses. If a respondent provides a phone number — either in a dedicated phone-number field or typed into a free-text answer — we add it to their Klaviyo profile in E.164 format (e.g. `+14155551234`); the Shopify customer phone is used when available. When an email is also present, the phone is added to that same profile so you don't end up with duplicates; otherwise we create or update a profile keyed by the phone number. The phone is stored on the profile only — we do not subscribe anyone to SMS marketing.

When someone completes a survey, we send an event to Klaviyo named after that survey — **`[Zigpoll] Completed Survey: <your survey title>`** — so each of your surveys gets its own metric. This event contains the results for that survey. The data is displayed using each Slide's handle as the key. If you would like to change how your data is displayed, you can adjust the handle of each slide individually.

We will also pipe through your customer's average sentiment score and survey results. You can use this sentiment score to create mailing campaigns and trigger other events that will help grow your customer lifetime value.


---

# 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://docs.zigpoll.com/integrations/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.
