Key takeaways
- Recharge, Loop, Skio and Stay AI name a new subscription four ways in Klaviyo: "Subscription started on ReCharge", loop_subscription_started, "Skio: New Subscription Created" and "Retextion - Subscription Started".
- Stay AI still sends every Klaviyo metric with the "Retextion" prefix, its old company name, per its help center in September 2026.
- Smart sending skipped an order email for most qualifying orders at one of our brands, because a loyalty points email fired a minute after every order.
Every subscription flow in Klaviyo hangs off one event the app sends. Get the name wrong and the flow sits there, Live, with no entries. Nothing errors.
After a supplement brand we moved from Appstle to Loop went live, we found no Klaviyo flow covering failed payments, and Loop's own payment emails had stopped in September. Every retry that month went out with no email. That is what a missed event costs.
So here is every event name for Recharge, Loop, Skio and Stay AI, and which flow runs on which. Each name is copied from the app's own Klaviyo doc, checked on 1 November 2026. Nothing is guessed. The tool choice sits in our subscription apps guide.
The Klaviyo event map: same moment, four names

| Moment | Recharge | Loop | Skio | Stay AI |
|---|---|---|---|---|
| Subscription started | Subscription started on ReCharge | loop_subscription_started | Skio: New Subscription Created | Retextion - Subscription Started |
| Upcoming order | Order upcoming on ReCharge | loop_upcoming_order | Skio: Billing Reminder Notification | Retextion - Order Upcoming |
| Payment failed | Charge processing failed on ReCharge (seen in Klaviyo, not on the metrics page) | loop_billing_attempt_failed | Skio: Billing Attempt Failed | Retextion - Billing Attempt Failed |
| Card expiring | Not listed | loop_payment_method_expiring | Skio: Card Expiration Notification | Retextion - Payment Method Expiring |
| Skipped | Not listed | loop_order_skipped | Skio: Subscription Skipped | Retextion - Subscription Skipped |
| Paused | Subscription paused on ReCharge | loop_subscription_paused | Skio: Subscription Paused | Retextion - Subscription Paused |
| Cancelled | Subscription cancelled on ReCharge | loop_subscription_cancelled | Skio: Subscription Cancelled | Retextion - Subscription Canceled |
| Reactivated | Recharge subscription reactivated | loop_subscription_reactivated | Skio: Subscription Reactivated | Retextion - Subscription Reactivated |
| Next date changed | Subscription next charge date changed on Recharge | loop_subscription_rescheduled | Skio: Subscription Next Billing Date Updated | Not listed |
| Out of stock | Not listed | loop_order_out_of_stock | Skio: Subscription Item Out of Stock | Retextion - Item Out Of Stock |
| Saved in cancel flow | Not listed | Not listed | Skio: Subscription Went Through Cancel Flow | Not listed |
| Winback | Not listed | Not listed | Skio: Winback Initiated | Retextion - Winback Ready |
Sources: Recharge, Loop (updated 27 August 2026), Skio (updated 3 July 2026) and Stay AI (updated 21 September 2026). The Recharge failed charge name is from our own test store's Klaviyo account.
Four naming styles, and what to search for
Klaviyo's trigger picker is a text search, so search for each app's own prefix: loop_ for Loop, "Skio: " for Skio and "Retextion" for Stay AI. Type the wrong word and the metric looks missing.

