Overview
Send subscription lifecycle events from memberr Subscriptions to Klaviyo.
The Klaviyo integration sends subscription lifecycle events from memberr Subscriptions to Klaviyo in real time. Each event lands on the customer's Klaviyo profile (keyed by email) as a custom metric, which you can then use as a flow trigger, segment condition, or analytics dimension.
What you get
Every meaningful state change on a subscription - start, pause, cancel, expire, reactivate, SKU swap, frequency change, next charge date change - fires a metric, plus order- and charge-level events. Profile properties on the customer are kept in sync alongside the events so your email templates can reference the latest values.
Available metrics
| Metric name | Fires when |
|---|---|
Subscription started on memberr Subscriptions | A new subscription contract is created |
Subscription cancelled on memberr Subscriptions | A subscription is cancelled |
Subscription expired on memberr Subscriptions | A subscription auto-expires after reaching its maximum cycles |
Subscription paused on memberr Subscriptions | A customer pauses their subscription |
memberr subscription reactivated | A cancelled subscription transitions back to active |
Subscription SKU swapped on memberr Subscriptions | A customer swaps the variant on a subscription line |
Subscription next charge date changed on memberr Subscriptions | The next charge date is rescheduled |
Subscription frequency changed on memberr Subscriptions | The billing or delivery frequency changes |
Order placed successfully on memberr Subscriptions | A recurring order is successfully created |
Charge processing failed on memberr Subscriptions | A billing attempt fails |
See the Events reference for the full list of properties on each metric.
Per-subscription-line semantics
Subscription-level events (started, cancelled, paused, etc.) fire once per subscription line. A contract with three different products sent on the same schedule emits three Subscription started events - one per product - each carrying the product, variant, SKU and price for that line. This matches how segmentation typically works in subscription email flows: you usually want to send a different welcome email per product, not one email lumping multiple products together.
Order- and charge-level events fire once per order or once per billing attempt respectively, with a line_items array describing everything in the order.
How events flow
Shopify webhook → memberr Subscriptions → Klaviyo Events APISubscription state changes from Shopify (via subscription_contracts/cancel, subscription_contracts/pause, subscription_contracts/expire, billing attempt webhooks, etc.) are picked up by memberr Subscriptions, which translates them into lifecycle events and posts them to Klaviyo's /api/events endpoint. There is nothing to install on Klaviyo's side - the metrics show up automatically the first time they fire.
What to do next
- Connect Klaviyo - authorize memberr Subscriptions against your Klaviyo account.
- Review the event reference - see exactly which properties each metric carries.
- Send a test batch - fire one of every event into your Klaviyo profile so you can build flows against real data immediately.