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

# Klaviyo

Connect Klaviyo to Apple Wallet and Google Wallet passes in The Wallet Crew: send pass download links, sync wallet lifecycle signals and update lists.

Connect The Wallet Crew with [Klaviyo](https://www.klaviyo.com/) to enroll more customers in **Apple Wallet and Google Wallet**, and to trigger lifecycle messaging based on wallet adoption.

This integration connects Klaviyo customer journeys to mobile wallet passes. It supports loyalty cards, gift cards, offers, and other pass-based programs. Wallet adoption and lifecycle become visible in Klaviyo for targeting and reporting.

<figure><img src="https://3852727835-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlP7d71aYydav6e0pRkxc%2Fuploads%2Fgit-blob-296d2def3ed39fb828421a5412a818ee8801ae6c%2Fklaviyo-overview-illustration.png?alt=media" alt="Klaviyo connected to The Wallet Crew to distribute and track Apple Wallet and Google Wallet passes"><figcaption><p>Klaviyo keeps segments, flows, and campaigns. The Wallet Crew executes the wallet actions and returns lifecycle signals.</p></figcaption></figure>

<details>

<summary><strong>Real-world examples</strong></summary>

* A reminder campaign targets customers who have not installed the pass yet.
* A welcome flow starts right after a pass is installed.
* An enrolment form syncs consent into a Klaviyo list subscription.
* A wallet notification is sent for a birthday, with an exclusive offer.

</details>

## Use cases

This integration supports these common scenarios.

* Store pass installation status inside Klaviyo profiles.
* Send emails with a link to download the pass.
* Trigger flows from wallet lifecycle events (registration, install, uninstall).
* Subscribe profiles to Klaviyo lists from The Wallet Crew enrolment form, based on consent.
* Trigger wallet-side actions from Klaviyo flows (pass update, notifications).

Personalized pass links are built on the profile property `neostore.authenticationToken`, synced into Klaviyo profiles by the profile sync flow. The prefix `neostore` is the platform's former name and is kept in technical identifiers.

## How the integration works

{% stepper %}
{% step %}

#### Klaviyo → The Wallet Crew

Klaviyo flows can call webhooks. These webhooks can sync profile data and trigger wallet actions.
{% endstep %}

{% step %}

#### The Wallet Crew → Klaviyo

The Wallet Crew sends wallet lifecycle events and maintains profile properties used for segmentation.

Enrolment flows can also subscribe profiles to a Klaviyo list, based on consent.
{% endstep %}
{% endstepper %}

## Pages in this section

The pages below cover the connector from configuration to campaign building and lookup.

* [Setup](/connectors/marketing-automation/klaviyo/setup.md): API keys, connector settings, profile sync, and list subscription behavior.
* [User guide](/connectors/marketing-automation/klaviyo/user-guide.md): marketer patterns for segments, flows, and pass download links.
* [Reference](/connectors/marketing-automation/klaviyo/reference.md): link patterns, webhook endpoints, lifecycle metrics, profile properties, list subscriptions and script hooks.

## FAQ

<details>

<summary><strong>Is this integration required to start distributing passes by email?</strong></summary>

No. Pass links can be sent without Klaviyo.

Klaviyo makes distribution easier at scale through segmentation, automation, and analytics.

</details>

<details>

<summary><strong>Is SMS supported?</strong></summary>

Yes, when Klaviyo is used for SMS delivery.

The same personalization approach applies, including pass links based on the synced token. Syncing SMS consent to a list needs `EnableSmsSupport`: see the [Reference](/connectors/marketing-automation/klaviyo/reference.md#list-subscriptions).

</details>


---

# 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.thewalletcrew.io/connectors/marketing-automation/klaviyo.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.