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 Data Protection Officer
A drag-and-drop journey builder is documented with event triggers, filters, send and finish-path modules, per-automation entry caps (once, once per day, no-more-often-than per person), time windows, and draft-before-live saving, and journeys can be entered from external systems through the HubSpot connection via Zapier. We found no public information on arbitration when one contact qualifies for several journeys, suppression across journeys, per-step reporting, or holdout groups, so the documented level sits between a plain visual builder and a fully arbitrated programme. 3 4 9 11