Loop Subscriptions and Klaviyo: Integration and the Retention Flows to Build

A subscription brand’s most important emails aren’t campaigns. They’re the upcoming order reminder, the failed payment notice and the cancellation save, and all of them depend on data that lives in your subscription app. If Klaviyo can’t see it, those emails come from the subscription app’s default templates, or they don’t come at all.

This guide covers how Loop Subscriptions connects to Klaviyo, what it sends, and the flows to build on it. We’re an official Loop partner and an official Klaviyo partner, and this is how we set it up for clients. Every event, property and setting below is from Loop’s help centre, checked in September 2026.

One thing to clear up first: Loop Subscriptions is not Loop Returns. Loop Returns is a separate returns platform with its own Klaviyo integration, and its help articles often show up in the same search results. Everything here is about Loop Subscriptions (loopwork.co).

---

What Loop is

Loop is a Shopify subscription app for subscribe-and-save, bundles, build-a-box and prepaid subscriptions. It includes a self-serve customer portal, failed payment recovery, cancellation flows and out-of-stock protection. Loop says it’s used by 2,400+ Shopify subscription brands, and its Shopify App Store listing showed a 5.0 rating from 767 reviews in September 2026.

Loop pricing (September 2026):

Plan	Monthly fee	Transaction fee	Notes
Free Forever	$0	None listed	Up to 50 active subscriptions
Starter	$99	1.0%	14-day free trial
Pro	$399	0.75%	Adds prepaid and gifting, API and webhooks, dedicated CSM
Enterprise	Custom	Negotiable

Source: loopwork.co/pricing, September 2026. Loop says it charges no setup, migration or onboarding fees.

Comparing subscription apps? Our Shopify subscription apps guide puts Loop next to Recharge, Skio, Stay AI and others.

---

Connecting Loop to Klaviyo

The connection uses a one-click authorisation, not an API key:

1. In Loop, go to Tools & apps → Apps → Klaviyo and click Connect.
2. On Klaviyo’s authorisation page, click Allow.
3. Click Trigger sample events to send test data, so every event appears in Klaviyo before you build flows on it.
4. Click Sync existing customers to backfill your current subscribers. Loop says this can take 48 to 72 hours.
5. Choose which Loop events count towards Klaviyo’s attributed revenue. Loop recommends excluding negative events such as subscription cancelled.

Loop’s help centre lists the Klaviyo integration on its Starter and Pro plans.

---

What Loop sends to Klaviyo

Events

Loop sends 28 events. In Klaviyo they display with readable names (for example loop_subscription_started shows as Loop subscription started).

Group	Events
Subscription lifecycle	started, paused, resumed, delayed, rescheduled, lines changed, marked for cancellation, cancelled, expired, reactivated
Orders	upcoming order, order processed, order skipped, order unskipped, order out of stock
Billing	billing attempt failed; failed and will be retried; failed and last retry left; payment method expiring
Gifting	gift subscription created, received, completed, upcoming order, thanks sent to gifter
Account	customer account activation, send customer login link, customer data sync, flow completed

Loop retries the subscription created and upcoming order events up to six times if the first send to Klaviyo fails, so those two are reliable triggers.

Profile properties

Loop also writes 18 properties to each subscriber’s Klaviyo profile. The ones we use most:

• $loop_active_subscriber and $loop_active_subscription_count: who’s subscribed right now
• $loop_next_billing_date: when the next charge happens
• $loop_subscribed_line_item_names: what they’re subscribed to
• $loop_subscription_revenue and $loop_processed_order_count: subscriber value and tenure
• $loop_cancelled_subscription_count and $loop_paused_subscription_count: churn history
• $loop_has_bundle: bundle subscribers, who often need different messaging
• loop_customer_portal_link: a link straight into the customer’s portal

Quick action links

Loop provides pre-authenticated links, such as quick_action_update_payment, that let a customer act from an email or SMS without logging in. Use them in dunning and upcoming order emails. Every extra login step loses people.

---

Turning off Loop’s own emails

Loop sends its own notifications by default, including an upcoming order email three days before billing. For each one you rebuild in Klaviyo, switch the Loop version off under Settings → Notification, where each email can be enabled or disabled on its own. Loop confirms that its Notify Customer toggles don’t stop events being sent to Klaviyo, so turning off a Loop email doesn’t break the Klaviyo flow that replaces it.

Do this one email at a time, as each Klaviyo flow goes live, so no customer ends up with zero reminders or two.

---

The flows to build on Loop data

1. Failed payment recovery

