Journeys & orchestration
How this is scored
Multi-step automation: triggers, branching, waits, and — the part that decides whether it survives contact with reality — what happens when journeys collide.
0 — Autoresponders on a single trigger; no branching, no waits, no conditions.
3 — Linear sequences with simple conditions, one entry trigger per journey, and no visibility into where a contact currently sits.
5 — A visual builder with branching on attributes and behaviour, waits and goals, entry and exit conditions, and per-contact journey state visible.
8 — Event-driven entry from external systems, frequency capping and suppression across journeys, priority when a contact qualifies for several, versioning 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 a journey a colleague can read months later without a diagram.
The Data Protection Officer
Architect is evidenced as a zero-code drag-and-drop builder for multi-branch journeys, with A/B testing of entire flows, journey analytics, and frequency caps, fed by a profile that updates from CRM and offline systems in milliseconds and positioned as a centralized decisioning engine. We found no public information on versioning of a live journey, on priority when several journeys claim the same person, or on seeing where a specific contact currently sits — the collision behaviour and per-person visibility I would need to audit what was decided about someone. 3 4 6 8