Configure Journey Entry Events and Guardrail Rules

Journey entry event configuration defines the precise trigger signal that starts a customer's traversal of a journey — which event type, which XDM schema, which payload fields are available to subsequent steps, and how the platform identifies the customer being admitted. Guardrail rules layer on top to control the safety envelope: how often a profile can re-enter the same journey, what timeout closes an open journey instance, and any global messaging frequency caps that prevent inadvertent over-communication.

The entry event schema must include the Orchestration eventID field group (_experience.campaign.orchestration.eventID); schemas lacking this field group do not appear in AJO's event picker. The system-generated eventID must be extracted from the event's sample payload and embedded in the upstream application (e.g., a Data Collection / Tags data element) so that the correct journey is triggered when the event fires. Payload field selection at configuration time determines which event-context values are accessible downstream without additional data-source lookups.

Guardrail decisions are equally consequential: allowing re-entry enables the journey to re-execute for the same profile on each qualifying event (appropriate for transactional flows); blocking re-entry prevents duplicate journey instances (appropriate for lifecycle flows with a defined end state). Journey timeout ensures that profiles that enter but never reach an end node are eventually closed out, preventing resource accumulation.

Parallel viability note (AEP-locked module): The specific pattern of schema-registered entry events with system-generated orchestration IDs is native to the AJO/AEP platform. In composable stacks, the nearest equivalent is a streaming event consumer (Kafka, Kinesis, Pub/Sub) paired with a workflow orchestrator (Temporal, Airflow, AWS Step Functions) that evaluates entry conditions against a feature store. Guardrail equivalents — re-entry control, capping — must be implemented as custom state logic, often in a Redis or database-backed counter store. This represents significant custom engineering compared to the declarative configuration AJO provides.