Updated · 8 min read
Browse abandonment: the program that sits between ads and cart
Cart abandonment gets the attention because the intent signal is obvious: the user added to cart. Browse abandonment is quieter but catches a much bigger audience — every product view, category page, or search result that didn't convert. The per-user lift is smaller, but the volume of triggers is 10–20× higher. For most programs, browse abandonment is the biggest single revenue lever you haven't shipped yet.
Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
What counts as browse abandonment
The trigger is: an identified user viewed a product, category, or search result and left the site without adding to cart or purchasing. "Identified" is the catch — you need to know who the user is, which means they're logged in or their email is tied to the session through previous engagement.
Typical qualifying events:
Product detail page view — the user spent time on a product, didn't add. The cleanest trigger.
Category browsing — the user scrolled a category or collection page without engaging. Weaker intent, but still actionable.
Search with no click-through — the user searched and left without tapping a result. Interesting for catalog-gap learning, but low-intent as a trigger.
Cart abandonment is a user who decided to buy and paused. Browse abandonment is a user who considered buying and didn't. The messaging has to respect that difference.
The three-message structure
Message 1 — 1 hour after view.Product reminder. Subject: "Still thinking about [product]?" Body: the product they viewed, with one or two similar items that share an attribute (colour, category, price band). No discount. The goal is to re-anchor the interest while the consideration is fresh.
Message 2 — 24 hours after view.Social proof or category expansion. Subject: "Here's why customers love [product category]" or "More in [category]". Body: reviews, user content, or three curated picks from the same category. Still no discount. Widens the consideration set.
Message 3 — 72 hours after view (optional).The nudge. Subject: "Back to where you left off" or an offer if your program uses them. This is where a small incentive can be placed if you're comfortable running it — most programs skip this one and rely on the first two to do the work.
Cut the sequence the moment the user adds to cart (handoff to the abandoned cart flow) or makes any purchase. Continuing to send browse reminders after intent has advanced is annoying and dilutes the effect.
Data requirements
Browse abandonment is data-hungry compared to most lifecycle programs. You need:
1. Identified browsing. Site analytics (segment.io, Rudderstack, or direct to your ESP) that can attach an email address or a known user_id to the product-view event. Anonymous sessions don't trigger anything.
2. Product metadata. At send time, you need the product's name, image, price, and link. Most ESPs pull this via Liquid from a product catalog or via an API callout. Braze handles this through Catalogs; Iterable through data feeds.
3. Related-product logic. To show "similar items" in message 1 or "more in category" in message 2, you need a rule that selects candidate products by shared category, price band, or collaborative-filtering signal. Rudimentary is fine; a "three other products from the same category, excluding the one they viewed" rule works.
The Braze Liquid reference covers the Liquid patterns for catalog lookups; the pattern is similar in other ESPs.
Typical lift and gotchas
,
Gotcha 1: trigger fatigue.A user who browses daily will hit the trigger daily. Cap the frequency — one browse abandonment sequence per user per 7 days, regardless of how many product pages they view. Otherwise you're sending four emails a week to engaged browsers.
Gotcha 2: out-of-stock products. Message 1 goes out 1 hour later; by then, the product may have sold out (especially for drops or limited inventory). Always check stock at send time — if out of stock, substitute with similar items or skip the product-specific message entirely.
Gotcha 3: bot views.Scrapers, preview bots, and logged-in sessions in background tabs trigger false views. Filter to "view for more than 15 seconds" or "two pageviews in the session" to exclude the noise.
Measuring incrementality
Browse abandonment looks great in last-click attribution because users who would have come back anyway get credited to the reminder email. Measure the real lift with a holdout: randomly suppress 10% of users who qualify for the sequence, and compare their 14-day conversion rate to the sent group.
Expected holdout vs sent gap: 8–15% incremental lift on purchase rate within 14 days of trigger. If you're seeing >30% in the reporting, that's almost certainly natural-return behaviour being over-credited by last-click.
The holdout group design guide covers sizing and assignment for this test.
covers when browse abandonment should be prioritised relative to other lifecycle investments — usually after welcome, winback, and cart abandonment are shipped but before most category-specific campaigns.
Frequently asked questions
- What's the difference between browse and cart abandonment?
- Cart abandonment triggers when the user added an item to cart and left. Browse abandonment triggers when they viewed a product (or category) without adding. Cart is higher intent, smaller audience, higher per-user conversion. Browse is lower intent, larger audience, smaller per-user conversion — but larger total lift.
- Do I need to be logged in to trigger browse abandonment?
- The user needs to be identified — which usually means logged in, or their email tied to the browser session via a previous click from an email. Anonymous sessions don't trigger because there's no address to send to.
- How soon after browsing should the first email send?
- 1 hour is the default. Too quick feels surveillance-y (<30 min); too slow loses the context (>6 hours). 1 hour catches the user while the consideration is fresh but lets them get on with whatever else they're doing.
- Should I offer a discount in browse abandonment?
- Rarely in the first two messages. Users who viewed without buying often just need more information, not a price cut. Discounting too aggressively trains users to browse-and-wait. If you do include a discount, put it in the third message (day 3) as a final nudge — or skip the third message entirely.
- How often should browse abandonment trigger?
- Cap at once per user per 7 days. Engaged users browse frequently; without a cap, you'll send 3–5 browse emails a week to your best customers. One sequence per week per user is enough to capture the intent without fatiguing the list.
- What if the product they viewed is out of stock by send time?
- Check stock at send time via Liquid or an API callout. If out of stock, either substitute with 'similar items' (three products from the same category), or suppress the message entirely. Sending a reminder for a product they can't buy is worse than sending nothing.
- How do I know if browse abandonment is actually working?
- Run a 10% holdout. Expected incremental lift: 8–15% higher 14-day purchase rate in the sent group vs the suppressed group. Last-click attribution will show a much larger number (often 3× the real lift) because browse abandonment mostly re-credits users who would have returned anyway.
Related guides
Browse all →Referral program emails: the three flows that make a referral program work
Referral programs live or die on the lifecycle messaging around them. Here are the three flows every referral program needs — inviter prompt, invitee welcome, reward confirmation — and the timing and copy that make each convert.
Trial-to-paid: the seven-email sequence that converts 20%+ of free users
Trial conversion is the most financially leveraged lifecycle flow in SaaS — every percentage point of improvement compounds against CAC. Here's the seven-email sequence that reliably moves trial conversion from 5% to 20%+.
Replenishment emails: the lifecycle flow that buys itself
Replenishment emails remind users to re-order a consumable product before they run out. Done right, they generate the highest revenue-per-send in any lifecycle program because the purchase intent is already established. Here's the timing, data, and copy.
Price increase emails: how to raise prices without a churn spike
A price increase is one of the highest-risk lifecycle moments — done wrong, it triggers churn, public complaints, and a reputation dent that outlasts the extra revenue. Done right, most users accept the change without friction. Here's the sequence that works.
Free shipping threshold emails: the cart-value nudge that reliably lifts AOV
A user with $45 in their cart and a $50 free shipping threshold will add another item to hit the threshold — if they realise it. The right email at the right moment surfaces the gap and reliably lifts AOV 5–15%.
Review request emails: the timing that actually produces reviews
A review request sent at the wrong time gets ignored. Sent at the right time, it converts at 15–25% into a submitted review. Here's the timing logic, the message pattern, and why incentivising reviews almost always backfires.
Found this useful? Share it with your team.