- Recharge puts the app name last: "Order upcoming on ReCharge". Its own doc spells it ReCharge in some names and Recharge in others. Search both. Profile properties start with rc_.
- Loop uses snake case: loop_upcoming_order. Profile properties mostly start with $loop_.
- Skio puts "Skio: " first, then title case. Profile properties start with skio_ and run in camel case, like skio_hasActiveSubscription.
- Stay AI still uses its old name for events: "Retextion - Order Upcoming". Profile properties start with stay_. Search "Stay" and you only find the properties.
Two kinds of data come over. Events start flows and carry that one moment, like the product or the cancel reason. Profile properties sit on the person and drive segments and splits. Recharge's property doc draws the same line.
Recharge Klaviyo integration: the metrics
Recharge sends the most metrics, with the oddest gaps. From its metrics page:
- Subscription started on ReCharge fires once per subscription. A customer who buys three subscriptions gets three welcome emails. Recharge's fix: trigger on "Order placed successfully on Recharge" filtered to CHECKOUT.
- Order upcoming on ReCharge fires three days before the charge by default. You change the day in Recharge's upcoming order email settings. It reaches Klaviyo in the early afternoon, US Eastern time, per its flow guide.
- Subscription cancelled on ReCharge carries cancellation_reason, so winback can split by reason.
- Also listed: paused, expired, reactivated, SKU swapped, frequency changed, next charge date changed, and gift, bundle and membership metrics.
The page lists no skip event and no failed payment event. But a failed charge does reach Klaviyo, as "Charge processing failed on ReCharge". It fires on every retry. So we trigger on charge_attempts = 1. One person, one entry. That is the trigger for our 7-email card update flow.
What Klaviyo cannot send is Recharge's own Failed Payment Recovery emails. Its recovery doc says those stay inside Recharge, and the AI strategy sends five of them. You don't want both running. So pick one sender. We use Klaviyo. Ask Recharge to keep the AI retries and turn its emails off.
Recharge also has three ready-made flows in Klaviyo's library: New Subscriber Welcome, Upcoming Order Reminder and Subscriber Win Back, per its pre-built flows page. They need the latest integration. And the reminder does not fire for $0 prepaid shipments.
After the integration upgrade, Recharge metrics sit under a Recharge filter in Klaviyo, not the API filter, and can take up to 24 hours to show. The full build is in our Recharge retention setup.
Loop Klaviyo events
Loop sends 28 events, all in loop_ snake case, per its Klaviyo doc. The ones most flows need:
- loop_subscription_started, loop_upcoming_order, loop_order_processed
- loop_order_skipped and loop_order_unskipped
- loop_subscription_paused, loop_subscription_resumed, loop_subscription_cancelled, loop_subscription_reactivated
- loop_subscription_marked_for_cancellation, for a cancel that takes effect later
- loop_payment_method_expiring and loop_order_out_of_stock
Payment failures come as three events, so one flow can change its message by stage: loop_billing_attempt_failed_and_will_be_retried, loop_billing_attempt_failed_and_last_retry_left and loop_billing_attempt_failed. Each carries the retries left. We split on that.
A date change comes as two events, loop_subscription_rescheduled and loop_subscription_delayed. A flow takes one trigger. So the "your date changed" flow needs a copy for each.

Klaviyo comes with Loop's Starter and Pro plans. Syncing existing customers can take 48 to 72 hours. Start it days ahead. Loop also asks which events count as revenue in Klaviyo, so check that before you trust flow revenue. And its resume link, event.quickAction_resumeSubscription, goes in our paused and winback emails so nobody has to log in. More in our Loop retention setup.
Skio Klaviyo events
Skio prefixes every metric with "Skio: ", per its event metrics page. Beyond the map, it sends Subscription Renewed, Subscription Unpaused and 3DS Verification Required.
Skio is the only one of the four that tells Klaviyo about a save. "Skio: Subscription Went Through Cancel Flow" fires when a subscriber is saved in the cancel flow. That gives you a "thanks for staying" email. It also lets you count saves that cancel again a month later.
Its Klaviyo guide has the payment flow wait 2 days, then check skio_hasFailedSubscription is still true before the next email. A Skio success manager can clone the default flows into your account. The Klaviyo invite you send them lasts 12 hours.
A Skio metric only shows in Klaviyo after it fires once. Use Send Test in Skio's Klaviyo settings before you build. More in our Skio retention setup.
Stay AI Klaviyo events: still "Retextion"
Stay AI used to be called Retextion. Its Klaviyo metrics still say so. Its Klaviyo doc lists 21, from "Retextion - Subscription Started" to "Retextion - Winback Ready". Stay says they will be renamed later. It gives no date.
- The doc lists "Subscription Canceled" with one L, then "Cancelled" with two. Use the spelling your Klaviyo account shows.
- Profile properties use stay_: stay_active_subscriber, stay_active_subscription_count, stay_cancelled_subscription_count.
- Three fields, rtx_all_subscriptions, rtx_active_subscriptions_charge_count and rtx_subscriptions, came off Stay's metrics on 3 November. If a flow filters on them, change it.
Winback Ready, from Stay's WinbackEngine, is the winback trigger. See our Stay AI retention setup for the rest.
Find the events with traffic and no flow
Once a month, list every subscription metric in Klaviyo with its events in the last 30 days. Then match each to a flow.
At one Stay AI brand we checked in October, Retextion - Subscription Started and Retextion - Payment Method Expiring fired every day with no flow on them. Onboarding ran on a shipping event instead, behind filters that let through 0.5% of the people it fired for. The card expiring email came first. It stops the failure before it happens.
Which Klaviyo flow runs on which event
These are our core subscription email flows, with the trigger each one needs.
| Flow | Trigger |
|---|---|
| Welcome and onboarding, orders 1 to 3 | Subscription started. On Recharge, Order placed successfully filtered to CHECKOUT |
| Upcoming order reminder | Upcoming order |
| Failed payment | Payment failed. Recharge: first attempt only. Loop: split by retries left |
| Card expiring | Card expiring. Recharge lists none |
| Skip, pause and date change | Skipped, paused, date changed. Loop has two date events |
| Thanks for staying | Saved in cancel flow. Skio only |
| Cancel confirmation and winback | Cancelled, split by reason. Stay AI has Winback Ready |
| Out of stock | Out of stock |
Every message after a delay needs a cancel exit. And active subscriber suppression on acquisition campaigns runs on the rc_, $loop_, skio_ or stay_ properties, not an event.

