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
Triggers fire on events, segment joins and object-relationship changes, with filter conditions and retry windows, waits up to 24 hours, and a per-person Journeys tab showing every delivery, conversion, entry and exit — that per-person view is the attribution backbone I want. What holds it mid-scale: we found no public information on if/else branching, cross-journey frequency capping, priority when someone qualifies for several journeys at once, or safe editing of a live journey. 3 4 5 4