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 visual workflow builder triggers on events, objects, relationships, dates, forms and segment joins, with filter conditions retried for up to thirty minutes and a wait setting that holds a person up to twenty-four hours; the journeys view shows each person's deliveries, conversions and entry and exit, and journeys can be ended manually. The vendor also documents holding out a percentage of a segment to compare activation rates, but rate limiting is documented only within a single automation, and we found no public information on frequency capping or priority across journeys, or on safe editing of a live journey. 3 4 6 4