Journeys & orchestration
ActiveCampaign (Automation)
The builder shows branching on behaviour, goal tracking with channel-switch fallbacks, and event-driven entry from site tracking and 900-plus apps, which is genuine orchestration. What decides whether a programme survives contact with reality is missing from the captured pages: I found no public information on frequency capping across journeys, suppression or priority when a contact qualifies for several, versioning of a live journey, holdout groups for measurement, or a per-contact view of where someone currently sits.
HubSpot Marketing Hub
The tier table evidences genuine multi-step automation — up to 300/1,000 workflows driven by behavioural events, unlimited actions from Professional — but the evidence is silent on everything that makes journeys survive contact with each other: no frequency capping, no cross-journey suppression, no priority when a contact qualifies for several, no versioning, no holdout groups. Branching, waits and per-contact journey state aren't evidenced either, so this lands between the linear and visual-builder anchors.