Date-Bounded Sequence Variants

Anchor a sequence on a future event (launch, webinar, sale start, Black Friday) and route subscribers by how far they are from it. You can run two or three variants of the same nurture in parallel: long arcs for early signups, compressed pacing for mid-cohort, single-email heads-ups for last-minute joiners. Same trigger, same form. Different copy depending on runway.

Why use this

A single drip sequence assumes every subscriber has the same time horizon. Real launches don't work that way. Someone who joins your waitlist 21 days before launch wants a slow product-context arc. Someone who joins 3 days before needs a Monday heads-up, not a "let me tell you about our vision" email that lands the day after launch.

Date-bounded variants let you ship the right cadence to each cohort automatically. No manual segmentation, no copy/paste of half-edited sequences, no late signups dropping into a long arc that gets cut off by the launch broadcast.

How to set up a variant

Open any sequence in Email & Automation > Sequences. In the sequence settings panel you'll see three new fields:

A subscriber's distance to the event is calculated as (event_date - signup_time).days. If their distance falls between min and max (inclusive on both sides), they enroll in this variant.

Example. Set event date to 2026-06-01 03:00 UTC, min to 7, max to 13. A subscriber who signs up on May 22 is 10 days from launch. They fall inside the 7-13 window so they enroll. A subscriber who signs up on May 14 is 18 days out: they don't match this variant.

Cross-validation rules

ILLIXIS checks two things when you save:

• Max must be greater than or equal to min. A window of 14-7 makes no sense; you'll get a 400 with the field highlighted.
• Ends-at must be on or before the event date. A sequence can't run past the event it orbits. If you also set an Ends at date, it must be ≤ the event date.

The three-variant pattern

The cleanest setup for a 21-day pre-launch is three sibling sequences listening on the same trigger:

All three share the same event_date and ends_at (= event date). Windows don't overlap, so every signup lands in exactly one variant.

You can scale this pattern up or down. For a 7-day product release window, two variants (Full 4-7d, Short 0-3d) might be enough. For a 60-day Black Friday lead-up, you could run four (Awareness 30-60d, Vision 15-29d, Compressed 7-14d, Final-week 0-6d).

Routing rules

When multiple sequences listen on the same trigger (the same form_slug, subscriber_added event, etc.) with date-bounded windows:

1. ILLIXIS finds all sequences whose window contains the subscriber's distance to the event.
2. If exactly one matches, the subscriber enrolls in that one.
3. If two or more match (overlapping windows), the tighter window wins. A 7-13 window (6 days wide) beats a 0-21 window (21 days wide).
4. Final tiebreaker on equal width: the sequence with the lowest internal id wins.
5. If zero match, the subscriber doesn't enroll. They'll still get any broadcast you send manually around launch day.

The tighter-window rule means you can add a Short variant later without re-routing existing Compressed subscribers. The Compressed window (6 days wide) still beats the Full window (7 days wide) where they overlap.

Date-agnostic sequences. If a sequence has no event date set, it matches every signup but loses every tiebreaker against a bounded variant. This is the backward-compat path: your existing single-sequence setups keep working, and you can layer date-bounded variants alongside them without disturbing anything.

Pair with Ends at

Always set Ends at = event date on every variant. This halts in-flight enrollments at the event boundary regardless of which variant they're on. Without it, a subscriber who joined the Compressed variant on Day 0 keeps receiving emails past launch.

Ends at is the launch-day safety net. It works for date-bounded variants and date-agnostic sequences alike.

Common mistakes

Naming variants the same as the parent. Sequence names are how ILLIXIS identifies them in the database. If you have two sequences both called "Black Friday Nurture", operations like re-seeding can target the wrong one. Use suffixes: "Black Friday Nurture", "Black Friday Nurture (Compressed)", "Black Friday Nurture (Short)".

Day-of-week phrasing in email body copy. A Day-3 email after a Tuesday signup lands on Friday. The same Day-3 email after a Saturday signup lands on Tuesday. Avoid "Launch mechanics arrive Friday" in copy that ships across the week. Use cadence-relative phrasing ("Launch mechanics in a few days") or absolute dates ("Monday, June 1 at 10am ET").

Calling out the cohort in email body copy. The subscriber doesn't know they're in the Compressed variant. Phrases like "since you joined our late cohort" or "you cut it close on signup" leak our routing logic into copy the reader has no context for. Different variants should differ in pacing and length, not in self-aware acknowledgment of which bucket the reader is in.

Forgetting the Ends at safety net. Without it, late signups in the Short variant could receive their welcome email after the event has already happened. Set Ends at = event date on every variant in the family.

Related help guides

• Visual Sequence Builder (Guide 16): building the underlying sequence structure
• Sequence Triggers (Guide 67): all 13 trigger types and when to use each
• Email Automation Triggers (Guide 111): trigger event reference
• Trial Email Sequences (Guide 125): example of a date-agnostic nurture pattern
• Email Playbooks (Guide 155): pre-built sequence templates for common scenarios