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

# Klaviyo

<figure><img src="/files/TfSq5rXGyQ0r5sm5usJl" alt=""><figcaption></figcaption></figure>

## Overview

Integrate Novel's wallet passes into your Klaviyo emails. With this integration, you can embed personalized wallet pass URLs in your emails that enable a one-click install. Your customer's don't need to login.&#x20;

To get started, you'll want to get your private API key from the Klaviyo app. You can find it under: <mark style="color:purple;">**Settings -> API Keys -> Create Private API Key -> Full Access Key**</mark>

In Novel, navigate to <mark style="color:purple;">**Integrations -> Klaviyo.**</mark> Enter your API Key, click save, and you're done!&#x20;

<figure><img src="/files/bpEeUmuXkLSv6vwUCoNS" alt=""><figcaption><p>Novel App</p></figcaption></figure>

You'll see the following custom attributes being added to Klaviyo profiles that are Shopify customers. Use the <mark style="color:purple;">**$NovelEmailPassLink**</mark> attribute for emails and the <mark style="color:purple;">**$NovelSmSPassLink**</mark> for SMS outreach.&#x20;

{% hint style="info" %}
It may take some time to update your profiles in Klaviyo, depending on the number of customers you have.&#x20;
{% endhint %}

<figure><img src="/files/HhSeWptECPXJz1UYVYTj" alt=""><figcaption><p>Klaviyo Custom Attributes</p></figcaption></figure>

To use these attributes in emails, insert the following as the image URL. Don't forget to replace the \[yourstorefront] with the URL in your [Novel pass install link. ](/start-guide/distribute-your-pass.md)

We recommend that you use the *add to wallet* images in the [Novel brand kit](https://www.figma.com/file/5u5yQM726XWS0WurrX1Hcw/Novel-Brand-Kit-\(Community\)?type=design\&node-id=0%3A1\&mode=design\&t=ZNsU9QGKuJtPLptM-1) when creating your email and using the below as the URL.&#x20;

```
{{person|lookup:'$NovelEmailPassLink'|default:'https://[yourstorefront].novel.com/email'}}
```

For email design help, refer to the Novel brand kit Figma below.&#x20;

{% @figma/embed fileId="5u5yQM726XWS0WurrX1Hcw" nodeId="0:1" url="<https://www.figma.com/file/5u5yQM726XWS0WurrX1Hcw/Novel-Brand-Kit-(Community)?mode=design&node-id=0:1&t=MzMXOkpt86mMltPm-1&type=design>" %}

***

### Store Credit Balance Attribute

Novel can sync a customer’s store credit balance into Klaviyo as a profile attribute.

Attribute:

```
$NovelStoreCreditBalance
```

You can use this in Klaviyo emails and flows to dynamically display each customer’s balance.

Example:

```
You currently have ${{ person|lookup:'$NovelStoreCreditBalance' }} in store credit.
```

Common use cases:

* Monthly rewards emails
* VIP / loyalty updates
* Store credit reminders
* Winback campaigns

If you do not see this attribute in Klaviyo, contact Novel support to enable store credit syncing.


---

# 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://support.novel.com/integrations/email-and-sms/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.
