Product recommendation blocks in email are one of the highest-leverage, most misused components in a DTC brand's retention toolkit. The potential is significant: an email that surfaces a product the subscriber is genuinely considering can drive click-through and purchase rates well above the baseline for campaign emails. The execution gap is also significant: most recommendation blocks in DTC email flows are showing products based on "frequently bought together" catalog logic, which means the subscriber is often seeing items similar to what they've already purchased rather than what they're likely to want next.
This playbook covers how to structure recommendation blocks across the most common Klaviyo flow types, what signal sources to use for each, and the failure modes that turn potentially high-performing blocks into noise that trains subscribers to skip over that section of your emails.
The Core Problem: What Signal Are You Actually Using?
Before worrying about the visual design or placement of recommendation blocks, the more fundamental question is: what's the underlying recommendation logic? Most Klaviyo-native recommendation blocks pull from one of three sources: (1) globally popular products, (2) products in the same category as the subscriber's last purchase, or (3) Klaviyo's co-purchase model, which is similar to Shopify's native rec API in that it aggregates across the platform.
All three of these are purchase-history-centric. They're also static at the point of email send — the recommendations are determined when the email is built or triggered, not at the moment of open. A subscriber who opened an email about a sale, browsed your site for 15 minutes after clicking through, and then opened the follow-up email three days later is getting recommendations that don't reflect anything they did in that browsing session.
The alternative is recommendations that pull from a live behavioral profile — one that captures the subscriber's on-site browsing behavior and updates it continuously, so that the email sent after a browsing session reflects what that subscriber was actually looking at. This requires a connection between your on-site behavioral tracking system and your email platform's profile properties. It's more infrastructure, but it's also a meaningfully different product for the subscriber.
We're not saying globally popular products are the wrong recommendation in every context — for welcome emails and early-engagement flows, showing your bestsellers to a new subscriber with no behavioral history is a reasonable fallback. The problem is when that fallback becomes the permanent default for engaged subscribers who have given you extensive behavioral signal that you're ignoring.
Recommendation Logic by Flow Type
Welcome Series
The welcome flow is your cold-start challenge in email. A new subscriber typically has either no purchase history or one recent purchase that triggered the subscription. What you have is: their acquisition source (which landing page they came from, which ad creative they clicked), and whatever browsing behavior they showed in the session that converted them to a subscriber.
For the first email in a welcome series, recommendation blocks should reflect the acquisition context. If they subscribed from a landing page about a specific product category, show products from that category — not your global bestsellers, which may be from a completely different category. If they came from a specific campaign creative, show products thematically related to that creative.
By the second or third email in the welcome series, you should have accumulated some post-subscription browsing behavior. If they clicked through from email 1 and browsed a specific collection, email 2's recommendation block should reflect that browsing. Welcome series that maintain static recommendation blocks across all three or four emails are wasting the behavioral signal the subscriber is generating between sends.
Post-Purchase Flows
Post-purchase is the flow where recommendation logic errors are most visible and most damaging to trust. Showing a subscriber the product they just bought, or something nearly identical to it, in the recommendation block of a post-purchase email is a notable failure — it reads as inattentive and reduces confidence in the brand's personalization capabilities.
Good post-purchase recommendation logic excludes the purchased product and its close variants, and surfaces complementary items based on genuine affinity modeling rather than just "frequently bought together from the same category." If someone bought a premium coffee grinder, "frequently bought together" might surface more coffee equipment. That might be right — or it might already be in their cabinet. A behavioral affinity model would consider what they were browsing before the purchase, which might surface something in an adjacent category they were considering but didn't act on.
The timing of post-purchase emails also matters for recommendation relevance. An immediate post-purchase confirmation email is the wrong place for cross-sell recommendations — the subscriber is in confirmation mode, not browsing mode. The 3-7 day follow-up email, once the initial purchase experience has settled, is a better entry point for a recommendation block with cross-sell intent.
Browse Abandonment
Browse abandonment is the flow where session-level behavioral data matters most, and where most implementations are too narrow. The standard browse abandonment email shows the specific product page the subscriber visited. That's a valid component — the subscriber did demonstrate interest in that product. But a single product recommendation block that only shows the browsed item and its variants misses the broader picture of what the subscriber was exploring in that session.
A more effective browse abandonment block shows: (1) the primary browsed product or products, and (2) 2-3 items from other parts of the catalog that the shopper's session behavior suggests they have affinity for. If someone browsed a specific jacket but also spent time in your accessory collection during the same session, a combined block that shows the jacket plus 2 relevant accessories reflects the full scope of their interest — and may trigger a combined purchase rather than just recovering the single-item consideration.
Winback Flows
Winback flows targeting lapsed subscribers present a different signal challenge: you have purchase history that may be many months old, and potentially little or no recent session data. The recommendation logic should be weighted heavily toward your current catalog's best new arrivals within the categories the subscriber has historically purchased from — not toward the exact product types they bought before, which may feel repetitive or irrelevant if the line has evolved.
For winback flows where the subscriber hasn't been on site recently, the recommendation block's job is discoverability, not conversion. The goal is to show them that there's something in the current catalog worth coming back for. This is one case where a broader editorial recommendation — "what's new in [category they love]" — can outperform a pure affinity model recommendation built on stale data.
Block Layout and Placement
The mechanics of how recommendation blocks are laid out within an email affect click rate independent of recommendation quality. A few consistently observed patterns:
Three-product horizontal layouts convert better than single-product featured placements in most DTC catalog contexts. The shopper's scan behavior applies to email layouts as well — showing three options gives the subscriber something to compare and evaluate rather than a binary "click or don't click" decision on a single product.
Placement in the lower third of an email, below the primary message, captures click-through from subscribers who read through the email rather than scanning for the first clickable element. Recommendation blocks placed too high compete with the primary email message and often get scrolled past. The exception is a dedicated "your picks" email where the recommendation block is the entire point — in that format, leading with the recommendations is appropriate.
Product image quality in email thumbnails matters more than it does on your site, because the smaller render dimensions amplify any composition or clarity issues. A product that photographs well at 800×800px may not read clearly at 180×180px in a three-column recommendation block. Run your actual recommendation candidate images at thumbnail size before finalizing the recommendation catalog subset you're drawing from for email.
Measuring Whether Your Blocks Are Working
The standard metrics — click rate on the block, attributed revenue per email — are necessary but insufficient for diagnosing recommendation quality. A high click rate on a recommendation block can mean the recommendations are good, or it can mean you have a high-engagement subscriber list that clicks most things. The more diagnostic metric is the click-to-purchase rate on recommendation block clicks specifically: among subscribers who clicked a recommendation, what fraction purchased?
A recommendation block with a 6% click rate and 8% click-to-purchase rate is performing better than one with an 8% click rate and 3% click-to-purchase rate, even though the raw click rate on the second is higher. The first block is sending qualified, intent-matched traffic to PDPs. The second is sending curious but unqualified traffic that bounces when it gets there.
Track recommendation block click-to-purchase rate separately from overall email click-to-purchase rate. If the block's click-to-purchase rate is materially below the rate for primary CTA clicks in the same emails, that's a signal that the recommendation relevance needs improvement — the block is getting clicks but not generating conversions at the rate a well-matched recommendation would.