Which Shopify subscription events does Zubs send to Klaviyo?

What reaches Klaviyo?

Every moment in a subscription’s life, each as its own event that can start a flow, define a segment or filter a campaign:

• Lifecycle: a subscription is created, paused, reactivated or cancelled.
• Billing: a renewal succeeds, or a billing attempt fails on payment or on stock.
• Orders and changes: a reminder before the next order, a skipped order, changed items, frequency, date, address or delivery method, and a ship-now order.

Each event carries the subscription, product and customer details your templates need. Pickup subscriptions include the pickup location, so an email can say where to collect the order. The reminder event follows your reminder schedule even when the Zubs reminder email is off, so Klaviyo can take that email over completely.

Why does the failed-payment event matter?

It fires on every failed attempt, not only the last one, and says which stage of dunning the subscription is in. That is what you need to send a different message at each step: a friendly first notice, a last-chance email before the final retry, and an out-of-stock note that asks the customer for nothing. Recovering these payments keeps them from turning into involuntary churn.

What does Zubs keep on each profile?

Subscription data that every segment and campaign can use without exporting lists: whether the customer is an active subscriber, how many subscriptions they have, which products they receive and how often, and whether they collect from a pickup location. Zubs updates it whenever something changes.

Use it to keep subscribers and one-time buyers apart. Subscribers want to hear what’s coming next and how to change it. One-time buyers need a reason to come back. The same campaign rarely serves both, and a discount meant for newcomers can sour someone who already pays every month.

What can you build with it?

• Dunning emails per stage. One flow on the failed-payment event, with a branch for each stage and a separate message for stock failures. The failed-payments playbook walks through the sequence.
• Win-back. A flow on the cancellation event that checks after each delay whether the customer is still gone, so those who came back drop out. Full play: win back cancelled subscribers.
• “Pick your items” reminders. A flow on the reminder event for customers who haven’t chosen their next order’s items yet.
• Pickup reminders. Segment pickup subscribers and name their location in the email.
• Campaign segments. Customers with more than one subscription, everyone who receives a given product, or one-time buyers for a subscription offer.

How does it fit with the rest of Zubs?

Zubs sends the data, and the flows, templates and timing stay in your Klaviyo account, where your marketing already lives. You choose which Zubs emails to keep and which to hand over. For automations outside your email program, Zubs also brings subscription triggers and actions to Shopify Flow.

Set it up in the help center: Klaviyo events and profile properties.