Klaviyo sees clicks. We see hesitation. Why both matter.

The Klaviyo gap

Klaviyo fires its abandoned-cart flow when a shopper adds to cart and leaves. That is a strong signal because the shopper explicitly committed to a product. The important boundary is simple: the flow can act on cart-stage behavior, not on every product-page visit.

But here's the catch: many shoppers leave before adding to cart.

They land on the product page. They look at the photos. They click the size chart, get confused, and close the tab. Klaviyo never sees them. Their behavior — the hesitation, the friction, the specific reason they left — is invisible to the cart-abandonment flow.

Where the missed shoppers go

The pre-cart drop-off triggers teams most often investigate:

• Size uncertainty — shopper hovers and rage-clicks the size chart, leaves
• Shipping cost surprise — shopper enters their zip in the shipping calc, sees the cost, leaves
• Out-of-stock variant — shopper picks a size, sees "out of stock," dead-clicks the unavailable button, leaves
• Price comparison — shopper opens 4 product pages on your competitor's site (you can detect the rapid back-tab pattern)
• Decision fatigue — shopper visits 3 times across 3 days, never adds to cart

Each of these is a specific reason. Each one needs a different email. Klaviyo's cart-abandon flow sends the same email to all of them — because all Klaviyo knows is that they didn't buy.

What "behavior emails" actually look like

The shopper from the size-chart example. Generic abandoned-cart email:

"You left a Wool Runner in your cart!"

That email never fires because they never added to cart. And even if it did, it wouldn't address why they left.

A behavior email, written by AI but in the founder's voice:

Hi Jane, saw you were looking at the Wool Runner Mizzles in Charcoal but the sizing chart threw you off. Totally fair — if you want help choosing a size, reply to this email and we can point you to the store's sizing guidance and returns policy. — Khadin

Three things make this work:

1. Specific friction acknowledged. The shopper feels seen, not surveilled.
2. Real solution offered. Sizing guidance, free returns, founder-on-call.
3. Founder voice. Not template language. Not marketing-speak.

Do not treat this example as a conversion benchmark. The useful lesson is the message design: acknowledge the observed friction, offer a real answer, and make the sender sound like a person who can help.

Run both, not one

Klaviyo handles cart-stage. Behavior emails handle pre-cart-stage. Different shoppers, different windows, both essential.

The combined pipeline:

1. Shopper lands → behavior tracking watches for friction
2. If they add to cart and leave → Klaviyo's flow handles it
3. If they leave BEFORE adding to cart → behavior emails handle it
4. If they're still hesitating after both → a store's consented automation can route them to a later follow-up, with the trigger and message kept explicit

Many operators think Klaviyo "covers email." It covers one important slice. The pre-cart slice is a different measurement and messaging problem, and Klaviyo's cart-abandonment trigger does not touch it.

That's the gap this workflow is designed to help you inspect.