Klaviyo abandoned-cart and recovery flows, with the storefront evidence

The flow sees the abandonment, not the cause

A flow triggers on a started checkout that did not finish. It does not know that the shopper left when delivery cost appeared, or went to find a discount code, or could not pay with one tap on a phone. Those are storefront facts, and they are the ones that decide how big the flow’s audience is in the first place.

What Liftable reads, and what it can write

Connected, Liftable reads your flows, their metrics and list counts, and shows the recovery flows beside the cart opportunities on your store. It asks Klaviyo for four scopes: flows read, flows write, metrics read and lists read. It never reads a profile, a list’s members or an email address.

The one thing it can write is a new flow, created as a draft. A drafted flow is never activated by Liftable on its own: it goes live only when you approve it, and the approval is recorded in the decisions log. No merchant has connected Klaviyo in production yet.

Connecting, and leaving

Klaviyo’s marketplace app for Liftable does not exist yet, so you connect by creating a private API key in Klaviyo with those four scopes and pasting it on the Connections page. The first read runs as soon as you connect. Disconnecting is one button on the same page and takes effect immediately; the key is purged.

The checks that look for this

The free scan runs these on your own pages, desktop and mobile, and shows each finding with its evidence. Each check has its own page saying how to see the problem without installing anything.

What Liftable does about it today

What is live today. Liftable finds the opportunity and our founding-team programme implements and measures the first fix with you. Automated testing is not live on any merchant’s store yet.

• Theme app extensionC1 · P6

  Shown through Liftable’s theme app extension, a block you switch on in the theme editor. Liftable never edits your theme’s code.

• Shopify Function (discount)C3

  Runs as a Shopify Function for discounts, and only for a test you have approved.

• Recommendation for your developerC4 · C2

  A recommendation with the change written out for your developer. Liftable never edits theme code, live or otherwise.

• Available now the scan, the evidence, the drafts, the approval
• With the founding team implementing and measuring the first fix
• Coming automated tests on a merchant’s store

What you get

• Your recovery flows and their metrics, beside the cart findings on your storefront that feed them.
• A drafted recovery flow where there is none, or a drafted variant where there is one, for you to read and approve in Klaviyo.
• Fix drafts for the storefront causes the scan found, so the flow’s audience shrinks for a reason you chose.
• Four read-mostly scopes, a key you can revoke in Klaviyo at any time, and no access to profiles or email addresses.

Who it is for

A good fit

• Brands on Klaviyo whose abandoned-cart flow is the main recovery lever and who want to know what it is recovering from.
• Teams that want a second flow drafted without starting from a blank template.

Not the right tool

• Stores on Marketo or another email platform: Liftable reads Marketo sends, opens and clicks, but drafts flows only in Klaviyo today.
• Anyone who wants Liftable to send email. It does not; Klaviyo does, on your approval.

Questions