Directory
DevelopersSupportContact usBook demo
Start typing to search…

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 (Prive) 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 Prive-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:

Prive Metric in KlaviyoWhen is it triggered?
Prive Subscription StartedThis metric is triggered when a subscription is created/purchased by the shopper.
Prive Subscription CancelledThis metric is triggered when a subscription is canceled by you in the merchant admin or by the customer in the customer portal.
Prive Subscription PausedThis metric is triggered when a subscription is paused by you in the merchant admin or by the customer in the customer portal.
Prive Status UpdateThis metric is triggered when a subscription’s status changes.
Prive Billing Attempt FailedThis metric is triggered when a billing attempt failed.
Prive Upcoming OrderThis metric is triggered 3 calendar days before the scheduled upcoming order.
Prive Gift ConfirmationThis metric is triggered when a gift subscription is created/purchased by the shopper.
Prive Out of StockThis metric is triggered when a product variant is deleted or has 0 quantity left.
Prive Order PlacedThis metric is triggered when a renewal order has successfully been placed.

Recurly Commerce metric / event properties

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

Metric(s)PropertyTypeDescription
Prive Subscription Startedcharge_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.
…next_billing_dateStringSubscription 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.
…is_prepaidBooleanTrue if the subscription is prepaid; false otherwise.
…valueNumberSubscription contract total charged amount (inc. taxes & shipping).
…priceNumberSubscription contract price before discounts.
– Prive Subscription Cancelledcancel_reasonStringReason captured from the cancellation survey.
– Prive Billing Attempt Failedtotal_retriesNumberNumber of dunning retry attempts (excludes the initial failure).
– Prive Upcoming Orderis_prepaid_upcoming_chargeBooleanTrue if the upcoming order is a fulfillment only; false if it includes a charge.
– Prive Gift Confirmationorder_numberNumberThe number of completed orders at the time the gift confirmation metric fires.
– Prive Out of Stock(same as above properties)……
– Prive Order Placedorder_numberNumberThe number of completed orders at the time the order placed metric fires.

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:

Recurly Commerce Customer PropertyTypeDescription
prive_is_active_subscriberBooleanTrue if the customer has ≥1 active subscription; false otherwise.
prive_active_subscription_countNumberTotal number of active subscriptions for this customer.
prive_status_active_subscriptionsNumberAlias for active subscription count.
prive_status_cancelled_subscriptionsNumberTotal number of cancelled subscriptions for this customer.
prive_status_paused_subscriptionsNumberTotal number of paused subscriptions for this customer.
prive_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 the Prive merchant admin, configure a quicklink with a name and an action.

  2. After the next Prive metric fires (e.g., upcoming order or cancelled), the quicklink appears in the customer’s Klaviyo profile.

  3. Reference the quicklink in a Klaviyo flow using the variable syntax {{ event.extra.quicklink_name }}.

    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.

Updated about 8 hours ago