MERIDIANIntroduction to Building a Journey8:30
The journey canvas
A journey is a visual flowchart that orchestrates messages and decisions across channels. Customers enter at the top, and the canvas decides what happens next based on their data and behavior.
⚡ Event: cart.abandoned
↓
Wait 1 hour
↓
Cart value > $200?
Yes ↓
✉ High-value reminder
No ↓
✉ Standard reminder
The five node types
Every journey is built from five kinds of nodes. Master these and you can express any orchestration pattern.
  • Entry — how profiles enter the journey. Event-triggered, audience-read, audience-qualified, or API-triggered.
  • Action — the thing you do. Send an email. Send a push. Update a profile attribute. Call an external API.
  • Wait — pause the journey. Wait a fixed duration. Wait until a specific date or time. Wait for an event to fire.
  • Condition — branch the journey based on profile data, event data, or random A/B test allocation.
  • End — the journey terminates. Explicit ends help with reporting; implicit ends happen at the bottom of any path.
Test before you ship
Every journey can be tested with a sample profile before going live. Use the Test Mode panel to walk a real or simulated profile through the canvas — see which path it takes, which actions fire, and how long it takes.

Sandbox testing

Run the journey against test profiles in your sandbox. No real sends. Validate the logic before activating in production.

Test proofs

For email content, send a test proof to internal addresses before activating. Verify rendering, links, personalization, and consent suppression.

The activation gate

Once a journey is activated, it starts processing real profiles in real time. Activate during low-traffic hours and watch the first hour of execution closely. The "running journeys" dashboard surfaces errors and unexpected drop-offs immediately.

0:00
1 / 3