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
Journeys branch on real-time behaviour and cross-channel interactions, exit people the instant they convert, and message priority rules set once apply across every campaign and Canvas — a programme-level arbitration layer rather than per-flow tuning, which is exactly what I want to see. Frequency capping across channels, versioning with post-launch edits, testing at the journey, step and message level, and turnkey Global Control Groups for measuring engagement uplift cover most of what I look for. The one gap in the captured pages is per-contact journey state and step-level reporting, which is not spelled out. 2 3 4