Segment and target your audience in both flows and campaigns with subscription-specific triggers.

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

How it works

Smartrr's integration with Klaviyo can be used in conjunction with or in place of Smartrr's native email Customer Notifications.

The following triggers are available to be passed from Smartrr to Klaviyo:

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;

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 will sync as soon as the metric itself fires.

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 "hello@smartrr.com" 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.

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.