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 Skeptic
Canvas Flow with Action Paths, Audience Paths and Decision Split, exit criteria that pull a contact out the moment they convert, post-launch edits with version history, and testing at the journey, step and message level covers my checklist for a mature builder. Frequency capping on or across channels and message priority rules applied to every campaign and Canvas mean a contact qualifying for several journeys is handled rather than left to chance. I found no public information stating per-contact journey state or reporting per step, which holds this just below the top band. 2 3 4