A Practical Klaviyo Flow Guide: Entry, Exclusions, QA and Measurement

By Trayan Hristov · Thrivelia · Reviewed 13 October 2026

A useful Klaviyo flow moves a customer towards a specific next step. The technical build should express that decision clearly: who enters, what they need, when the message becomes irrelevant and how you will judge the result.

This guide uses checkout recovery as an example. The same planning discipline applies to welcome, product adoption and replenishment. Start with the customer need rather than the number of messages in a flow.

Write a flow brief before opening the builder

Define the entry event, audience, customer question, intended action, stopping condition and owner. For checkout recovery, the question might be about fit, shipping or product confidence. The intended action is a completed purchase; a discount is one possible tactic rather than the purpose of the journey.

Map the events and properties needed for the decision. Compare real examples from your connected store with the account’s events, including a multi-item basket, a completed purchase and a changed product variant. Name any missing information before creative production begins.

Distinguish trigger filters from continuing eligibility

Klaviyo trigger filters evaluate event-specific information at entry. Profile filters are checked at entry and before flow actions. Its current documentation also separates re-entry controls from these filters. A failed profile filter can skip an action; do not assume that every skipped action removes the person from the whole flow.

For a purchase-aware journey, decide what counts as a subsequent purchase and which actions need that exclusion. Use the actual Started Checkout and Placed Order events available in the account, with a reviewed timing rule. A completed purchase should not receive a later message that says the checkout remains incomplete.

Review Klaviyo’s official trigger and filter guide alongside the live account. Treat the eligibility rules as part of the customer experience, not a technical note to add after design.

Build a small journey with a useful message

Begin with one message that answers a real checkout question and provides a clear return path. Check that its product content remains understandable on mobile and that the action appears early. If the message uses stock, delivery or offer claims, confirm the source and the intended fallback.

Add later steps only when they have a different job. One might resolve a remaining objection; another might help the customer choose the right product. Repeating the first message with a larger discount does not automatically make the journey more effective.

Test the states that can make the message wrong

Use previews and controlled test profiles before launch. Record what actually happened at each action, including skips and data delays. Assign someone to review the first live entrants rather than treating the builder’s saved state as evidence that the journey works.

Test state	Expected decision	What to inspect
Checkout without purchase	Eligible customer can reach the intended action	Event data, timing, product content and return link
Purchase during the wait	A later recovery action no longer describes an abandoned checkout	Purchase event arrival and action-level eligibility
Suppressed or unsubscribed profile	Marketing follows the account’s consent and suppression rules	Eligibility and channel permissions
Repeat checkout	Re-entry follows the agreed customer experience	Frequency, duplicate messages and timing

Measure efficiency and customer progression

Report eligible entrants, messages delivered, purchases and revenue per delivery for a defined period. Break out promotions and customer groups where they change the comparison. Also check unsubscribes, complaints and subsequent purchase behaviour so a short-term attributed result does not hide a weaker customer relationship.

Our perfectwhitetee client analysis shows how we describe flow revenue per delivery with its calculation and reporting periods. It is an example of measurement, not a promised result for another account.

Next, use the Klaviyo self-audit, compare platform cost and fit or discuss your flow priorities. Platform behaviour reviewed 13 October 2026.

Worked build: a first-order journey for a footwear brand

Use an illustrative footwear brand whose first customers often ask whether the fit is correct. The first-order journey should help the buyer feel confident using the product, then introduce a relevant next purchase. Give the sequence three jobs: preparation, first-use support and the next useful choice. Keep order confirmation and delivery notifications owned by the existing operational system unless their responsibilities are deliberately reassigned.

Define the customer states before choosing delays. A first-time buyer waiting for fulfilment needs different content from someone who has received the shoes, reported a fit problem or already ordered a second pair. A fixed day-seven sales message will not recognise all of those states. Our VIBAe case illustrates the role of product education and post-purchase support in a footwear programme.

Map the minimum data before building

