Lifecycle journey vs real-time event campaign: when to use each
When to build a multi-step lifecycle journey versus an instant event-triggered relay — decision table, Iran ecommerce examples, anti-double-messaging.
Sara Moradi
Designs customer journeys and marketing automation campaigns for retention and lower churn.
September 11, 2026 · 7 min read
- lifecycle journey
- real-time campaign
- event-triggered
- marketing automation
- onboarding
- back in stock
- SMS
Also available in فارسی
Direct answer
A lifecycle journey is a multi-step path with a longer time horizon: enter a state (signup, first purchase, silence), several spaced touches, branches, and an exit when the goal is met. Think WebEngage-style journeys that move people across lifecycle stages over days and weeks.
A real-time event campaign (relay) is a fast reaction to one sharp event: back in stock, price drop, code about to expire, cart just abandoned — usually one or two touches inside a short window, not a long lifecycle map.
One practical line: journey = horizon and state; real-time event = urgency and trigger. “What do we say to this list today?” is a blast campaign (see: Journey vs campaign). This article answers a different question: multi-step lifecycle path versus an instant relay on one event.
What is a lifecycle journey vs a real-time event campaign?
| Lifecycle journey | Real-time event campaign / relay | |
|---|---|---|
| Primary trigger | State-segment entry or lifecycle point (new, active, at risk) | Sharp event with a short TTL (back_in_stock, price_drop, …) |
| Time horizon | Days to months; several waits | Minutes to a few hours; often same day |
| Message job | Educate, habit, activate, retain | Urgent notice, scarce opportunity, short recovery |
| Branching | Rich (behavior, channel, value) | Light; usually one dominant path |
| Critical exits | Lifecycle goal completion + frequency caps | Opportunity consumed / window expired + conversion |
| Failure mode | Too slow for a perishable opportunity | Instant spam with no horizon |
Working definition: lifecycle journey
A path that moves someone from one state to the next — e.g. “signed up, no purchase” → “active buyer” — with email/SMS touches, waits, branches, and a hard exit when the goal event fires. Its horizon is longer than a single cart nudge; the WebEngage-like idea is a journey on lifecycle stage, not one shot.
Working definition: real-time event campaign
A relay on an event: when the signal arrives and conditions hold, message inside a short window. Examples: SKU back in stock, price drop, code near expiry, delivery slot opened. In product UI it may look like a “triggered campaign” or a short wait-for-event; the essence is short horizon, not a lifecycle map.
Decision table: when journey, when relay?
| Question | If the answer is… | Choose |
|---|---|---|
| Does this person need several touches over time? | Yes — education / habit | Lifecycle journey |
| Does message value die with delay? | Yes (stock, price, slot) | Real-time event |
| Is one conversion exit enough? | Long path with mid goals | Journey |
| Do you only have one short opportunity? | One TTL-bound event | Relay |
| Are behavioral events still unstable? | Calendar list only | Clean campaign first; wire events in parallel |
Simple rule: stable state → journey; perishable opportunity → real-time event.
Iran ecommerce examples: onboarding vs back-in-stock
Fashion-store onboarding (lifecycle journey)
Someone signed up with no order_completed yet. Right path: welcome, size/shipping help, favorite-category nudge, soft reminder — 12–48h gaps and a hard purchase exit. That is a multi-day horizon; crushing it into one urgent SMS is spam, not onboarding.
Keep welcome-series craft separate; here we only care about horizon. If you also run cart recovery, do not blur tone/triggers with abandoned browse vs abandoned cart.
Home-appliance back-in-stock (real-time event)
An SKU was out for weeks; back_in_stock fires. Message value peaks in the first hours. Do not park this inside a seven-day “meet the brand” journey — send one email/SMS with a PDP link, consume the opportunity once, and suppress people who already bought that SKU.
Combining both without double-messaging
Sample priority table for an Iranian store:
| Priority | Path | When active | What it suppresses |
|---|---|---|---|
| 1 | Real-time event (stock/price) | TTL window open | Soft onboarding touches that same day |
| 2 | Cart recovery | Open cart, no purchase | Soft browse; blast promo |
| 3 | Onboarding / lifecycle journey | State goal not completed | — |
| 4 | Calendar promo | Manual campaign | Anyone inside 1–3 |
One person must not get “It’s back!” and “Welcome to the family” with two conflicting discounts the same day. Shared frequency caps + segment suppressions — not luck.
Time horizon and relays
In products like WebEngage, journeys often sit on relay / wait / wait-for-event blocks. Practical operator split:
- Fixed wait in a lifecycle journey: 24h after signup → email 2. Planned horizon.
- Short wait-for-event: wait up to 6h for
purchase; else SMS. Still recovery, not a month-long map. - Real-time event relay: enter on
back_in_stock; no four-week blueprint.
Common mistake: dump everything into one giant lifecycle journey and treat stock as “step 5.” Result: delay on perishable opportunities + conflicting copy.
Channels: where email and SMS sit
- Lifecycle journeys: email for depth (guides, story, multiple CTAs); SMS sparingly for activation or key reminders with separate consent.
- Real-time events: SMS when minutes matter and consent exists; email when product image and link beat the second.
- We do not re-litigate cart channel choice here — see: Abandoned cart email vs SMS.
Mapping to Leadara (events, segments, journeys, email/SMS)
- Name state vs opportunity events separately: e.g.
signed_up,first_order_completedvsback_in_stock,price_drop. - Lifecycle segment: “signed up, no purchase in 7 days” for onboarding journeys.
- Real-time segment/trigger: watchers or last
view_itemon that SKU + freshback_in_stock. - Two separate paths with a priority table and same-day mutual suppress.
- Exits: hard
order_completed(and for relays, “opportunity consumed” or TTL expiry). - Email/SMS only carry the message; horizon and urgency decisions live in segments/journeys.
Leadara gives you events, segments, journeys, email/SMS. A magical “horizon AI” does not replace a clean event catalog and a priority table.
Common mistakes
- Onboarding as one urgent SMS with no purchase exit
- Parking
back_in_stockas a late step inside a four-week journey - One template for lifecycle and stock relays
- Parallel paths with no suppress (welcome + back-in-stock + Friday)
- Forgetting TTL on real-time opportunities
- Measuring only opens instead of activation (lifecycle) and click-to-purchase in the short window (real-time)
Related reading
- Journey vs campaign in marketing automation — timed blast versus behavioral path
- Abandoned cart email vs SMS
- Abandoned browse vs abandoned cart
FAQ
What is the difference between a lifecycle journey and a real-time event campaign?
A journey works on state and a longer horizon; a real-time event works on one perishable signal inside a short window. Both can be behavioral — the split is horizon and message job, not “automated or not.”
Is this the same as journey vs blast campaign?
No. A blast is usually a timed send to a list. This article compares a multi-step lifecycle path to an instant event relay. For blast vs journey: Journey vs campaign.
Should onboarding be a journey or a real-time event?
Classic onboarding = lifecycle journey. Only if a perishable opportunity appears mid-onboarding (e.g. the viewed SKU returns), run a higher-priority real-time relay and suppress soft touches that day.
Should back-in-stock live inside the welcome journey?
Usually not as a late step. Build a separate short-TTL trigger and suppress soft welcome touches on event day so tones and discounts do not collide.
How do we prevent double-messaging?
Path-priority table, shared 24h frequency cap, mutual suppress, and exits on purchase/opportunity consumed. One vague “all actives” segment for both paths guarantees repeats.
Is abandoned cart a journey or a real-time event?
Usually a short recovery journey (a few touches, purchase exit) — shorter horizon than onboarding, sometimes longer than back_in_stock. Measure channel separately: Abandoned cart email vs SMS.
Which events do we need in Leadara?
At least state events (signed_up / equivalent, order_completed) and opportunity events if you use them (back_in_stock, price_drop, add_to_cart). Keep names stable in the catalog.
Which should we launch first?
If you have signup and purchase: a small onboarding journey with a purchase exit. Add a stock relay once stock signals and message identity are stable — with a priority table from day one.
Bottom line and next step
Lifecycle journeys serve state and habit; real-time event campaigns serve perishable opportunity. This week: separate state vs opportunity events, ship a purchase-exiting onboarding journey, define a short-TTL stock relay, lock same-day priority and suppress rules, and pick channels after you pick horizon — not the other way around.
