Skip to main content

Best Practices for Setting Up Reclaim Flows in Klaviyo

To help brands fully capitalize on Reclaim, we recommend implementing five key Klaviyo flows designed to re-engage shoppers who are known to you but browsing anonymously. These flows leverage Reclaim’s identity resolution and event enrichment to trigger precise, personalized messages that reach users before they disappear from your funnel. By addressing session identification challenges such as expired cookies, cross-device usage, and logged-out sessions, Reclaim ensures that revenue opportunities lost due to these issues can be recovered. Platforms like Shopify and Klaviyo amplify this recovery potential by leveraging Reclaim's effective targeting capabilities.

The five recommended flows:

  1. Active on Site Reclaim – Detects and engages known visitors browsing your site.

  2. Viewed Category Reclaim – Identifies customers viewing product categories but not engaging further.

  3. Viewed Product Reclaim – Captures interest at the product level for cart-building intent.

  4. Added to Cart Reclaim – Detects when customers add products to cart.

  5. Checkout Started Reclaim – Converts users who started checkout, but didn’t complete purchase.

Each flow uses Reclaim-specific custom metrics, exclusion filters, and prioritization strategy to ensure contacts move through a clean, non-overlapping funnel while maintaining deliverability and personalization.


Before You Begin

We recommend maintaining your original Klaviyo abandonment flows. For each Reclaim event, simply clone the existing flow and replace the original trigger metric with the Reclaim equivalent.

  • Active on Site → Active on Site Reclaim

  • Viewed Category → Viewed Category Reclaim

  • Viewed Product → Viewed Product Reclaim

  • Added to Cart → Added to Cart Reclaim

  • Checkout Started → Checkout Started Reclaim

This approach ensures your creative, segmentation, and timing remain consistent while allowing Reclaim’s enriched event data to operate in parallel. This prevents overlap or double sends.


General Notes

Klaviyo Flows: Triggers use Reclaim-specific custom metrics.

Filtering: Strictly exclude overlapping metrics from default Klaviyo flows or other event sources.

Notes on Filtering:

  • Time-based filters (e.g., “zero times in the last 1 hour”) are essential to handle concurrency and race conditions.

Tracking: Ensure UTM tracking is enabled for all Reclaim-triggered messages.

💡 Tip: Add SMS to your Reclaim flows for improved reach and engagement.


1. Active on Site Reclaim

Purpose: Identify and engage known customers who are actively browsing but haven’t interacted further.

Trigger: Active on Site Reclaim

Recommended Filters: These filters ensure that when multiple abandonment events occur in a short time frame, customers enter only the highest-priority Klaviyo flow. This prevents duplicate messaging and keeps your engagement sequence organized and intentional.

Only add metric exclusions for flows that you are actively using. For example, if you are not using any category level flows, there is no need for filters that include the Viewed Category or Viewed Category Reclaim metric on this flow.

  • Placed Order zero times since starting this flow
    AND

  • Placed Order zero times in the last 1 day
    AND

  • Has not been in the flow in the last 14 days
    AND

  • Viewed Category zero times since starting this flow
    AND

  • Viewed Category Reclaim zero times since starting this flow
    AND

  • Viewed Product zero times since starting this flow
    AND

  • Viewed Product Reclaim zero times since starting this flow
    AND

  • Added to Cart zero times since starting this flow
    AND

  • Added to Cart Reclaim zero times since starting this flow
    AND

  • Checkout Started zero times since starting this flow
    AND

  • Checkout Started Reclaim zero times since starting this flow
    AND

  • Received email zero times in the last 7 days where the flow equals the original Active on Site flow

Messaging Focus: Light “welcome-style” content—thank them for visiting, introduce your brand value, or share top categories.

Optional SMS:Include a Conditional Split for SMS consent after the first delay and send a short greeting message before the first email.

For full setup details: See “Set up Reclaim for Active on Site in Klaviyo.”


2. Viewed Category Reclaim

Purpose: Retarget known users who viewed a category page but didn’t proceed to products or cart.

Trigger: Viewed Category Reclaim

Recommended Filters: These filters ensure that when multiple abandonment events occur in a short time frame, customers enter only the highest-priority Klaviyo flow. This prevents duplicate messaging and keeps your engagement sequence organized and intentional.

If you don't already have them, you should add flow filters to exclude anyone who has:

  • Placed Order zero times since starting this flow
    AND

  • Placed Order zero times in the last 1 day
    AND

  • Has not been in flow in the last 7 days
    AND

  • Received email zero times in the last 7 days where flow = [Native Viewed Category flow]
    AND

  • Viewed Category zero times in the last 1 hour

If flows are triggered off of Viewed Product, Viewed Product Reclaim, Added to Cart, Added to Cart Reclaim, Checkout Started and/or Checkout Started Reclaim, to add these flow filters:

  • Viewed Product zero times since starting this flow
    AND

  • Viewed Product Reclaim zero times since starting this flow
    AND

  • Added to Cart zero times since starting this flow
    AND

  • Added to Cart Reclaim zero times since starting this flow
    AND

  • Checkout Started zero times since starting this flow
    AND

  • Checkout Started Reclaim zero times since starting this flow

If an additional vendor is part of your identity stack, make sure to apply the following flow filters:

  • Viewed Product [additional vendor metric] zero times since starting this flow
    AND

  • Added to Cart [additional vendor metric] zero times since starting this flow
    AND

  • Checkout Started [additional vendor metric] zero times since starting this flow

Dynamic Variable Highlights:

Name: {{ event.Name|default:'' }}

URL: {{ event.URL|default:'' }}

Always use the |default:'' filter to prevent blank outputs.

