Browse abandonment is the flow brands add third, after cart and checkout, and it is the one most likely to be built wrong. Done properly, it catches the largest audience in your funnel: people who looked at a product and left without adding it to cart. Done badly, it pulls high-intent shoppers out of your cart recovery sequence, doubles up sends, and burns list engagement on your lowest-intent visitors.
The difference comes down to three decisions: the trigger, the suppression logic, and how aggressively you let it fire. This covers all three.
Where browse sits in the funnel, and why that changes everything
The funnel hierarchy is simple: checkout beats cart beats browse. Someone who started checkout showed more intent than someone who added to cart, who showed more intent than someone who only viewed a product page.
Every setup decision follows from that. Browse abandoners get fewer emails, softer messaging, no incentives, and they must never receive browse emails when they qualify for a higher-intent flow. A browse flow that ignores the hierarchy is not adding coverage, it is downgrading your best prospects into your weakest sequence.

The trigger: Viewed Product, not Active on Site
Klaviyo gives you two candidate triggers and one of them is a trap.
Viewed Product fires when an identified profile views a product page. This is the trigger to use. It carries the product data you need for dynamic blocks, and it fires on a specific, meaningful action.
Active on Site fires when a cookied profile visits any page. It tells you nothing about what they looked at, carries no product context, and fires constantly. Do not build browse abandonment on it.
One constraint to accept up front: browse abandonment only works for identified profiles, meaning people who are cookied through a previous email click or a form fill. Anonymous traffic is invisible to this flow. Your browse flow reach is a function of your list size and your click activity, which is why it performs better on mature programmes than new ones.
Suppression: the filters that stop cannibalisation

This is where the flow either protects your cart recovery revenue or eats it. Two layers.
Exclude anyone further down the funnel. The flow filter on your browse flow should require that the person has not Added to Cart and not Started Checkout and not Placed Order since starting the flow. Note the logic: these are AND conditions, because you mean “none of these happened.” Written with OR, the filter passes anyone who fails a single condition, and shoppers who added to cart still fall into browse. Same trap as in cart flows, same silent revenue leak. Klaviyo re-checks filters before each send, so someone who views a product, gets browse email 1, then adds to cart the next day exits the browse flow automatically and lands in cart recovery where they belong.
Throttle repeat entries. Viewed Product fires far more often than checkout events. Without a control, an engaged browser can re-trigger the flow every few days and get nudged into unsubscribing. Add a flow filter: has not been in this flow in the last 30 days. Fourteen days is the aggressive end, 30 is the safe default. This one filter is the difference between a browse flow that feels helpful and one that feels like surveillance.

Turn Smart Sending off in this flow
Same as cart and checkout, and for the same underlying reason: an abandonment flow is the one place you cannot afford a silently skipped send.
Smart Sending suppresses anyone contacted in the last 16 hours (or whatever your window is). On a browse flow that sounds harmless, since browse is low intent. But the person who viewed a product an hour after getting your campaign is showing you fresh, specific interest, and that signal is exactly what the browse flow exists to catch. Skipping it because they got a newsletter this morning throws away the trigger you built the flow for.
The rule holds across all three abandonment flows: Smart Sending off in browse, cart and checkout. Frequency control for these belongs at the flow level, through the trigger itself, the suppression filters, and the 30-day re-entry throttle, not through a blanket 16-hour skip that fires blind to intent.
The sequence: shorter and softer than cart
Two emails maximum. Browse abandoners have not signalled enough intent to justify three touches, and no incentive belongs anywhere in this flow. A discount for viewing a product page trains your entire cookied list to browse and wait.
Email 1, around 2 hours after the trigger. A light, editorial touch. Dynamic block showing the viewed product, one line of copy framed as helpfulness rather than pursuit: “still thinking about this?” reads fine, “you forgot something” does not, because they did not forget anything, they looked at a page. Include 2 to 4 related products, because unlike a cart abandoner, a browser may have rejected that specific item.
Email 2, around 24 hours later, optional. Social proof on the viewed product or category: reviews, press, a bestseller angle. If you only build one email, you lose little. Past two emails, browse flows generate unsubscribes faster than orders.
Test the dynamic product block with a real cookied profile before going live. Viewed Product blocks break the same way cart blocks do, and a browse email with an empty product block is pure noise.
Priority order
- Confirm your cart and checkout flows are solid first. Browse is the third flow you build, never the first. If cart recovery leaks, fix that before adding a lower-intent layer on top.
- Build on Viewed Product, not Active on Site.
- Set the suppression filters with AND logic: no add to cart, no checkout, no order since starting the flow.
- Add the 30-day re-entry throttle.
- Leave Smart Sending on.
- Ship two emails, no discount, related products in email 1.
More advanced layers sit on top once this is live: branching by number of sessions or products viewed, splitting new visitors from returning customers with different messaging, and category-level browse flows for your hero collections. All of them depend on the suppression foundation being right first. If your browse and cart flows are both running and you are not certain who is ending up in which, that overlap is worth auditing before anything else, because it is the most common silent leak in a three-flow abandonment stack.
Free abandonment stack audit
If you want a second pair of eyes on your browse, cart and checkout flows, or you suspect your flows are overlapping and pulling shoppers into the wrong sequence, book a free 30-minute audit with us. We will map who enters which flow and where the suppression leaks.
Or if you want to talk through strategy first: Book a strategy call
Jamie Watkins, Director at UndergroundEcom
[LinkedIn] | [UndergroundEcom.com]

