JLDIGITAL KNOWLEDGE HUB · Email & Klaviyo

Klaviyo flows: which automations does an online store need?

Klaviyo flows are automated message sequences triggered by an action, list or segment membership, or a date. The right mix depends on your customer journey, the events your integration supplies and the way people buy your products — not a fixed number of emails every store is supposed to send.

In this article

One journey. Different moments to follow up.

JLDIGITAL · SIMPLIFIED ILLUSTRATION · Illustrative email steps — not prescribed timing
  1. 01Visitor
  2. 02Subscriber
  3. 03Browsing
  4. 04Cart
  5. 05Checkout
  6. 06First purchase
  7. 07Customer
  8. 08Repeat purchase / inactive

Welcome

Trigger
Added to subscriber list
Purpose
Set expectations and help with the first choice.

Signup → wait → check purchase and channel eligibility.

  1. 01

    Welcome and the promised content

  2. 02

    Help choosing a product

  3. 03

    Address a common question

Illustrative logic: check purchases and permission before the next message. Exit or branch if the situation has changed.

A flow responds to a person; a campaign has a send date

A launch campaign usually reaches an audience at a planned time. A flow starts when an individual qualifies. Customers can enter the same automation on different days and follow different branches, even though the underlying design is shared.

The trigger opens the door. Trigger filters narrow the event itself, while profile filters check the person’s history or properties. Klaviyo checks profile filters at entry and again before flow actions. A rule excluding people who purchased since starting the flow can therefore prevent an irrelevant abandonment reminder.

Documentation: Klaviyo — flow triggers and filters

A product view, a cart and a checkout are not interchangeable

Browse abandonment uses the Viewed Product event and needs an identifiable visitor with the relevant tracking in place. Added to Cart and Started Checkout must also be available from your particular integration. Designing the message first will not fix a missing event.

Klaviyo uses abandoned cart as an umbrella term, but cart and checkout sequences can have different triggers. Document that distinction and check any default reminders from your commerce platform so customers do not receive a parallel set of messages.

Documentation: Klaviyo — browse abandonment · Klaviyo — cart and checkout abandonment

Choose a job before you choose another automation

Our practical approach is to address frequent, useful moments first. A store attracting subscribers but seeing few repeat orders might prioritise welcome and relevant abandonment sequences. A replenishable product range gives you a different reason to build a repeat-purchase programme.

Give each sequence a specific job. Welcome can establish expectations and help a subscriber find a suitable product. Post-purchase can explain delivery, use or care. Cross-sell should be about a compatible next purchase, not simply whichever product needs more promotion.

  • Welcome: introduce the relationship and a useful next step.
  • Browse, cart and checkout: follow up in proportion to the intent.
  • Post-purchase: help the customer get value from the order.
  • Replenishment or cross-sell: a relevant next order where the range supports it.
  • Winback: consider re-engagement after a meaningful gap.

Timing and permission belong in the flow design

Someone who has purchased should leave a purchase reminder or move to a different branch. Use filters and conditions, and review campaigns alongside flows. A reasonable email in each of three programmes can still add up to too much contact.

An event is not marketing permission. Check consent, channel eligibility and the rules applicable to the market. Necessary order communications and promotional messages are not interchangeable simply because both are automated.

Set winback timing around the actual buying cycle. A furniture buyer and a customer buying consumables have different reasons to return. An illustrative replenishment sequence might wait until expected consumption and then check whether another order has already arrived.

Documentation: Klaviyo — flow triggers and filters · Klaviyo — winback flows

Read performance in the context of the relationship

Begin with deliveries, clicks, unsubscribes and spam complaints. Then review purchases, platform-attributed revenue and attributed revenue per recipient within the same account, period and currency. Welcome and winback audiences start from different circumstances; their raw figures are not a fair ranking of the two flows.

Klaviyo-attributed revenue does not prove additional or incremental sales. Attribution settings, existing purchase intent and other channels influence the report. Use store orders and, where feasible, controlled tests to add context. Opens alone are an unreliable indicator of interest.

Work through the sequence: did the right person enter, did the message reach them, was the destination relevant, and does the next step still make sense? Repair an identifiable break before adding more messages.

Build the first sequence around a testable event

Start with an event you can verify and a customer problem you can name. Map the wait, exit rules and messages before writing the emails. Run a test profile through realistic events and trace what your commerce integration supplies to Klaviyo.

Before launch, check links, product rendering, mobile display, eligibility and overlap. Keep evaluating the original customer task after launch. Our Email Marketing service covers strategy and ongoing execution; this guide focuses on how the automations work.

  • Confirm the event and integration.
  • Define the purpose, audience and exit rule.
  • Write only the messages with a clear job.
  • Test realistic events and channel permission.
  • Review relevance, delivery and economics before expanding.

Sources and scope

Technical explanations draw on the documentation below. Priorities and working methods are JLDigital’s practical judgement. Figures and examples are original educational work, not client data or projected results.

Platform features and rules can change. Check the actual setup and applicable documentation before implementing.