Browse abandonment: the program that sits between ads and cart

The trigger: an identified user viewed a product, category, or search result and left the site without adding to cart or purchasing. The word "identified" is the catch — you need to know who they are, which means they're logged in or their email is tied to the session through a previous click. Anonymous sessions trigger nothing, because there's no address to send to.

The qualifying events, in order of intent:

Product detail page view. The user spent time on a product and didn't add. Cleanest trigger. Highest intent.

Category browsing. The user scrolled a category or collection page without engaging. Weaker signal but still worth acting on.

Search with no click-through. The user searched and left without tapping a result. Good input for catalog-gap analysis, low-intent as a send trigger. Don't build your flow off this one.

Message 1 — 1 hour after view.Product reminder. Subject: "Still thinking about [product]?" Body: the product they viewed, plus one or two similar items sharing an attribute (colour, category, price band). No discount. The job here is to re-anchor interest while the consideration is still warm. Thirty minutes feels surveillance-y; six hours loses the context. One hour is the sweet spot.

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 from one SKU to the shelf.

Message 3 — 72 hours after view (optional).The nudge. Subject: "Back to where you left off", or a small incentive if your program runs them. Most programs skip this third touch entirely and let the first two do the work. If you do include a discount, this is where it goes — never message 1. Discounting users who viewed without buying trains them to browse-and-wait, which is a training loop you don't want.

Cut the whole sequence the moment the user adds to cart (handoff to the abandoned cart flow) or makes any purchase. Continuing browse reminders after intent has advanced is annoying and actively dilutes the effect of the flow it should have handed off to.

Browse abandonment is more data-hungry than most lifecycle programs. Three things have to be in place before the flow works at all:

1. Identified browsing. Site analytics — Segment, Rudderstack, or direct to your ESP — attaching an email or known user_id to every product-view event. Without identity resolution, there's no program.

2. Product metadata at send time. Name, image, price, link. Most ESPs pull this via Liquid from a product catalog or via an API callout. Braze handles it through Catalogs; Iterable through data feeds. Whichever you use, the metadata has to refresh frequently enough that the email doesn't ship a stale price.

3. Related-product logic. To populate "similar items" in message 1 or "more in category" in message 2, you need a rule that picks candidate products by shared category, price band, or collaborative-filtering signal. Rudimentary works — "three other products in the same category, excluding the one they viewed" is a perfectly fine starting rule. Don't wait for a recommendation engine to ship.

The Braze Liquid reference covers the Liquid patterns for catalog lookups; other ESPs follow the same shape.

Gotcha 1: trigger fatigue.A user who browses daily will hit the trigger daily. Cap at one sequence per user per 7 days regardless of how many product pages they view. Skip the cap and you're sending four emails a week to your most engaged browsers — which is exactly the group you don't want to fatigue.

Gotcha 2: out-of-stock products.Message 1 ships an hour after the view. By then the product may have sold out, especially for drops or limited inventory. Check stock at send time. Out of stock? Substitute with similar items or skip the product-specific message entirely. A reminder for a product the user can't buy is worse than silence.

Gotcha 3: bot views.Scrapers, preview bots, and background-tab sessions all fire false views. Filter to "view for more than 15 seconds" or "two pageviews in the session" to strip the noise. Skip this and a non-trivial share of your sends go to robots who are, frustratingly, excellent at not converting.

Browse abandonment looks brilliant in last-click attribution, because users who would have come back anyway get credited to the reminder email. That number is a lie by default. 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 14-day purchase rate. If you're seeing above 30% in the attribution reporting, that's almost certainly natural-return behaviour being over-credited by last-click — the flow is doing real work, just not as much as the dashboard says. Size the investment case on the holdout number, not the attribution number. One is measurement. The other is marketing maths.

The holdout group design guide covers sizing and assignment for the test.

covers where browse abandonment sits on the roadmap relative to other investments — usually after welcome, winback, and cart abandonment are shipped, and before most category-specific campaigns. Build in that order and each program compounds off the last one.