Double sends: the app's emails and Klaviyo's
Turn a Klaviyo flow on without turning the app's own email off, and subscribers get two. Recharge's flow guide says it plainly: deactivate the matching Recharge notification under Email.
The same thing happens between Klaviyo flows. At one of our brands, subscribers got the general post-purchase flow and the subscriber one, because the subscriber exclusion looked back one hour only. Another had a native and a backup flow firing minutes apart, until a customer complained. The fix: the backup excludes anyone who had the native event in the last 30 days. And keep new subscribers out of campaigns for their first month, so onboarding emails are not buried.
Some events also fire twice for one change. Recharge's next charge date changed fires once per subscription, and at one brand about 1 in 4 customer-days carried two or more. A flow filter fixes it: not in this flow in the last day. Never smart sending.

Smart sending blocks order emails
Smart sending skips an email if the person got another one in the last few hours. Fine for campaigns. So we turn it off on every subscription email and SMS, because it can block a reminder or a payment email.
At one of our brands, an order-triggered flow sent to under 3% of the orders that qualified. The flow filter looked like the cause. It was not. A loyalty points email fired about a minute after every order, so smart sending skipped the next email for nearly everyone. Skips do not show on the profile timeline. So it took a while to find.
So when an order flow under-sends, check smart sending on its first email before you touch the filters.
What breaks when you switch apps
Every flow on your old app stops on cutover day. It still says Live and never gets another entry. The full move is in our subscription migration checklist. Four things, in the order we usually find them.

Flows on the old event go quiet
The upcoming order email is the one that hurts first. It is where subscribers skip instead of cancel. If it stops, the next thing they see is the charge.
Segments freeze
The old app stops updating its profile properties. rc_active_subscriber stays true for someone who cancelled on the new app last week. Every segment and campaign filter built on the old properties needs the new one.
Migrated subscribers look new
A migration creates every subscription again in the new app. On the brand we moved to Loop, they all landed in one day. If the new app sends a start event for each one, your welcome flow treats loyal subscribers like first-timers. Ask the migration team, and add a filter either way.
Merge tags break
A cloned flow keeps the old app's merge tags. {{ event.scheduled_at }} is a Recharge field. On Skio the date is nextBillingDate. A tag with no data renders blank, so the email says "Your order ships on ." Preview every email with a real event. Test events miss things. Our Recharge test event had no portal link, so the button fell back to the login page.
Dates need a filter too. Raw, they print as 2026-11-24. Nobody reads that. Add |format_date_string|date:'F j, Y' and they read as words. On Recharge the subscription id also moves: event.extra.id on a cancel, event.line_items.0.subscription_id on a failed charge.

The order we use is in the graphic. Two checks people skip: switch old and new flows in the same hour, and confirm order counts carried over before the order 2 and 3 gifts fire, or the gift lands on the wrong order. If you are still choosing the app, event depth is one of the levers in our best Shopify subscription app comparison.

What we could not confirm
We found no Recharge skip event, and no Recharge or Loop event for a cancel flow save. If your Klaviyo account shows a metric that is not here, the account is the source of truth.
If failed payments are the gap, failed payment recovery covers the flow, and Churn Buster is the option when you want it outside the app.
Remapping events is the easy part. Rebuilding the flows on the right triggers is where the time goes. Subscription LTV Maximizer™ builds the cancel flow, portal, payment recovery, pause and skip in Recharge, Skio, Stay AI or Loop, plus the email and SMS on these events, live in 30 days, for $5,000.
FAQ
What does the Recharge Klaviyo integration send?
It sends metrics like Subscription started on ReCharge and Order upcoming on ReCharge, plus rc_ profile properties such as rc_active_subscriber. Its metrics page lists no skip event. A failed charge still shows as Charge processing failed on ReCharge. Recharge's own Failed Payment Recovery emails cannot be sent from Klaviyo.
Does Stay AI still use Retextion in Klaviyo?
Yes. As of September 2026, every Stay AI metric in Klaviyo starts with "Retextion - ". Stay says they will be renamed later. Profile properties already use stay_, so searching "Stay" only finds the properties.
Should smart sending be on for subscription flows in Klaviyo?
No. Turn it off on every subscription email and SMS. It skips a message if the person got another one recently, so a loyalty email sent minutes earlier can block a payment email. The skips do not show on the profile timeline, so check this first when a flow under-sends.
Why are my subscribers getting two emails for the same thing?
Usually the subscription app and Klaviyo are both sending. Turn the app version off wherever a Klaviyo flow replaces it. The other causes are two flows on one event with a short exclusion window, and events that fire once per subscription.
Do old Klaviyo flows keep working after a subscription app switch?
No. They stay live but stop getting new entries, because the old app stops sending events. People already partway through a flow finish it. Segments on the old app's properties freeze too. Rebuild each flow on the new app's event before cutover.
One email a week on subscription retention: the numbers, the strategy, and what to fix first.







