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 drag-and-drop editor builds multi-step journeys with behaviour and tag triggers, configurable waits, the linking of several automations, and more than twenty prebuilt journeys including welcome, cart-abandonment and reactivation flows — real retention work, not just welcome mail — and the trigger mechanics are documented honestly down to a tag firing only when newly set. But I found no public information on if/else branching, goals or exit conditions, or on what happens when one contact qualifies for several journeys at once — nothing on frequency capping, priority or holdout groups — so this stops short of programme-level orchestration. 1 4 5 11