Klaviyo and Liftable: what the connection reads, and what it can draft

The four scopes, and why each one

flows:read: which flows exist, their status, what triggers them and when they last changed. The trigger, not the name, is what tells an abandoned-checkout flow from a welcome series, so a flow you renamed is still recognised for what it does.

metrics:read: the metric totals Klaviyo keeps, which is how flow results can sit beside the cart and checkout opportunities Liftable finds.

lists:read: your lists, read as counts only. Liftable does not read who is on them.

flows:write: the one write. It is used for a single thing, creating a new flow as a draft. That is the whole list. Profiles, segments and campaigns are left at no access, which is why Liftable cannot see an email address, a name or who any individual subscriber is.

What Liftable does with it

It answers two questions neither tool answers alone: whether you have a flow for abandoned carts and checkouts at all, and how your flows sit next to the cart and checkout opportunities Liftable finds on your store.

A recovery email monetises abandonment after it happens; a cart fix removes some of the cause. Seeing both in one place stops you counting the same shopper twice, and shows where a missing or paused flow is the cheaper fix.

This is a comparison, not an attribution claim. Liftable’s receipt is built to measure revenue on Shopify orders against a holdback, and the Klaviyo figures sit beside it as context.

The one thing it can write

Liftable can create a flow in your Klaviyo account, and only as a draft. The status it sends is always draft; it then re-reads what Klaviyo created and refuses to continue if the flow came back live. The draft’s name starts with “liftable:” so you can see who made it.

A draft goes live only when you approve it in Liftable, and the decision is recorded in your decisions log. Because the draft is in your own Klaviyo account, you can also edit it, switch it on yourself or delete it there.

It does not edit or switch off your existing flows, and it never sends an email.

Where this stands

The Klaviyo connector is built and covered by tests. No merchant has connected one in production yet, so there are no results from it to show.

There is no Klaviyo app listing for Liftable yet, which is why the connection is a private key you create rather than a one-click approval screen.

Disconnecting

In Liftable, open Connections, choose Klaviyo and disconnect. The stored key is deleted and nothing further is read.

You can also delete the key in Klaviyo under Settings → API keys, which stops it working at once. Either works, and neither requires contacting us.

Connecting, in four steps

1. 01

   Create a private API key in Klaviyo

   In Klaviyo, go to Settings → API keys and create a private key. Choose a custom key rather than a preset, give it read access to flows, metrics and lists, and write access to flows if you want Liftable to be able to create draft flows. Leave everything else at no access.

2. 02

   Paste it in Connections

   In Liftable, open Connections, choose Klaviyo and paste the key. Liftable checks it with Klaviyo before saving it, and a key Klaviyo does not accept is reported back and not stored. A saved key is encrypted and never shown again, not even masked.

3. 03

   Let the first sync run

   Liftable reads your flows and metrics as soon as you connect, then every hour. Answers come from the last sync, and are marked stale if nothing has been read for a day.

4. 04

   Review any draft flow before it runs

   If Liftable proposes a recovery flow, it appears in your Liftable approvals and in Klaviyo as a draft whose name starts with “liftable:”. It stays a draft until you approve it.

Questions