memberr Docs

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 use as a flow trigger, segment condition, or analytics dimension.

What you get

12 metrics covering start, pause, cancel, expire, reactivate, SKU swap, frequency change, next charge date change, upcoming charge, order placed, charge failure, and 3D Secure challenges
2 profile properties updated on each successful subscription order (memberr_last_subscription_purchase_at, memberr_last_subscription_order_id)

There is nothing to install on Klaviyo's side. Metrics appear automatically the first time they fire (or when you send a synthetic batch).

No historical backfill

Events emit only while Klaviyo is connected, at the moment a contract or billing attempt changes. Connecting later does not replay past subscription history.

Start here

Quickstart

Connect Klaviyo via OAuth and verify delivery.

Events reference

Properties, unique IDs, triggers, and skip rules for every metric.

Flows

Essential metric-triggered journeys for a standard setup.

Testing

Fire all 12 metrics into your own Klaviyo profile.

Available metrics

Metric name	Fires when
`Subscription started on memberr Subscriptions`	A new subscription contract is created
`Subscription paused on memberr Subscriptions`	The subscription is paused
`Subscription cancelled on memberr Subscriptions`	The subscription is cancelled
`Subscription expired on memberr Subscriptions`	The subscription reaches its maximum cycles
`memberr subscription reactivated`	A cancelled subscription becomes active again
`Subscription SKU swapped on memberr Subscriptions`	A line's variant or product changes
`Subscription next charge date changed on memberr Subscriptions`	The next billing date is rescheduled
`Subscription frequency changed on memberr Subscriptions`	The billing or delivery interval changes
`Upcoming charge on memberr Subscriptions`	A reminder window opens before the next charge
`Order placed successfully on memberr Subscriptions`	An order is linked to a subscription contract
`Charge processing failed on memberr Subscriptions`	A billing attempt fails
`Payment authentication required on memberr Subscriptions`	The customer must complete 3D Secure

Per-subscription-line semantics

Subscription lifecycle and change events fire once per subscription line. A contract with three products on the same schedule emits three Subscription started events - one per product - each with that line's product, variant, SKU, and price. That matches how subscription email flows are usually built: welcome or win-back per product, not one email lumping every line together.

Order- and charge-level events fire once per order or once per billing attempt. Upcoming charge fires once per contract per billing cycle. Order placed successfully includes a line_items array for everything on the order.

How events flow

Shopify webhook / DB sync → memberr Subscriptions → Klaviyo Events API

Subscription state changes from Shopify (cancel, pause, expire, billing attempts, contract updates, and more) are picked up by memberr Subscriptions, translated into lifecycle events, and posted to Klaviyo. See the Events reference for triggers, properties, and what does not fire.