> ## Documentation Index
> Fetch the complete documentation index at: https://egentify.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Klaviyo Integration for Egentify

> Connect Klaviyo to Egentify to send chat and ticket events into your flows, and give your AI agent commercial context about the customer it is talking to.

Egentify's AI agent handles customer support across chat, voice, and email. Klaviyo is the only integration that works in both directions with it: Egentify sends chat and ticket events into your flows, and reads back context that helps the agent talk to each customer appropriately.

For the full list of events and how consent is handled, see the [marketing overview](https://egentify.com/docs/integrations/marketing.md).

## Connect Klaviyo

There is no API key to paste. Klaviyo uses a one-click approval flow.

**1. Turn Klaviyo on**

In your Egentify dashboard, go to **Store Settings > Integrations** and toggle **Klaviyo** on.

**2. Click Connect with Klaviyo**

You are sent to Klaviyo to approve the connection.

**3. Approve the permissions**

Approve to return to Egentify, where the card reads **Connected to Klaviyo**.

Klaviyo asks you to grant read access to your account details, customer profiles, events, segments, and metrics, plus write access to profiles and events. Egentify uses the write access to record chat activity and support status, never to change anyone's marketing consent.

## What Klaviyo sends back

With Klaviyo connected, the agent can see commercial context about a signed-in customer: predicted and historic lifetime value, churn risk, average order value, order count, expected next order date, their segments, and their ten most recent Klaviyo events.

It uses this to judge tone and surface relevant products. The agent is instructed never to say any of it out loud, so no customer hears their churn score or segment names read back to them.

> [!WARNING]
>
> This context is only ever read for a customer whose identity is verified through a signed-in storefront session. An email a customer types into chat never unlocks their Klaviyo profile.

If Klaviyo cannot be reached, the agent carries on without the context. You get a less personalised reply, not an error.

## Anonymous visitors

If your storefront already runs Klaviyo's onsite tracking script, Egentify reads the cookie that script has set and attaches it to chat events from visitors who are not signed in, exactly as Klaviyo's own onsite tracking does.

Egentify never creates a Klaviyo identifier of its own. If your store does not run Klaviyo's script, anonymous chat events are simply not sent.

When an anonymous visitor later signs in and verifies, Egentify sends one event linking the two so Klaviyo can merge the history onto the real profile. That link is only ever sent for a verified identity, never for a typed email, because a typed email could pull one person's browsing history onto a stranger.

> [!NOTE]
>
> As with Klaviyo's own tracking, two people sharing a browser share one identifier.

## Disconnecting and reconnecting

**Toggling off** pauses the integration and keeps the connection. Context and events stop.

**Disconnect** removes the connection and revokes Egentify's access on Klaviyo's side.

The connection maintains itself and does not need periodic renewal. If you revoke Egentify's access from inside Klaviyo, the card changes to **Reconnect needed** and **Connection lost**, with a **Reconnect** link, and an amber dot appears on the Integrations tab.

> [!WARNING]
>
> Nothing emails you when a connection is lost. If events stop appearing in Klaviyo, check **Settings > Integrations** first.

## Reliability

Every Klaviyo event carries a unique ID, so a retried delivery cannot fire your flow twice. Events that fail for a temporary reason are retried up to five times.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.