Updated: Oct 27
Klaviyo Browse Abandonment Flow: Follow Up Without Colliding With Cart Recovery
By Trayan Hristov · Thrivelia · Reviewed October 2026

A Klaviyo browse abandonment flow follows up after someone views a product. Its job is to help them make a decision: understand the fit, see how the product works or find the right option. Before writing the reminder, decide when browsing stops being the most useful signal. Cart activity, checkout and a purchase should change what happens next.
The familiar mistake is to build each flow separately, then discover that a shopper can receive three different versions of the same nudge. A coherent recovery programme needs a shared priority order and a distinct reason for each message.
Browse, cart and checkout represent different decisions
Klaviyo uses Viewed Product to trigger browse abandonment. Its browse abandonment setup guide distinguishes this earlier signal from cart and checkout activity. Plan the message around what the shopper has actually done.
Observed behaviour | Likely question | Useful response |
|---|---|---|
Viewed a product | Is this right for me? | Fit, use, materials, options or credible product proof |
Added an item to cart | Do I want to commit? | Buying confidence and practical objections |
Started checkout | Can I complete this purchase? | Clear route back and relevant checkout help |
Placed an order | What happens next? | Order expectations and product adoption |
These are planning hypotheses, not a way to read a customer's mind. Use research, support questions and product behaviour to decide which answer your brand should lead with. Our Shopify and Klaviyo cart recovery guide covers the later handoff in more detail.
Prove the event and the audience before building
For Shopify, Klaviyo's onsite tracking documentation explains the app embed and event testing. Trace a test visitor into the correct profile and inspect an actual Viewed Product event. Confirm that the product, destination and event time reflect what happened in the browser. A connected integration alone does not complete that test.
Identification and marketing permission are separate checks. A known email address does not automatically make a shopper eligible for browse abandonment messages. Apply your account's consent and suppression rules to the relevant channel and market. Klaviyo's consent guidance specifically addresses marketing-flow eligibility, including browse abandonment.
Write the handoff rules in one place
Klaviyo's setup guide includes profile filters for no order and no checkout since flow entry. Where a separate Added to Cart flow exists, it also includes an Added to Cart exclusion. Map those conditions to the real events in your integration, including any alternative checkout path you operate.
Browse follow-up continues only while browsing remains the relevant unresolved behaviour.
Cart and checkout journeys have clear ownership; one does not repeat the other's offer by accident.
Purchase activity prevents further recovery messages and routes the customer towards the appropriate post-purchase experience.
Welcome and campaigns respect the same contact-pressure plan instead of treating every flow as a separate audience.
Re-entry rules prevent frequent visitors receiving the same introduction repeatedly.
Use the right kind of condition. Klaviyo distinguishes trigger filters from profile filters: metric-trigger filters inspect the entry event, while profile filters are checked at entry and before actions. Failing a profile filter can skip an action without removing the profile from the flow entirely. Test the later steps too.
For the wider architecture, use our guide to stopping conflicting Klaviyo flow emails. The useful output is an audience rule that the whole team can explain and maintain.
A worked apparel example
Consider a fictional apparel store selling linen shirts. Research suggests that shoppers hesitate over fit and fabric weight. The store chooses an initial two-message test for eligible browsers, with a later message conditional on continuing eligibility. This is an illustrative brief, not a client result or a recommended universal sequence.
Message role | Illustrative copy | Destination |
|---|---|---|
Help choose the fit | A closer look at the linen shirt. Compare the measurements with a shirt you already love, then see how this cut sits on different heights. | The actual product page and its size guide |
Answer the fabric question | Light enough for warmer days, with the texture that makes linen feel like linen. Here is the weave up close and how it softens with care. | Relevant fabric or care explanation, with a clear path to the product |
The brand should substantiate those product claims before using the copy. If the shopper is browsing a wool overshirt, the linen explanation is unsuitable. If the customer already owns the same shirt, a repeat introduction may add little. Product and purchase context should change the message when the data supports it.
For this test, the team might evaluate an initial delay of several hours and a later follow-up the next day. Klaviyo's documented starting point uses at least an hour and includes a frequency restriction. Actual timing and message count should reflect buying behaviour, campaign pressure and the size of the learning opportunity.
Check the product experience as carefully as the copy
Preview the real event used by each message. Confirm the item shown, price, image, link and fallback. Then check what happens when stock changes. Klaviyo documents template changes that skip emails featuring unavailable Shopify products. Configure and test that behaviour in every relevant message; it is not guaranteed by connecting the store. The documented check operates at product level, so an unavailable size or colour can still appear when another variant remains purchasable.
Eligible browser: receives the intended product and buying help.
Browser who starts checkout during the delay: receives no conflicting browse reminder.
Browser who purchases between messages: receives no later recovery prompt.
Repeat visitor: respects the planned frequency and re-entry controls.
Suppressed or ineligible profile: receives no marketing message through this flow.
Unavailable product or missing event detail: follows the tested skip or fallback behaviour.
Mobile reader: can read the copy, open the size guide and reach the intended product.
Measure whether the follow-up improves the decision
Record eligible entrants, actual deliveries, purchases and revenue using consistent windows. Investigate skips rather than automatically treating them as lost opportunity: some show that the shopper progressed and the rules worked. Review complaints, unsubscribes and discount cost alongside commercial results.
Platform-attributed revenue tells you which orders received credit under the configured model. It does not reveal how many would have happened anyway. Where volume permits, a suitable holdout can help evaluate additional purchasing. Keep promotions, product availability and other recovery activity in the interpretation.
Frequently asked questions
Should browse abandonment always include a discount?
No. Start with the buying question. A size comparison, use demonstration or credible review may be more useful than a price reduction. Test an incentive only when the audience and economics justify it, and coordinate it with other offers.
How many browse abandonment emails should we send?
Choose the smallest sequence that answers a real need and gives you enough evidence to learn. A second email needs its own purpose. Adding messages to match another brand's flow count is a weak brief.
Why does the reminder show an unexpected product?
Trace the profile's entry event, re-entry setup and message preview together. Do not assume the item shown represents the shopper's latest preference. Agree the intended selection behaviour, then verify it with a customer who views several products.
Build the recovery journeys as one programme
Thrivelia connects customer research, creative and implementation so recovery messages respond to the customer journey. Explore our Klaviyo agency support, review the flow rebuild project, or use the Klaviyo flow build guide to brief your internal team.

.png)
Comments