These are planning inputs. Use the actual event names and property paths exposed by your store integration; a service exception is not assumed to be a built-in Klaviyo event. Trace sample events before copying a property into a split. An order list, a category array and a single text property require different matching rules.

Input	Meaning in this example	Decision it supports
Placed Order	The order and product/variant purchased	Entry and product-specific routing
Fulfilled Order or another reliable delivery signal	The operational milestone your integration actually supplies	When first-use content becomes useful
Purchase history	Whether this is the first or a later order	New-buyer versus repeat-customer path
Product category or variant	The actual product decision, such as type or width	Relevant education and complementary products
Service exception signal	A reviewed indication of an unresolved customer issue, if available	Pause inappropriate promotional follow-up
Subsequent order	A new purchase after entry	Stop or redirect the next-purchase reminder

Translate the brief into Klaviyo decisions

Klaviyo’s product-specific-flow guidance distinguishes a trigger split, which can inspect the triggering event, from a conditional split based on other customer information. Its cross-sell guidance includes Placed Order or Fulfilled Order as relevant entry metrics. Read the product-specific guide and cross-sell guide, then confirm the event and property configuration in your account.

A first-order split must be tested against a real first order and a real second order. Do not choose a lifetime-count threshold from memory without checking when the triggering event is included. Record the observed behaviour and the timing of the data update.

• Choose the order-related metric that matches the message’s purpose and confirm it arrives reliably.

• Use event-specific trigger filters to restrict product eligibility when the journey is category-specific.

• Use a conditional split for customer context that needs checking on the path, such as first versus repeat purchase.

• After a delay, re-check the customer state that would make the next action inappropriate.

• Give a later cross-sell or reorder message its own subsequent-purchase exclusion.

• Review re-entry, overlapping campaigns and other flows before activating the journey.

Write three different message briefs

These are sample briefs, not client emails. Keep the product guidance approved and connect the action to the page that fulfils the promise. Put the key explanation and action early, then use lower content for proof and questions. If the fit remains unresolved, direct the customer towards help rather than a second sale.

Message job	Illustrative subject and content	Primary action
Preparation	‘A good first fit starts here’ — explain what the buyer should expect and how to check the fit	Read the fit guide
First-use support	‘Before you decide they’re too snug’ — answer a specific product question with approved guidance	Check the fit steps
Relevant next purchase	‘The next pair for your working week’ — recommend from the buyer’s actual product context	Explore the relevant collection

Add a failure-focused QA pass

For each test, keep the profile, source event, expected route, observed route and release decision. Review a small live cohort after launch. A correct preview does not establish that a purchase filter, re-entry rule or delayed event behaves correctly.

• Order arrives twice: the customer should not receive duplicate first-order education.

• Fulfilment is delayed: the content should not assume the product is already being used.

• Order has multiple categories: the chosen education should fit the actual basket.

• Product or variant is unavailable: the recommendation should use an approved fallback.

• A second order happens during a wait: the later reminder should reflect it.

• A service issue is recorded: the promotional path should follow the agreed exception rule.

• A repeat buyer enters: the first-time instructions should not repeat without a reason.

• An email is suppressed: record the skipped action and the remaining journey behaviour.

A worked measurement example

Imagine 1,000 first-order customers with a complete 90-day observation window: 180 place a second order, giving an 18% first-to-second purchase rate. A later comparable cohort has 205 second orders from 1,000 customers: 20.5%. The difference is 2.5 percentage points, or about 13.9% relative to the earlier rate. These are illustrative calculations, not a Klaviyo or client result.

A before-and-after difference can also reflect acquisition mix, promotions, stock or seasonality. Pair cohort progression with journey reporting and, where feasible, an appropriately designed holdout. If a message has $8,400 of tracked revenue from 4,000 deliveries, its revenue per delivery is $2.10; that is a different metric from the 90-day second-order rate. Keep both definitions visible.

Review the next-purchase journey only after enough customers have had time to act. A seven-day dashboard can diagnose entry or delivery problems; it cannot settle a 90-day repeat-purchase question. Use the first-to-second purchase framework to plan the observation window.