Configure event-triggered journey entry and real-time action routing

Event-triggered journeys fire the moment a qualifying behavioral signal arrives — a purchase, an abandoned cart, a service cancellation — and immediately route the profile through a pre-defined action sequence. Configuring this capability requires defining the entry event (its schema, the fields that carry contextual data, and the mechanism for matching an inbound event to the correct journey), assembling the journey canvas with conditional branches and communication actions, and crafting message content that draws on both standing profile attributes and the live event payload.

Key decisions include selecting the correct eventID strategy (system-generated versus externally defined), choosing which XDM fields from the triggering event to expose in downstream message personalization, managing journey re-entry rules so returning profiles are handled predictably, and coordinating the Data Collection client-side configuration so events actually arrive in the edge network. Batch journeys follow a parallel pattern: instead of an event node they use a Read Segment entry, which enables scheduled, audience-scoped sends without requiring a live trigger.

Parallel viability: The real-time event-entry and sub-second action-routing pattern is deeply integrated with AEP Edge Network and AJO's internal orchestration engine, making it functionally AEP-locked for latencies under a few seconds. Composable stacks can approximate the batch variant (Read Segment) using tools such as Hightouch Journeys or Braze Canvas with a CDP audience sync, but the unitary-event path — where the journey fires within the same Edge call that ingested the event — has no direct equivalent outside AEP without significant custom engineering.