What we do
Tools
Industries
Department
How we workLet's talk →
Home/Klaviyo/Klaviyo Flows
Klaviyo

Klaviyo Flows: What Starts One, What Filters It, and Why Someone Got Skipped

A flow is a sequence of emails, texts or both that Klaviyo sends on its own once something happens to a profile. Most flow trouble comes down to three settings: the trigger, the filters, and Smart Sending. Here's how each one behaves, then the mistakes that make a flow go quiet.

What can start a Klaviyo flow

Added to list: someone joins a list, usually through a signup form. The usual start for a welcome series.

Flows Create flow Build your own

Added to segment: someone's data changes so they newly qualify for a segment, such as passing a spend threshold.

Metric: an event happens, like Started Checkout, Placed Order or a custom event your own systems send in.

Date property: a date on the profile comes round, such as a birthday or a renewal date.

Price drop and low inventory: a product someone looked at or carted gets cheaper, or is running out.

Not a trigger: Opened Email and Clicked Email. Engagement metrics can't start a flow, though filters and splits can use them.

Why a Klaviyo flow skipped someone it should have reached

Open the profile, look at its activity, and compare it with each of these.

They were already in the segment when the flow went live

How you'll know: A segment-triggered flow sat at zero for days, even though the segment has thousands of people.

Fix: Segment flows only start for people who newly enter the segment. Anyone already there stays out. If they need the messages too, send them a one-off campaign rather than editing the segment to force entry.

A trigger filter was treated like a profile filter

How you'll know: The flow is metric-triggered, the filter says something like "Value is at least $100", and people who qualified later never got in.

Fix: Trigger filters look at the event that started the flow, and only when it starts. Profile filters look at the person, at entry and again before every message. Put the rule in the box that matches what it's checking.

Smart Sending held the message back

How you'll know: The profile shows the flow message as skipped, right after they got a campaign.

Fix: By default Klaviyo won't send another email within 16 hours, or another text within 24, of the last one. Leave it on for marketing flows. Switch it off on the individual messages that must arrive, such as a receipt-style follow-up.

A profile filter failed halfway through

How you'll know: They got email one, missed email two, then got email three.

Fix: That's how profile filters work: a person who fails the check before a message skips that message and carries on to the next step. If missing one message should end the sequence, use a conditional split that exits instead.

Re-entry is set to once, and they'd been through before

How you'll know: A repeat buyer gets the post-purchase flow on their first order and never again.

Fix: Re-entry is a trigger setting: once, every time they qualify, or after a waiting period. It's only checked when someone enters, so pick it before the flow goes live.

When the moment that should start the flow happens outside Klaviyo

Every trigger above reads data Klaviyo already holds. Shopify's native integration brings in a lot of it, which is why the standard store flows work well out of the box. The trouble starts when the real moment sits somewhere else: a customer crosses a loyalty tier calculated in another app, a trade account orders through a portal, a subscription renews in a billing tool, a support ticket closes.

Klaviyo can't trigger on any of that until it arrives as an event or a profile property. Once it does, it's an ordinary metric or segment trigger, and the flow you already built just starts working. Segments behave the same way, and our Mailchimp segmentation page covers the equivalent problem on that platform.

n-frames builds that missing feed for Klaviyo flows: the event sent in with a stable name and properties, the profile field that a date or segment trigger reads, and a check that tells someone when events stop arriving. The wider map of Klaviyo's APIs is on our Klaviyo hub page.

Which trigger suits which Klaviyo flow

The common store flows, with the trigger that usually fits and the thing that trips them up.

Flow Usual trigger Watch for
Welcome series Added to list Someone who signs up at checkout may already be a customer. A profile filter on Placed Order keeps first-purchase discounts away from them.
Abandoned cart and browse abandonment Metric: Started Checkout or Viewed Product A filter that drops anyone who has placed an order since the flow began, so a buyer doesn't get a reminder for what they just bought.
Post-purchase and review requests Metric: Placed Order, or a fulfillment event Order date and delivery date can be a week apart. A review request timed off the order can land before the parcel does.
Win-back Added to segment, or a metric with a long delay Only orders Klaviyo can see count. Purchases through a wholesale portal, marketplace or shop counter look like silence.
Birthday, anniversary or renewal reminder Date property The date has to be on the profile in a format Klaviyo reads as a date. Renewal dates held in a subscription tool need syncing over first.
Price drop or back-in-stock style alerts Price drop or low inventory Both read Klaviyo's catalog. If prices or counts live in another system, the catalog has to be current or the alert is wrong.

Questions people ask

What is a Flow in Klaviyo?

An automated series of email and SMS messages that starts when something happens to a profile: joining a list or segment, an event like a placed order, a date on the profile, or a price drop on something they viewed. Inside it you add time delays, conditional splits and the messages themselves. Other platforms call the same thing an automation or a workflow.

What is Smart Sending in Klaviyo?

A setting that skips a message if the person got one on the same channel recently. The default window is 16 hours for email and 24 hours for SMS. Each flow message has its own on or off switch, so you can leave it on for promotional steps and turn it off for the ones that must always go out.

How do segments work with Flows in Klaviyo?

Two ways. A segment can be the trigger, in which case the flow starts when someone newly qualifies. Or segment membership can be a profile filter or split inside a flow that starts some other way. Segments update as profile data changes, so they're only as current as the data feeding them.

Which Klaviyo Flows do most stores run?

Welcome series, abandoned cart, browse abandonment, post-purchase follow-up and win-back. Klaviyo ships templates for all of them, so most stores edit a template rather than starting from a blank canvas. Birthday and price drop flows are the next most common.

Can a Klaviyo Flow trigger off something outside Klaviyo's native integrations?

Yes, once that something is sent into Klaviyo through its API as an event or a profile property. Until then the flow has nothing to watch. A wholesale order, a loyalty tier change or a renewal in a separate billing tool all need that step first.

Why didn't my Klaviyo flow send to someone?

Usually one of five things: they were already in the trigger segment before the flow went live, a trigger filter or profile filter excluded them, Smart Sending skipped the message, re-entry was set to once, or the message was still in draft or manual mode. The profile's activity feed shows which.

Who can build a custom trigger for a Klaviyo flow?

That's a job n-frames takes on: we get the event or property from the system where it actually happens into Klaviyo, named so your flows and segments can use it, with retries and an alert if it stops.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.