LatchPay

Connections

Connect Klaviyo

Keep your Klaviyo abandoned-checkout flows working on the LatchPay checkout: create a private key, connect it, and copy the flows.

Updated

Why abandoned-checkout emails need this

Klaviyo's abandoned-checkout flows start on the event Checkout Started. Shopify sends it when a buyer types an email in the Shopify checkout. With LatchPay on, buyers check out in the LatchPay checkout instead, so Shopify never sends it and those flows go quiet.

The Klaviyo Bridge fixes that: LatchPay sends its own Checkout Started (LatchPay) event as soon as a buyer enters an email, and a copy of each abandoned-checkout flow listens to it. Your other flows (Added to Cart, Viewed Product, Placed Order, welcome and list flows) keep working without changes, and orders still reach Klaviyo as Placed Order through Shopify.

Create a private API key in Klaviyo

You need to be an Owner, Admin or Manager in Klaviyo. It takes about two minutes.

  1. Open API keys

    In Klaviyo, click your account name at the bottom left, then Settings → Account → API keys.

  2. Create a private key

    Under Private API keys, click Create Private API Key. Name it LatchPay and choose Custom Key.

  3. Give it six scopes

    • Accounts: Read, to read your account name and public key.
    • Events: Full, to send Checkout Started (LatchPay).
    • Profiles: Full, to attach the event to the buyer by email.
    • Metrics: Read, to find which flows start on Checkout Started.
    • Flows: Full, to read your flows and create the draft copies.
    • Segments: Read, to find segments that use Checkout Started.

    Leave everything else on No Access.

  4. Copy the key

    Click Create and copy the key straight away: Klaviyo shows it only once. It starts with pk_.

Private key, not public key

Klaviyo also has a public API key: six characters, also called the site id. That one only identifies your account and cannot send events from a server, so LatchPay asks for the private key and reads the public key from it.

Connect it in LatchPay

In the dashboard, open Email, paste the key and click Connect Klaviyo. LatchPay checks the key, reads your account and shows its name and public key. From then on every checkout with an email reaches Klaviyo.

What LatchPay sets up in Klaviyo

Right after you connect, LatchPay sends one test event to your own email address and then prepares your flows in Klaviyo, as drafts. It takes about a minute. The Email page then shows what it made and what is left for you.

  • Abandoned-checkout flows (they start on Shopify's Checkout Started) get a copy named after the original with "(LatchPay)" at the end: same filters, delays and emails, started by Checkout Started (LatchPay). Keep the original live as well: it covers checkouts that go through Shopify when you switch LatchPay off, and a checkout only ever starts one of the two.
  • Flows that only check Checkout Started in a filter or split, like a Browse Abandonment flow that skips people who started a checkout, get a copy with the same trigger and the LatchPay event added to that condition. Once the copy is live, set the original to draft, or both send.
  • Segments are not copied: your campaigns point at the segment itself. The page shows the condition to add by hand.
  1. Open each copy in Klaviyo

    The Email page links every copy under To do in Klaviyo. Check the emails in preview.

  2. Set it live

    Set the copy and its emails live in Klaviyo. LatchPay never switches a flow on or off for you.

  3. Follow the rest of the list

    Turn off the originals the list names, and add the segment conditions. Click Regenerate flows any time you add a flow: LatchPay only creates what is missing.

What LatchPay sends

One event per checkout, sent within seconds of the buyer entering an email, with the same fields as Shopify's own Checkout Started, so the product blocks and buttons in your templates keep working:

  • the value and currency of the checkout, the item names and count, and the discount codes;
  • event.extra.line_items with title, quantity, price, image, variant, SKU and product, and event.extra.checkout_url, the link back to the buyer's LatchPay checkout;
  • Source Name is latchpay, so you can tell the events apart in reports.

When Klaviyo does not answer, LatchPay retries every ten minutes for a day. Klaviyo drops duplicates, so a retry never starts a flow twice.

Good to know

  • Klaviyo is connected per store. Each store can send to its own Klaviyo account.
  • The key is stored encrypted. The dashboard only ever shows its last four characters.
  • If you delete the key in Klaviyo or remove a scope, the Email page says so and LatchPay stops sending until you paste a new key.
  • Disconnect on the Email page stops the events right away. Flows and copies in Klaviyo stay as they are.
  • Only buyers who enter an email are sent. Email marketing consent is still handled by Shopify: a buyer who ticks the newsletter box is subscribed there, and Klaviyo picks that up through its Shopify integration.

Still stuck?

Tell us what you see and which store it is about. We reply by email, usually within a day.

More in Connections