Every re-match must unmatch vs fixed-interval re-entry: leave the segment then return vs calendar cooldown

Every-re-match requires the person to stop matching trigger/filter conditions, exit the automation, then match again (re-matching while still inside does not queue a new trip); fixed-interval re-entry re-admits them after N days/hours if they still match when the interval elapses—still never while an active trip is running.

What is the difference between must-unmatch re-match and fixed-interval re-entry?

After someone leaves a flow/journey once, the next question is “when may they come back?” Two common answers:

1. Every re-match (must unmatch, then rematch): leaving the automation is not enough if they still match the trigger segment. They must fall out of the condition (no longer inactive-14d, or no longer VIP), then match again. Rematching while still inside an active trip does not start a new trip.
2. Fixed-interval re-entry: a cooldown elapses from exit (or sometimes from entry—see the eligibility-clock post); when N days pass, if they still match, they enroll again—provided no concurrent active trip.

Closely related but different angle: flow re-entry once vs cooldown window focuses on once vs window; here the focus is whether leaving the segment is mandatory vs still-matching with enough calendar gap. Also eligibility clock from exit vs entry and segment enters vs already-in vs exits.

Comparison table

Timeline vignette: inactive 14 days

Day 0: last purchase; still active.
Day 15: enters inactive_14d → enrolls winback journey.
Day 20: finishes journey but still hasn’t purchased → still matches segment.

• Every re-match: no new enroll until they purchase (unmatch inactive) and later go quiet for 14 days again.
• Fixed-interval e.g. 30 days from exit: on day 50, if still inactive, they enroll again without an intermediate unmatch.

For monthly VIP the reverse instinct applies: you rarely want the same VIP message every 30 days to someone who never left VIP unless the content is deliberately periodic.

Iranian store and SaaS examples

Fashion store — abandoned cart: you usually do not want the same unchanged cart to re-enroll every 24 hours without an unmatch. Prefer exit on purchase/empty cart, then rematch on a new/meaningful cart update.

SaaS — trial_ending: if they still match after the flow ends, fixed-interval may email renewal every week; every-re-match blocks spam unless status changes (renewed → unmatch; new trial later → rematch).

Concurrent active trips

Mature engines almost always refuse a new re-entry while a trip is still active—under both modes. Mid-trip rematch is either ignored or noted for after exit; test, don’t guess.

Truthful Leadara mapping

With Leadara segments, events, journeys, and email/SMS:

• Distinguish segment-enters from already-in triggers;
• Make re-entry policy explicit (once, cooldown, or must leave and return);
• Periodic inactive nurture ≈ fixed-interval;
• Status loops you must not repeat ≈ require real segment exit (purchase, reactivation, leaving VIP) to approximate every-re-match.

If Customer.io labels “Every re-match” vs “At fixed intervals” and Leadara UI uses different words, describe behavior with segment conditions + re-entry window + exit on conversion—don’t claim identical labels.

Leadara AI Chat is an internal team assistant—not a customer-facing live-chat bot.

When to choose which

Practical steps

1. Brief: “must leave the segment” or “every N days if still inside”?
2. Lock cooldown origin (from exit vs from entry).
3. Cap re-entries per 90 days.
4. Three-profile QA: still-in-segment after exit / unmatch→rematch / active trip.
5. Take exit-on-conversion seriously.
6. Review re-enroll vs unmatch rate monthly.
7. Change copy on 2nd/3rd pass if using fixed-interval.

Common mistakes

• Assuming flow exit equals segment unmatch;
• Fixed-interval with no cap on always-true segments;
• Every-re-match on inactive with no real activity path → silent enroll death;
• Ignoring concurrent trips;
• Mixing once-only with every-re-match.

FAQ

If they re-match while still inside, do they restart on exit?

Under classic every-re-match, mid-trip rematch usually does not queue a new trip; after exit you need a fresh match edge—verify in your engine.

Fixed interval but still in an active trip?

Usually no new enroll until the current trip ends, even if N has elapsed.

Which mode for abandoned cart?

Exit on purchase + re-entry only when a new/meaningful cart appears (unmatch→rematch-like), not every N hours on the same cart.

Which mode for VIP nurture?

If the message is about newly becoming VIP, every-re-match or once. If it is a monthly newsletter to all VIPs, a campaign/fixed cadence may beat flow re-entry.

Is this the same as a cooldown window?

Cooldown is usually the fixed-interval family. This article stresses mandatory unmatch vs allowing still-matching.

Clock from exit or from entry?

Critical for fixed-interval—read the eligibility-clock post.

Does Live Chat explain this to customers?

Live Chat is human support. Re-entry policy is an internal product decision; AI Chat is only a team dashboard assistant.

How do I summarize for the PM?

“Either they must leave the segment and come back, or every N days they may return while still matching—never concurrent with an active trip.”

Next step

Take one real inactive segment and one VIP segment, lock every-re-match vs fixed-interval in the brief, run the three QA profiles, then set max counts and second-pass copy.

Cap counts and message fatigue

Even with every-re-match, people can bounce in and out of a segment (small purchase, inactive again). Set a practical cap: e.g. max 3 winbacks per 90 days. Fixed-interval with no cap on always-true segments becomes spam quickly.

Signals you chose the wrong mode

• Complaints “same inactive email every week” → fixed-interval too loose or uncapped;
• Zero re-enrolls despite lasting inactivity → every-re-match with no real unmatch path;
• Two parallel messages from two trips → concurrent-trip rule unclear, or two journeys on one segment.

Align with segment trigger type

If your trigger is already in rather than enters, re-entry behavior changes. Before debating unmatch, know which edge enrolls you—re-read the segment trigger post.

Numeric example for the product meeting

Assume 1,000 people in inactive_14d. Winback journey lasts 10 days. After exit, 800 still inactive.

• Under fixed-interval 30 days from exit, around day 50 you may re-enroll up to ~800—unless you cap.
• Under every-re-match, only people who purchase (unmatch) and later go quiet 14 days return; next month might be 50–100.

Neither is inherently right; the question is message budget and brand patience. Put the number on a product slide before launch so nobody is surprised.

Coordination with gamification and web push

If loyalty points or web push also fire on the same inactive segment, phase email/SMS re-entry with those channels so one person does not get triple winback in a week. Only assume channels Leadara documents for your workspace.

Related reading

• Flow re-entry once vs cooldown window: never again vs after N days
• Eligibility clock from exit vs from entry
• Segment Enters vs Already-in vs Exits trigger: new joiners only, everyone currently in, or people who just left