# Klaviyo

Connect The Wallet Crew with [Klaviyo](https://www.klaviyo.com/) to enrol 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://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2FumoDQBbPiQ6niTjMjein%2Fimage.png?alt=media&#x26;token=e151f4dc-72e2-437f-9015-b1743403cdaf" alt=""><figcaption></figcaption></figure>

Klaviyo stays in charge of segments, flows, and campaigns. The Wallet Crew executes wallet actions and emits wallet lifecycle signals.

<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).

## How the integration works

Klaviyo is the orchestration layer. The Wallet Crew is the wallet execution layer.

{% 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 %}

### More information

The pages below cover the full connector lifecycle, from configuration to campaign building and debugging.

* [Setup](https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo/setup): API keys, connector settings, profile sync, and list subscription behavior.
* [User guide](https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo/user-guide): marketer patterns for segments, flows, and pass download links.
* [Events & data model](https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo/events-and-data-model): reference for lifecycle metrics and profile properties.
* [Klaviyo actions](https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo/actions): link patterns and wallet-side actions triggered from flows.
* [Extensibility](https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo/extensibility): advanced patterns such as multi-list routing and rollout guidance.

## 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>Who owns campaigns and deliverability?</strong></summary>

Klaviyo owns campaigns, templates, and deliverability settings.

The Wallet Crew owns wallet issuance, wallet updates, and wallet-side events.

</details>

<details>

<summary><strong>What enables personalized pass links?</strong></summary>

Personalized pass links are built on `neostore.authenticationToken`.

This token is synced into Klaviyo profiles by the profile sync flow.

</details>

<details>

<summary><strong>Can existing Klaviyo profiles be back-populated with pass links?</strong></summary>

Yes. A Klaviyo flow can call a webhook to sync `neostore.authenticationToken` for existing profiles.

This avoids waiting for a new registration event to start using pass links in campaigns.

</details>

<details>

<summary><strong>How do Klaviyo list subscriptions work with The Wallet Crew?</strong></summary>

Subscription updates can be driven by consent captured in The Wallet Crew enrolment forms.

This keeps consent collection and wallet enrolment in one place, while list membership remains managed in Klaviyo.

</details>

<details>

<summary><strong>Which data should be checked first when a segment looks wrong?</strong></summary>

Start by checking profile properties for wallet status and the token. Then check if lifecycle metrics are ingested.

The fastest validation is inspecting one synced profile and one recent event in Klaviyo.

</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.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.thewalletcrew.io/connect/marketing-automation/klaviyo.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.