Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, goals — and what happens when a contact qualifies for several journeys at once.
0 — No automation; the product sends one-off campaigns only.
3 — Autoresponders or linear sequences started by a trigger such as a sign-up or a tag, with waits between steps.
5 — A visual workflow builder with triggers on behaviour and attributes, if/else branching and waits, and goals or exit conditions that take a contact out of the flow.
8 — Event-driven entry from external systems through an API, frequency capping and suppression across journeys, priority when a contact qualifies for several, per-contact journey state and reporting per step, versioning or safe editing of a live journey, and testing against real records.
10 — Orchestration is coherent across the whole programme: one decision layer deciding what a person receives next regardless of which journey wants to send it, holdout groups for measurement, and journeys documented and readable months later.
The Lifecycle Marketer
A visual journey builder with behavioural triggers, condition and percentage splits, waits, score-based entry and exit, and journey ejection is well documented, and version control with rollback plus journeys triggered from new Salesforce records and activities pushes it past the basics. What decides the score for me is what the pages omit: we found no public information on frequency capping, priority when a contact qualifies for several journeys, or holdout groups. 3 6 11 12