Trigger types
- Event trigger — a contact enters when a tracked event occurs (e.g.
purchase_made,form_submitted). - Schedule trigger — the journey runs on a recurring schedule against a segment.
Step types
| Step | Purpose |
|---|---|
send | Deliver a message on any channel |
delay | Wait a fixed period before the next step |
gate | Conditional split based on contact attributes or behaviour |
experiment | A/B test — randomly assign branches |
balancer | Distribute traffic across N branches by weight |
update | Modify a contact attribute |
event | Emit an internal event for tracking |
exit | Remove the contact from the journey |
link | Jump to another step (useful for loops) |
wait-for-event | Pause until a specific event occurs (or a timeout fires) |
Build a journey
Add a send step
Pick a channel and template. The template can pull contact attributes and event data via merge tags.
Add branching where needed
Use
gate to send different content to different cohorts; use experiment to test variants.Reference
The journey object contract is documented in the API:- Create / update / list / activate — see Main API → Journeys
Next
Smart segments
Audiences journeys can target.
AI content generation
Generate copy for any send step. Coming soon — check back.