# Klaviyo x Smartrr Integration
Last updated: May 14, 2025
{% hint style="warning" %}
**Effective December 28, 2023**, Smartrr now requires both public *and* private Klaviyo API keys for all shops. If youโre an existing merchant who has enabled our Klaviyo integration, please create a private API key from within your Klaviyo admin. For detailed instructions on how to do this, please visit. [Klaviyoโs help documentation](https://help.klaviyo.com/hc/en-us/articles/115005062267). Then, please add this private API key into Smartrr by going to Integrations > Klaviyo > Update. Please complete this action as soon as possible in order to avoid disruption to your Smartrr <> Klaviyo integration.\
\
{% endhint %}
### How it works
Smartrr's integration with Klaviyo can be used in conjunction with or in place of Smartrr's native email [Customer Notifications](/docs/support/subscription-setup/email-subscription-notifications-customer-notifications.md).
The following triggers are available to be passed from Smartrr to Klaviyo:
| Trigger Name | Fired when... |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Smartrr: Subscription created** | **๐** A customer has purchased a brand new subscription from your shop |
| **Smartrr: Subscription upcoming order** | **๐** A customer has an upcoming subscription order in 3 days |
| **Smartrr: Subscription send now** |
๐ฆ A customer has hit Send Now on their next subscription order in their account portal
Note: The "Send now" button ensures the subscription order will be processed at your shop's nextBilling Time. This is different from when Shopify creates the order and an order confirmation email is sent to the customer. When using this trigger in emails, we recommend using language like: "Your order will be processed within the next 24 hours." or "Your order will be processed on the next business day."
|
| **Smartrr: Transaction successful** | **๐ณ** A customer's order has successfully been run during your shop's [*Billing Time*](/docs/support/transactions/billing-schedule.md) |
| **Smartrr: Transaction attempt failed** | **โ** A customer's order has failed during your shop's [*Billing Time*](/docs/support/transactions/billing-schedule.md) |
| **Smartrr: Subscription skipped** | **โญ** A customer or admin has skipped an upcoming order |
| **Smartrr: Subscription unskipped** | **โฎ** A customer or admin has unskipped an upcoming order |
| **Smartrr: Subscription gifted** | **๐** A customer has gifted an upcoming order |
| **Smartrr: Subscription next order date change** | **๐ ** A customer or admin has changed/delayed the date of customer's next order |
| **Smartrr: Subscription product unavailable** | ๐ซ A product in the customer's subscription has become unavailable (out of stock, deleted/archived, etc.) |
| **Smartrr: Subscription canceled** | **๐** A customer or admin has permanently canceled a customer's recurring subscription |
| **Smartrr: Subscription paused** | โธ๏ธ A customer or admin has temporarily paused a customer's recurring subscription |
| **Smartrr: Subscription activated (unpaused)** | **โถ๏ธ** An admin has re-activated a customer's paused subscription in the admin portal |
| **Smartrr: Subscription auto-resume** | โฏ๏ธ Sent 7 days before a paused subscription is set to auto-resume |
| **Smartrr: Loyalty points earned** | ๐บ A customer has earned loyalty points |
| **Smartrr: Bonus points earned** | โ A customer qualifies for a bonus earn event and receives additional points |
| **Smartrr: Successful referral** | ๐ค A customer when someone has successfully used their referral code |
| **Smartrr: Loyalty points redeemed** | ๐ฐ A customer has redeemed some % of their loyalty points |
| **Smartrr: Referral code generated** | ๐งโ๐ป A customer has generated a referral code to be shared |
| **Smartrr: Loyalty Tier Advancement** | โ๏ธA customer has advanced up to the next tier |
### Custom Properties
In addition to passing triggers, the following custom properties will be passed to individual Klaviyo profiles:
#### Customer Context
```
$email: string;
customer_shopify_id?: string;
customer_smartrr_id: string;
active_subscriptions_count: number;
customer_currency: CurrencyCode;
order_count: number;
total_spent: string;
$first_name?: string;
$last_name?: string;
$phone_number?: string;
$address1?: string;
$address2?: string;
$city?: string;
$zip?: string;
$region?: string;
$country?: string;
```
#### Item Context
```
item_variant_smartrr_id: string;
item_variant_shopify_id: string;
item_variant_name: string;
item_variant_image: string;
quantity: number;
currency: string;
price: string;
sku: string;
item_smartrr_id: string;
item_shopify_id: string;
item_image: string;
item_image_small: string;
item_name: string;
```
#### Subscription Context
```
subscription_smartrr_id: string;
subscription_shopify_id: string;
next_order_date: string;
items: string;
item_names: [string];
item_variant_names: [string];
status: string;
frequency_unit: string;
delivery_frequency: number;
payment_frequency: number;
total_estimated_tax: number;
total_discounts: number;
total_line_items_price: number;
total_line_items_price_after_discount: number;
total_estimated_net: number;
total_shipping: number;
shipping_address1: string;
shipping_address2: string;
shipping_province: string;
shipping_province_code: string;
shipping_city: string;
shipping_country: "string;
shipping_country_code: string;
shipping_zip: string;
shipping_first_name: string;
shipping_last_name: string;
cancellation_reason: string;
was_last_subscription: Boolean;
gift_id: string;
gift_email: string;
gift_phone: string;
gift_note: string;
gift_notify_by: string;
```
#### Loyalty Context
```
points_earned: number;
earn_event: string;
earn_date: string;
previous_point_balance: number;
current_point_balance: number;
previousTier: string;
newTier: string;
points_earned: number;
earn_date: string;
previous_point_balance: number;
current_point_balance: number;
referral_code: string;
referral_url: string;
referee_first_name: string;
points_earned: number;
referral_date: string;
previous_point_balance: number;
current_point_balance: number;
```
#### Payment Context
```
order_id: string;
order_shopify_id: string;
payment_id: string;
payment_shopify_id: string;
remaining_retries: number;
payment_id: string;
payment_shopify_id: string;
```
#### Order Context
```
upcoming_order_date: string;
next_date: string;
skipped_date: string;
unskipped_date: string;
```
## Setup
To integrate Klaviyo and Smartrr, grab your public API key from your Klaviyo dashboard under **Account** > **Settings** > **API Keys**.
Your **Public API Key** is pre-generated at the top of the page. Copy this key.
In your Smartrr dashboard, navigate to **Integrations**. Under **Manual Integrations**, find Klaviyo and press **Connect** to enter the public API key you copied from Klaviyo.
Once successfully connected, the triggers [listed above](#how-it-works) will sync as soon as the metric itself fires.
{% hint style="info" %}
Heads up: Since Smartrr syncs real-time information into Klaviyo, make sure to take this into consideration when planning out your Klaviyo flows. For example, a flow triggered by the **Smartrr: subscription created** metric will trigger immediately after someone subscribes, which can result in inundating customers with 3+ emails if they are already receiving both "Welcome" and "Order Confirmation" emails.
{% endhint %}
So that you can immediately begin using all Smartrr-related metrics in your Klaviyo flows, upon successful connection we will immediately create a profile in your Klaviyo **""** that will fire all 11 available triggers once. โ
### Customer Profiles & Payloads
Once your integration is setup and syncing, you'll also be able to view subscription-level metrics detail on customer profiles within Klaviyo.
Click on **Details** to view the payload information that is passed along with each individual metric.
The information in the payload can be referenced as dynamic tags when designing your Klaviyo emails. For example, if you started a flow with the trigger **Smartrr: Subscription created** and wanted to reference one of the events in the payload, use the tag `{{ event.``event_name``}}` replacing `event name` with your desired variable in the body of your email.
If you have a payload in array form, such as **items**, you can loop through the array to find a specific result. [Click here to read more about how to use Klaviyo's dynamic variable tags](https://help.klaviyo.com/hc/en-us/articles/115005084927-Guide-to-Template-Tags-and-Variable-Syntax#event-variables-4).
You can use Klaviyo's preview feature to help locate tags. When in preview mode for a flow email for a customer, click in the information you'd like to populate and the corresponding tag will display. In the below example, we've clicked on the with the dynamic tag for subscription frequency: `{{ event.frequency_unit }}` . When put into the body of an email this will render the word "month" in the customer's email.
---
# 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://help.smartrr.com/docs/support/integrations/klaviyo-x-smartrr-integration.md?ask=
```
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.