Skip to main content

How do I connect Subi with Klaviyo?

Connect Subi to Klaviyo to sync subscribers into a Klaviyo list and send subscription events you can use in flows and segments.

Subi's Klaviyo integration keeps your subscription audience and activity in sync with Klaviyo. Once you connect Klaviyo, Subi automatically adds your subscribers to a dedicated Klaviyo list and sends subscription events — like a subscription starting, pausing, or a payment failing — as Klaviyo metrics, so you can build segments, campaigns, and flows around your subscribers without exporting and importing anything by hand.

How to connect Subi to Klaviyo

In your Shopify admin, open Subi → Settings → Integrations → Klaviyo. If you haven't connected yet, you'll see two ways to connect:

Subi's Klaviyo connection screen with Connect with OAuth and Connect with API keys options

  • Connect with OAuth (recommended). Click Connect with OAuth, sign in to Klaviyo, and approve access. This is the quickest way and keeps the connection secure — you never have to copy any keys.

  • Connect with API keys. Prefer to use keys? Click Connect with API keys, then paste your Public API Key and Private API Key. You'll find both in Klaviyo under Settings → API keys.

Subi's Connect with API keys form with Public and Private API Key fields

What Subi syncs to Klaviyo

As soon as you connect, Subi syncs your subscribers into Klaviyo:

  • Creates (or reuses) a Klaviyo list named Subi in your account.

  • Adds every existing subscriber's email to that list as a Klaviyo profile, and keeps adding new subscribers automatically as they sign up.

  • Matches customers by email, so existing Klaviyo profiles are updated rather than duplicated.

On each synced profile, Subi also keeps a few subscription properties up to date that you can segment on:

  • subi_active_subscriber — whether the customer currently has an active subscription.

  • subi_active_subscription_count — how many active subscriptions they have.

  • subi_next_billing_date — when their next subscription order is due.

Subscription events Subi sends

Beyond the list, Subi sends subscription events to Klaviyo as they happen. Each event becomes a Klaviyo metric you can trigger flows on. In the Events sent to Klaviyo section, the events are grouped into Contract events, Billing events, and Payment recovery events. You can turn each event on or off, use Send test to make a metric appear in your Klaviyo account before any real event fires, and use View example payload to see the exact data each group sends.

Subi's Events sent to Klaviyo settings showing the Contract events, Billing events, and Payment recovery events sections with per-event toggles

Contract events follow the life of a subscription. In Klaviyo they arrive as:

  • Started Subscription — a customer starts a new subscription.

  • Canceled Subscription — a subscription is cancelled.

  • Paused Subscription — a subscription is paused.

  • Resumed Subscription — a paused subscription resumes.

  • Subscription Skipped — a customer skips their next order.

  • Subscription Expired — a subscription expires.

Billing events cover the outcome of each billing attempt:

  • Subscription Billing Succeeded — a subscription order is billed successfully.

  • Subscription Payment Failed — a subscription payment fails.

Payment recovery events tell you how the recovery of a failed payment concluded. The Payment recovery ended event arrives in Klaviyo as the Subscription Recovery Ended metric.

Subi sends Subscription Recovery Ended only when payment recovery ends without the payment being recovered — the last retry has been used and the fallback action (pause, cancel, or skip) has been applied to the subscription, or you've marked the recovery as lost. If the payment is recovered, you get Subscription Billing Succeeded instead, so the two metrics never overlap. The event carries the subscription's details plus a summary of the recovery — why the payment was declined, when the recovery started and ended, how many retries were used, and which action was applied — everything a flow needs to send the right message. To learn how recovery itself works, see How do I recover failed subscription payments with Smart payment recovery?

Subi also sends one event automatically, without a toggle:

  • Upcoming Subscription Order — sent 3 days before a customer's next subscription order is due.

Checking what's been sent

To confirm everything is flowing, open Event history from the integration's More actions menu. It lists every event Subi has sent to Klaviyo, which customer it was for, and whether it succeeded.

Subi's Klaviyo event history page listing events sent, customers, and statuses

Using your Subi data in Klaviyo

Once the list, profile properties, and events are flowing, you can put them to work in Klaviyo:

  • Segments — build audiences from the Subi list or the subscription properties; for example, everyone with subi_active_subscriber set to true, or whose subi_next_billing_date falls in the next three days.

  • Flows — trigger automated emails or SMS off any Subi metric; for example, a win-back flow on Canceled Subscription, a payment-update reminder on Subscription Payment Failed, or a come-back offer on Subscription Recovery Ended when a failed payment couldn't be recovered.

Next steps

Connect Klaviyo from Subi → Settings → Integrations → Klaviyo, send a test event to confirm the connection, then build your first segment or flow. If you run into any trouble connecting, or you don't see your events in Klaviyo, reach out to our support team and we'll help you get set up.

Did this answer your question?