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
Automations trigger on events, segment joins, objects, relationships, dates and forms, with filter conditions retried for up to 30 minutes, waits up to 24 hours, rate limiting, manual early exit, and a per-person Journeys tab recording deliveries, conversions and entry and exit — real per-contact journey state, fed by real-time product data through the API — and holding back a percentage of a segment for comparison is described. We found no public information on priority when a person qualifies for several automations at once, or on versioning and safe editing of a live journey. 3 4 6 4