Trigger: Loop billing attempt failed and will be retried, and Loop billing attempt failed and last retry left.

This is the highest-value flow in most subscription accounts, because every recovered payment is revenue you already earned. Loop manages the retry schedule itself: you set the number of retries (Loop advertises up to 15) and the days between them, and what happens after the last one (skip, pause or cancel; Loop recommends pause).

Two rules from Loop’s own Klaviyo guidance:

• Split on the retries_left property so the first notice is a calm heads-up and the last-retry notice is clear and urgent.
• Don’t add Klaviyo time delays between emails. Loop’s retry timing already spaces the events out.

Put the quick_action_update_payment link in every message. If you have SMS consent, send an SMS on the last retry.

2. Card expiring

Trigger: Loop payment method expiring.

Loop fires this 30, 15 and 3 days before a card expires, and its own emails can’t send just one of the three. In Klaviyo you can: send the 15-day and 3-day notices and skip the 30-day one if your list finds it too early. Use the update payment quick action link.

3. Upcoming order

Trigger: Loop upcoming order.

Replace Loop’s default reminder with one that does three jobs: confirm what’s coming (loop over event.line_items to show the products), make changes easy (portal link, skip and swap), and add one relevant product with an “Add product” quick action link.

Two limits to know: Klaviyo SMS can’t loop over line items, so SMS reminders should link to the portal instead, and Klaviyo’s dynamic discount codes don’t work on subscription orders.

4. New subscriber onboarding

Trigger: Loop subscription started.

A subscriber doesn’t need your first-purchase welcome series. They need to know when the next order comes, how to skip or swap, and how to use the product well enough to still want it by order three. Filter subscribers out of your one-time buyer post-purchase flow so they don’t get both.

5. Cancellation and win-back

Triggers: Loop subscription marked for cancellation, Loop subscription cancelled.

Loop’s cancellation flow runs inside the portal, in three stages: a benefits page, cancellation reasons, and offers (skip, delay, swap, discount). Klaviyo picks up after that:

• Marked for cancellation: a plain confirmation, and one reminder of the alternatives the customer may have skipped past.
• Cancelled: a win-back sequence 30 to 60 days out, built around the cancellation reason where you have it. Loop’s help centre includes a recipe for a win-back segment built on the cancelled event.

Loop has a compliance mode for US automatic renewal laws. Keep save offers optional and the cancel path clear: a flow that makes cancelling hard creates chargebacks and complaints, not retention. Our win-back flow guide covers timing and offers.

6. Skip, pause and out of stock

• Loop order skipped: a light check-in. Skips are an early churn signal, so tag the profile and watch for a second skip.
• Loop subscription paused: a reminder a few days before it resumes.
• Loop order out of stock: tell the customer before they notice, with a swap option.

7. Gift subscriptions (Pro)

Loop’s gifting events cover the purchase, the recipient’s notification and a thank-you to the gifter. The recipient is a new customer with no history, so treat their first email as a welcome.

---

Segments worth building

• Active subscribers ($loop_active_subscriber is true): exclude them from first-order discount campaigns. Nothing annoys a subscriber like a better offer for strangers.
• High-value subscribers by $loop_subscription_revenue or $loop_processed_order_count: early access and loyalty, not discounts.
• Churn risk: anyone with a paused subscription, a recent skip, or a cancelled count above zero.
• One-time buyers of subscribable products: your subscription conversion audience.

More on the strategy behind these in subscription retention for Shopify brands and our replenishment flow guide.

---

Setup checklist

• Loop connected to Klaviyo and sample events triggered
• Existing customers synced (allow 48 to 72 hours)
• Cancelled and other negative events excluded from attributed revenue
• Failed payment flow split on retries_left, no Klaviyo time delays
• Upcoming order, card expiring and onboarding flows live
• Each Loop notification switched off as its Klaviyo replacement goes live
• Subscribers excluded from first-order discount campaigns

Want it set up or checked? Book a free audit. We’ll review the Loop and Klaviyo connection, your subscription flows and your dunning recovery rate, and send the fixes in writing.

---

Sources

• Loop Help Center, Klaviyo integration (connection, events, properties, retries, September 2026)
• Loop Help Center, Popular use cases in Klaviyo
• Loop Help Center, Customer email notifications
• Loop Help Center, Recovery via retries
• Loop Help Center, Cancellation flows overview
• Loop, Pricing (September 2026)
• Loop Subscriptions on the Shopify App Store
• Klaviyo Marketplace, Loop Subscriptions