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
The campaign designer pages show condition-driven journeys with behaviour triggers on clicks and page visits, waits between steps (a two-day wait is the documented example), split nodes with automated A/B testing, and scoring results used as trigger conditions that can hand a lead to the CRM or start a further campaign. I found no public information on frequency capping or suppression across journeys, on what happens when a contact qualifies for several at once, or on holdout groups and versioning — the parts that make a programme measurable rather than merely automated. 6 7 8 2