Mapping Sendwave Flows to Journey Types
Meridian Journey has four entry types. Each Sendwave flow type maps to exactly one of them. Get the mapping right and the journey behaves like the flow it replaced. Get it wrong and journeys fire too often, not often enough, or at the wrong time.
Meridian Journey (target)
Behavioral Triggers
Real-time response to something the customer just did. One person, one trigger, one journey.
Welcome SeriesFires on profile creation
→
Unitary Event JourneyTrigger: profile.created
Abandoned CartFires on cart abandon
→
Unitary Event JourneyTrigger: cart.abandon
Browse AbandonFires on session end without purchase
→
Unitary Event JourneyTrigger: session.ended
Post-PurchaseFires on order confirmation
→
Unitary Event JourneyTrigger: order.confirmed
Pattern: behavior → unitary
Anything triggered by an individual customer's action becomes a Unitary Event Journey in Meridian Journey. One person at a time, fires in real time, follows them down the canvas.
Scheduled Campaigns
Batch sends to a defined audience on a clock. Entire segment enters together.
Promotional CampaignWeekly newsletter
→
Read Audience JourneyScheduled on a recurrence
Flash Sale BlastOne-time promo to a list
→
Read Audience JourneyOne-shot scheduled send
Seasonal CampaignHoliday / event blast
→
Read Audience JourneyDate-anchored read
Pattern: schedule → read audience
Anything that reads a segment on a schedule and ships to everyone at once becomes a Read Audience Journey. Same behavior as Sendwave campaigns, native to Meridian Journey.
Segment-Change Triggers
Profile crosses a segment boundary in real time — and that change itself is the trigger.
Win-BackTriggered when "lapsed 90 days" reached
→
Audience Qualification JourneyFires on segment entry: lapsed90
VIP Tier ChangeTriggered when loyalty tier upgrades
→
Audience Qualification JourneyFires on segment entry: vip_platinum
ReactivationTriggered when re-engagement window
→
Audience Qualification JourneyFires on segment entry: reactivated
Pattern: state change → qualification
If the moment that matters is "they just became X," it's a Qualification Journey. Fires the instant a profile enters or exits the segment — no polling, no batch lag.
External Triggers
Something outside the marketing system fires the journey. CRM event, in-store purchase posted, support ticket resolved.
Webhook-Triggered FlowExternal system posts an event
→
API-Triggered JourneyExternal call kicks off journey
Use sparingly
API-triggered journeys are powerful but expensive to maintain — they couple a marketing journey to an external system contract. Use them only when no segment or event signal exists in MDP.
Map every flow before you build anything
Wrong entry type = journey behaves nothing like the Sendwave flow it replaced. Document the mapping for every Sendwave flow before you start rebuilding. The audit-classify-map step is what makes Phase 4 (Rebuild) go fast.