A subscriber who cancels after the second box costs you almost all of the acquisition spend it took to get them. Most subscription brands on Loop know that and still run their Klaviyo account like a one-time store: a welcome flow, an abandoned cart flow, a campaign every few days. Setting up Loop Subscriptions with Klaviyo properly means building flows around the subscription itself, the moments before an order ships, when someone skips, when someone tries to leave.
We work with subscription brands on both Loop and Recharge. The broader playbook is in our guide to subscription email marketing. This one is about the Loop side specifically.
Start with the events Loop sends to Klaviyo
Before you build anything, open Klaviyo and look at the metrics list. Once the Loop integration is connected, subscription activity shows up there as events, along with properties on the subscriber profile. That list is your toolbox.
We won't give you exact event names here, because they depend on your Loop version and integration settings, and they change. In general you are looking for events that cover these moments:
- A new subscription is created
- An upcoming order is about to process
- An order is skipped, rescheduled or the product is swapped
- A payment fails
- A subscription is cancelled
- A cancelled subscription is reactivated
Check which of these your Loop integration actually sends. Open a few test profiles and see which properties sit on them, like next order date or subscription status. If an event you need is missing, ask Loop support before you build a workaround in Klaviyo.
The Loop Subscriptions Klaviyo flows we build first
| Flow | Trigger | Job |
|---|---|---|
| Subscription welcome | New subscription | Confirm what they get and when, show how to manage it |
| Upcoming order reminder | Upcoming order event | No surprise charges, easy skip or swap |
| Skip and swap nudges | Skip or reschedule event | Keep the subscriber engaged while paused |
| Failed payment | Payment failure event | Get the card updated before the order is lost |
| Cancellation save | Cancellation event | Catch people who left for a fixable reason |
| Win-back | Cancellation, weeks later | Bring back churned subscribers |
| Subscribe-and-save upsell | One-time order placed | Turn a one-time buyer into a subscriber |
Upcoming order reminders
This is the email that prevents the angriest support tickets. Send it a few days before the order processes. Show what is in the box, the date and the amount. And put a skip link and a swap link right there, above the fold.
That sounds like you're inviting people to skip. You are. A subscriber who skips one month is still a subscriber. One who gets charged by surprise often cancels and asks for a refund in the same message.
Decide who sends this reminder. Loop can send its own notifications, and if Klaviyo sends one too, subscribers get two. We usually move it to Klaviyo so it looks like the rest of the brand's emails, then switch off the Loop version.
Skip and swap nudges
A skip is a signal. Maybe they have too much product at home, maybe they're bored of the flavor. After a skip, send one short email that suggests a swap or a different frequency. If your Loop setup passes the product on the event, you can name it directly. Keep it to one email. Nobody wants a sequence for pressing "skip."
Cancellation save flow
Loop has its own cancellation flow inside the customer portal, with options to pause or swap before someone confirms. Check what yours shows, because the email side should pick up where the portal leaves off, without repeating the same offer.
After the cancel event, we send one email within a day. Plain, from a real person at the brand, asking what went wrong and offering the obvious fix: a longer interval, a pause, a different product. If you store cancellation reasons as a profile property, branch on them. "Too much product" gets a frequency change. "Too expensive" might get a one-time discount on the next order.
Win-back of churned subscribers
A few weeks later, the win-back flow starts. We usually space it out over a month or two with a couple of emails. Lead with something new, a reformulation, a new flavor, a price change, or simply a reminder of what they liked. Link straight to reactivating the subscription where your setup allows it, not to the homepage. Our win-back flow guide covers timing and offers in more detail.
Subscribe-and-save in the post-purchase flow
Your best future subscribers are people who already bought once at full price. In the post-purchase flow for one-time orders, add an email around the time they would be running low. Show the price difference with subscribe-and-save in real numbers from your store, and explain how easy it is to skip or cancel. That second part matters more than the discount for a lot of buyers.
Exclude active subscribers from this flow. Use the subscription status property from Loop, or a segment built on the subscription events, so nobody who already subscribes gets asked to subscribe.
Things that break most often
- Duplicate notifications. Loop and Klaviyo both sending the same reminder or confirmation. Audit both before going live.
- Subscribers in one-time flows. A subscriber's renewal order can trigger a "thanks for your first order" email. Filter subscription orders out of the regular post-purchase and review flows where needed.
- Campaigns that ignore status. Sending a "try us" discount to active subscribers is a quick way to get support asking why they pay more. Build segments on subscription status and use them in campaigns. Our segmentation guide shows how.
- Stale test data. Test every flow with a real test subscription and check the event actually fires before you switch it on.
Questions we get a lot
Does Loop Subscriptions integrate with Klaviyo?
Yes. Loop has a Klaviyo integration that passes subscription events and subscriber data into Klaviyo. Which events and properties come through depends on your Loop setup, so check the integration settings and the metrics list in Klaviyo before you build flows.
Which Loop events can trigger a Klaviyo flow?
Typically things like a new subscription, an upcoming order, a skipped or changed order, a cancellation and a failed payment. Look at the metrics Klaviyo actually receives from Loop in your account and use those exact events as triggers.
Should Loop or Klaviyo send the upcoming order reminder?
Pick one sender so subscribers don't get the same reminder twice. We usually move customer-facing reminders into Klaviyo so they match the brand's other emails, and turn off the matching notification in Loop.
How do I win back cancelled Loop subscribers?
Run a win-back flow triggered by the cancellation event, starting a few weeks after the cancel. Lead with what changed or a reason to restart, and link straight to reactivation instead of the homepage.