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 Demand Gen Lead
The journey builder is real: a drag-and-drop editor with triggers, conditions and actions, an automations builder with event triggers, filters, send-campaign and finish-path modules, and settings that cap re-entry six ways ("no more often than", max once per day) with hour and date windows plus draft-before-activate control. External events can start journeys — the HubSpot path creates an event that triggers automation, and API docs are public — but we found no public information on cross-journey suppression, priority when a contact qualifies for several journeys, or per-step reporting, so I cannot yet tell my reps which journey sent yesterday's email. 3 4 9 11