Klaviyo integration

Extend your Klaviyo flows with bespoke Recurly Commerce subscription events and customer properties—unlock powerful segmentation and personalized messaging.

Overview

Prerequisites & limitations

You must have an active Klaviyo account and the Recurly Commerce / Klaviyo integration enabled in your merchant admin.

Data backfill populates historical customer properties but does not retroactively fire subscription events—only new events after integration will trigger metrics.

Definition

The Klaviyo integration pushes Commerce-specific metrics (e.g., subscription started, billing attempt failed) and customer properties (e.g., active subscriber count, pause status) into Klaviyo. These enrich your Klaviyo profiles and enable bespoke, event-driven flows and segments.

Key benefits

  • Granular subscriber signals: Fire events for every lifecycle milestone—starts, pauses, cancellations, upcoming orders, and more.
  • Rich customer profile: Surface counts of active, cancelled, paused, and skipped subscriptions for precise segmentation.
  • Quick Actions: Embed actionable links (skip next order, reactivate) directly in emails to drive self-service and reduce support tickets.

Key details

Available Recurly Commerce metrics / events

Below is the complete list of Recurly Commerce metrics/events that will be sent to Klaviyo in real time:

Commerce Metric in KlaviyoWhen is it triggered?
Billing Attempt FailedBilling attempt failed
Contract Order Skipped
Gift ConfirmationGift subscription is created/purchased by the shopper.
Gift Confirmation Recipient
Gift Opened
Gift Order Placed
One Time Addon Created
One Time Addon Removed
Order PlacedRenewal order has successfully been placed.
Out Of StockProduct variant is deleted or has 0 quantity left.
Revoked Payment Method
Status UpdateSubscription’s status changes.
Subscription CancelledSubscription is canceled by you in the merchant admin or by the customer in the customer portal.
Subscription StartedSubscription is created/purchased by the shopper.
Upcoming Order3 calendar days before the scheduled upcoming order.

Recurly Commerce metric / event properties

Each event is accompanied by a rich set of properties for granular segmentation:

Metric(s)PropertyTypeDescription
All metrics include the following propertiescharge_amountNumber (e.g. 50)Total amount the shopper paid when the subscription started (includes shipping, tax).
product_titleStringShopify product title.
product_idNumberShopify product ID.
variant_idNumberShopify variant ID.
variant_titleStringShopify variant title.
line_itemsArray<object>Subscription contract line items.
...addonItemsArray<object>Subscription contract add-on items.
nextBillingDateStringSubscription contract next billing date.
order_interval_frequencyNumberNumber relating to “Order Interval Unit” for subscription renewal cadence.
order_interval_unitString“DAY”, “WEEK”, “MONTH”, or “YEAR”.
order_interval_daysNumberNumber of days between renewals.
isPrepaidBooleanTrue if the subscription is prepaid; false otherwise.
...isGiftBooleanTrue if the subscription is a gift; false otherwise.
$valueNumberSubscription contract total charged amount (inc. taxes & shipping).
priceNumberSubscription contract price before discounts.
Additional property for "Subscription Cancelled"cancel_reasonStringReason captured from the cancellation survey.
Additional property for "Status Update"new_statusStringThe new status of the subscription
Additional property for "Billing Attempt Failed"total_retriesNumberNumber of dunning retry attempts (excludes the initial failure).
Additional property for "Upcoming Order"isPrepaidUpcomingChargeBooleanTrue if the upcoming order is a fulfillment only; false if it includes a charge.
Additional property for "Upcoming Order"daysBeforeBillingNumberNumber of days before the next order
Additional property for "Order Placed"order_numberNumberThe number of completed orders at the time the order placed metric fires.

Gift confirmation has several additional properties, which are shown in the below table

Metric(s)PropertyTypeDescription
Gift Confirmationsender_email
sender_first_name
sender_last_name
sender_phone
recipient_email
recipient_first_name
...recipient_last_name
recipient_phone
number_of_deliveries
gift_message
order_number
order_name
...order_internal_id
shipping_method
shipping_price
...shipping_address

Use Case: Leverage these events to create custom segments in Klaviyo (e.g., “All subscribers with paused subscriptions AND billing failures in the last 7 days”) and trigger tailored flows.

Available Recurly Commerce Customer properties

These properties are written to each Klaviyo profile under Custom Properties. These profile properties are updated as new events (e.g., additional subscription) are sent to Klaviyo.

Recurly Commerce Customer PropertyTypeDescription
commerce_is_active_subscriberBooleanTrue if the customer has ≥1 active subscription; false otherwise.
commerce_active_subscription_countNumberTotal number of active subscriptions for this customer.
commerce_status_active_subscriptionsNumberAlias for active subscription count.
commerce_status_cancelled_subscriptionsNumberTotal number of cancelled subscriptions for this customer.
commerce_status_paused_subscriptionsNumberTotal number of paused subscriptions for this customer.
commerce_status_skipped_subscriptionsNumberTotal number of skipped subscriptions for this customer.

Quick actions

Embed “Quick Action” links in Klaviyo emails to let subscribers self-serve common tasks (skip next order, reactivate subscription, add add-ons, etc.).

  1. In Recurly Commerce, navigate to Quick actionsfor Klaviyo, and +Add Quick Action for each action/event you want to track.
  2. Once configured for each lifecycle event (e.g., subscription cancel), Commerce will start to send the required data to Klaviyo, and update the customer profiles.
  3. The Quick action link is now available for use in a campaign as {{person|lookup:'actionName'}} , or a flow as {{event.actionName }}. It is common for merchants to include these actions as buttons in e-mails.

Once clicked, the action executes immediately and the subscriber sees a confirmation message.

Data backfill

Customer properties are backfilled automatically for all existing subscription customers (including migrated).

🚧

Backfilling does not retroactively fire subscription events; only new events post-integration will trigger.

Testing Klaviyo locally

To trial Klaviyo events in your local environment:

  1. Request access to your merchant’s Klaviyo account for testing.
  2. Copy the accounts row from production into your local database and extend the expires_at timestamp.
  3. Update merchantId to your local merchant’s ID.
  4. Trigger subscription events locally—they will appear in the test Klaviyo account.