Library / Guides / Klaviyo exclusions without jargon

Guidedtc

Klaviyo exclusions without jargonFlows that fight each other train people to mute you.

Exclusions are the craft. A buyer should not get cart. A subscriber should not get acquire coupons. Browse should not clone cart. You do not need a certification to understand this. You need a picture of who should not get which email, then you click the same picture into Klaviyo.

00

In plain words

Intern through CEO

Draw four people: subscriber who never bought, person with a cart, person who just bought, person who bought last year. They should not get the same email today.

  1. 01

    Draw four people: subscriber who never bought, person with a cart, person who just bought, person who bought last year. They should not get the same email today.

  2. 02

    Each flow has a 'do not enter if' list. That list is the product.

  3. 03

    If Placed Order is dirty, exclusions cannot save you. Fix the event first.

Who

Same lesson. Three jobs.

Read your row

Intern

What you actually do

Run steps 01 and 02 this week. Do not add a feature. On paper. Today.

Operator

What you protect

Protect the sequence. Each flow has a 'do not enter if' list. That list is the product.

CEO

What you refuse to fund

Do not fund more traffic or more seats until the scoreboard in this lesson is a number you will defend. If Placed Order is dirty, exclusions cannot save you. Fix the event first.

Steps

Do this in order

Why, then done when
  1. 01

    Draw the four people

    On paper. Today.

    Why: Settings without a picture are how you miss a collision.

    Done when: A sketch you could show an intern.

  2. 02

    Cart excludes buyers

    They already have a post-purchase job.

    Why: A coupon after payment is clumsy.

    Done when: A test purchase does not get cart.

  3. 03

    Browse is lighter than cart

    Different copy. Lower frequency. Does not clone.

    Why: Window shoppers are not abandoners.

    Done when: The two flows do not look like twins.

  4. 04

    Welcome excludes buyers

    They skipped that chapter.

    Why: Welcome-after-purchase is a bug.

    Done when: A test order is out of welcome.

  5. 05

    Win-back has a stop

    Finite. Then sunset.

    Why: Forever we-miss-you is how you become wallpaper.

    Done when: A stop rule you can point at.

Intern lab

Create a test profile. Buy. Wait an hour. See which emails arrive. If cart or welcome arrives, the exclusion is wrong. Fix that before any creative brief.

Why

Questions people actually ask

Pushback is normal

Can't we just lower frequency globally?

Global frequency hides collisions. The buyer still gets the wrong story. Exclusions are precise. Caps are a seatbelt, not a map.

Apply

Use-case pages for this leak

Shopify + Klaviyo

Working notes

DTC Retention Scorecard

Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.

Request the notes ↗
Next

If the leak is expensive, talk.

Email and WhatsApp stay open. A call is for installing the system.