Library / Tool / Klaviyo flow score: events, jobs, collisions, RPR

ToolHow to wire it

Klaviyo flow score: events, jobs, collisions, RPRIf campaigns are doing a flow’s job, you do not have lifecycle. You have a calendar.

This scorecard is how an intern scores the Klaviyo operating layer before anyone writes a subject line. Event truth, core flows on, exclusions, campaign impersonators off, sunset, RPR as a number you would say in a meeting. Each row is a point. Ship the two lowest gaps for 90 days.

00

The short version

Intern through CEO

This scorecard is how an intern scores the Klaviyo operating layer before anyone writes a subject line. Event truth, core flows on, exclusions, campaign impersonators off, sunset, RPR as a number you would say in a meeting. Each row is a point. Ship the two lowest gaps for 90 days.

  1. 01

    Score before creative. A beautiful welcome coupon on a dirty event is theatre.

  2. 02

    Core set is finite. Twenty tiny flows that stack score worse than four clean ones.

  3. 03

    RPR on flows is the headline. Open rate is a meeting.

  4. 04

    Impersonator campaigns are the fastest points to recapture — turn them off.

  5. 05

    Shopify Email plus Klaviyo both sending fails the sender row.

Who

Same system. Three jobs.

Read your row

Intern

What you actually do

Audit, score, walk, kill a thief. You are the score clerk.

Operator

What you protect

Events, jobs, exclusions, pulses. Peak rule. RPR. One ESP.

CEO

What you refuse to fund

Lifecycle is a score you can defend. Until it exists, more creative is more stack.

Wire

How to connect it

Objects, then edges

Placed Order, core flows, exclusion map, campaign impersonators, RPR, sunset, SMS collision, holdout.

  1. 01

    Dirty Placed Order → fail event row; stop creative

  2. 02

    Welcome/cart/post-purchase/win-back → jobs, not clones

  3. 03

    Campaign doing a state job → pause campaign

  4. 04

    Peak → flows stay on

Steps

Do this in order

Why, then done when
  1. 01

    Event sample

    Three orders vs Klaviyo.

    Why: Theatre filter.

    Done when: Pass/fail.

  2. 02

    Score the rows

    Below. Sum.

    Why: Two worst gaps become the 90.

    Done when: Score posted.

  3. 03

    Name two gaps

    90 days. Pause extra work.

    Why: A 20-gap list is how nothing ships.

    Done when: Two named.

  4. 04

    Kill one impersonator

    This week.

    Why: Immediate manners.

    Done when: Campaign off.

  5. 05

    Path walk

    View→cart→buy. List messages.

    Why: Collisions hide in unit tests.

    Done when: Stack found or clean.

Intern

Three-order audit, tick rows, path walk, turn off one thief campaign. You are not writing Q4 creative.

CEO

Refuse a creative retainer until this score exists and two gaps are named. Campaigns on a missing lifecycle raise unsubscribes.

Failure

All default flows on, double pixel, full-list Thursday, flows paused in peak, RPR a vibe.

Test

Event sample plus path walk. Score is a number. Two gaps on a 90-day note.

Why

Questions people actually ask

Pushback is normal

Can we score after the campaign calendar is set?

No. The calendar may be the impersonator. Score first.

We don’t have RPR handy.

Then the RPR row is 0 and week one is learning where it lives. Do not skip the rest.

SMS too?

If SMS clones email cart, you fail the collision row. Channel jobs are part of the score.

Sheet

Score it this week

0% · 0/12

Each row is a pass/fail. 0% is not a grade for the brand — it is whether the objects exist. Under 50% means do not add traffic. 50–80% means finish write-in. Above 80% means review Monday, then the next leak.

  1. Placed Order matches finance on a 3-order sample

    Value, items, refunds. 1 if pass.

  2. Welcome exists and is not only a coupon dump

    1 if a job besides discount-first.

  3. Cart/checkout not three identical panics

    1 if timing/proof differ or fewer, better emails.

  4. Post-purchase is not review on day zero

    1 if delay or use/shipping first.

  5. Win-back has a stop

    1 if finite. Forever we-miss-you = 0.

  6. Exclusion map: placed excludes cart; path walk clean

    1 if a walk did not stack.

  7. No campaign impersonating a core flow

    1 if last 10 sends were tagged and thieves off.

  8. Flows stay on in peak (rule written)

    1 if written. Pause-as-plan = 0.

  9. One marketing sender (Shopify Email off if Klaviyo owns)

    1 if no dual welcome.

  10. Flow RPR (or flow revenue) is a number you would say aloud

    1 if yes. Vibe = 0.

  11. Sunset/unengaged excluded from the next blast

    1 if yes. Museum mailed = 0.

  12. Two gaps named for 90 days

    1 if written. 20-item wishlist = 0.

This week

This week: score, two gaps, one impersonator off, path walk. Flows stay on. No new campaign concept as the main work.

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 — not for a tour of tools.