Optional SMS: Add a short “Still shopping for [Category Name]?” message before your first email.

For full setup details: See “Set up Reclaim for Category Views in Klaviyo.”


3. Viewed Product Reclaim

Purpose: Recover interest from users who viewed product pages but didn’t add to cart.

Trigger: Viewed Product Reclaim

Recommended Filters: These filters ensure that when multiple abandonment events occur in a short time frame, customers enter only the highest-priority Klaviyo flow. This prevents duplicate messaging and keeps your engagement sequence organized and intentional.

If you don't already have them, you should add flow filters to exclude anyone who has:

  • Placed Order zero times since starting this flow
    AND

  • Placed Order zero times in the last 1 days
    AND

  • Has not been in flow in the last 7 days
    AND

  • Received Email zero times in the last 7 days where flow equals (existing viewed product/browse abandonment flow)
    AND

  • Viewed Product zero times in the last 1 hour

If flows are triggered off of Added to Cart, Added to Cart Reclaim, Checkout Started and/or Checkout Started Reclaim, to add these flow filters:

  • Added to Cart zero times since starting this flow
    AND

  • Added to Cart Reclaim zero times since starting this flow
    AND

  • Checkout Started zero times since starting this flow
    AND

  • Checkout Started Reclaim zero times since starting this flow

If an additional vendor is part of your identity stack, make sure to apply the following flow filters:

  • Added to Cart [additional vendor metric] zero times since starting this flow
    AND

  • Checkout Started [additional vendor metric] zero times since starting this flow

Dynamic Variable Highlights:

Name: {{ event.Name|default:'' }}

Image URL: {{ event.ImageURL|default:'' }}

Price: {{ event.Price|default:'' }}

Product URL: {{ event.URL|default:'' }}

Messaging Focus:Show the last viewed item dynamically, reinforce social proof, and highlight “Still available” urgency.

Optional SMS: Short “Still thinking about {{ event.Name|default:'' }}?” message before the first email.

For full setup details: See “Set up Reclaim for Viewed Product in Klaviyo.”


4. Added to Cart Reclaim

Purpose: Re-engage known users who added items to their cart but didn’t start checkout.

Trigger: Added to Cart Reclaim

Recommended Filters: These filters ensure that when multiple abandonment events occur in a short time frame, customers enter only the highest-priority Klaviyo flow. This prevents duplicate messaging and keeps your engagement sequence organized and intentional.

If you don't already have them, you should add flow filters to exclude anyone who has:

  • Placed Order zero times since starting this flow
    AND

  • Placed Order zero times in the last 1 days
    AND
    Has not been in flow in the last 7 days
    AND

  • Received Email zero times in the last 7 days where flow equals (existing add to cart flow)
    AND

  • Added to Cart zero times in the last 1 hour

If flows are triggered off of Checkout Started and/or Checkout Started Reclaim, add these additional flow filters:

  • Checkout Started zero times since starting this flow
    AND

  • Checkout Started Reclaim zero times since starting this flow

If an additional vendor is part of your identity stack, make sure to apply the following flow filters:

  • Checkout Started [additional vendor metric] zero times since starting this flow​

Dynamic Variable Highlights:

Name: {{ event.Name|default:'' }}

Image URL: {{ event.ImageURL|default:'' }}

Price: {{ event.Price|default:'' }}

Quantity: {{ event.Quantity|default:'' }}

Product URL: {{ event.URL|default:'' }}

Messaging Focus:Emphasize urgency and scarcity. Include a clear CTA to resume the cart.

Optional SMS: Send a quick reminder like “Your cart’s waiting!” before the first email.

For full setup details: See “Set up Reclaim for Add to Cart in Klaviyo.”


5. Checkout Started Reclaim

Purpose: Recover identified users who initiated checkout but didn’t complete purchase.

Trigger: Checkout Started Reclaim

Recommended Filters: These filters ensure that when multiple abandonment events occur in a short time frame, customers enter only the highest-priority Klaviyo flow. This prevents duplicate messaging and keeps your engagement sequence organized and intentional.

It is important to note that you want your flow logic to prioritize this flow over all others because it’s the lowest in the funnel.

Edit or update your flow filters to include the following:

  • Placed Order zero times since starting this flow
    AND

  • Placed Order zero times in the last 1 day
    AND

  • Has not been in flow in the last 7 days
    AND

  • Checkout Started zero times in the last 1 hour
    AND

  • Received email zero times in the last 7 days where flow = [Native Checkout Started flow]

Dynamic Variable Highlights:

Checkout URL: {{ event.extra.checkout_url|default:'' }}

Product Title: {{ item.product.title|default:'' }}

Product Price: {{ item.product.price.amount|default:'' }}

Image URL: {{ item.product.image.0.src|default:'' }}

Quantity: {{ item.quantity|default:'' }}

Messaging Focus: Lead with urgency (“Your checkout is waiting”) and reinforce trust (shipping, returns, guarantee).

Optional SMS: Send a short reminder: “Your items are almost yours—complete checkout now.”


Flow Optimization Best Practices

To get the most from your Reclaim flows:

  • Enable UTM tracking for all Klaviyo links.

  • Keep naming conventions clear ([Reclaim] Added to Cart, etc.) for visibility.

  • Stagger delays across flows from top to bottom of the funnel. Example flow delay structure:

    • Active on Site → 2 hrs

    • Viewed Category → 1.5 hrs

    • Viewed Product → 1 hr

    • Added to Cart → 30 min

    • Checkout Started → 15 min

  • Exclude higher-funnel events from lower-funnel flows to prevent duplicate sends.


Reclaim Setup Guides

For complete implementation steps, including event scripts, dynamic field lists, and SMS setup, see:

Did this answer your question?