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

# Klaviyo

<div align="left"><figure><img src="/files/HL7dSYj2qMuhQvZhXVnv" alt="" width="188"><figcaption></figcaption></figure></div>

## Sending AB Tasty campaign data to Klaviyo

#### What this integration does

When AB Tasty assigns a visitor to a campaign and variation, the integration updates two fields on the user’s Klaviyo profile — only if the user is identified in Klaviyo:

* `abtasty_campaign` → the campaign name (and ID)
* `abtasty_variation` → the variation label (e.g., `A`, `B`, `Control`) and ID      &#x20;

That’s it. We don’t create lists, segments, or events for this push.

***

### Requirements

* Your site loads the Klaviyo onsite script and identifies users after signup/login.
* AB Tasty tag is loaded on your website
* Access to AB Tasty → **Settings** → **Integrations**.

***

### Turn it on (AB Tasty)

1. Go to **Settings** → **Integrations** → **Klaviyo**
2. Click **Create Connector**
3. Give your connector a name
4. To finalise, click **Create**

***

### Check it works (Klaviyo)

1. Launch a small AB Tasty test with two variations.
2. Visit the page as a known user (ensure your site calls Klaviyo `identify`).
3. In Klaviyo → **Profiles**, open your test profile\
   under **Profile properties**. You should see:
   * `abtasty_campaign = [campaignID] Your Campaign Name`
   * `abtasty_variation = [VariationID]Variation Name`&#x20;

<figure><img src="/files/2Utw4n9coCHl6T1Imf6X" alt=""><figcaption></figcaption></figure>

If nothing appears, confirm the user is identified, the integration is enabled, and scripts load in the right order.

***

### Use it in Klaviyo

Segment by exposure

* *Properties about someone* → `abtasty_campaign` equals `HP Hero Test`
* *AND* `abtasty_variation` equals `B`

Branch a flow

* Conditional Split → `abtasty_variation` equals `A` → send version A content, otherwise version B.

Create a report based on AB tasty variation & campaigns

* Get the profile exposed to your several AB tasty campaigns


---

# 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.abtasty.com/integrations/push-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.