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 Solution Architect
Canvas Flow gives decision splits, action and audience paths, exit criteria the moment someone converts, versioning with post-launch edits, and testing at journey, step and message level; global control groups cover holdout measurement, and priority rules set once and applied across every campaign and journey are the cross-journey arbitration a live programme needs. We found no public information on per-contact journey state or per-step reporting, so it sits just short of the top. 2 3 4