1.3 Unitary Journeys vs Business Journeys

1.3 Unitary Journeys vs Business Journeys

Journey Optimizer distinguishes a signal about one person from a signal about the business. Both can start journeys, but their schemas, entry patterns, and timing differ. The business-event pattern is often misunderstood: it does not use an event key to discover a cohort dynamically.

Unitary events: one occurrence, one person

A unitary event represents an occurrence associated with an individual, such as checkout, mobile login, support escalation, or a cart event. It creates an individual journey execution for the identified person. The event can supply contextual fields to downstream conditions and personalization when those fields were selected in event configuration.

Journey Optimizer supports system-generated and rule-based event configurations. Configuration points to an XDM schema and identifies the relevant event and identity information. When later activities need profile attributes, the identity and namespace must resolve to a profile Journey Optimizer can retrieve.

Use a unitary event when:

• the signal concerns one individual;
• the payload provides the identity needed for execution;
• each occurrence should be handled independently;
• immediate event context is useful on the path.

A streaming audience transition is different. If the requirement is “enter when a person qualifies for an audience,” use Audience Qualification rather than manufacturing a unitary event.

Business events: one occurrence, a preselected audience

A business event represents a non-person occurrence: a flight disruption, store closure, regional alert, inventory event, or service incident. Its schema is time-series and based on XDM ExperienceEvent, but its primary identity is a non-people namespace appropriate to the signal. During event configuration, select the payload fields, including the event identifier and timestamp.

The canvas has a strict structure:

1. Business Event is the first activity.
2. Journey Optimizer automatically places Read Audience after it.
3. The author selects the audience to read.
4. When the event arrives, Read Audience exports that audience and admits its members.
5. Downstream paths operate per person and can use available business-event context and profile data.

Read Audience is the only activity allowed directly after Business Event. A business journey cannot combine that entry with a unitary event or Audience Qualification.

What business events do not do

An incorrect design assumption is: “Receive flight 882, join flightId to every profile booking, and instantly discover the passengers.” That dynamic relationship join is not the Journey Optimizer Business Event entry model. The target audience is configured before execution. If a business key determines membership, upstream data and segmentation must prepare an appropriate audience, and the practitioner selects it in Read Audience.

This changes timing. A business event can react to an operational occurrence, but audience export is not immediate. Adobe documents an export delay of approximately 15 minutes to one hour. Do not promise a sub-second mass broadcast. For urgent use cases, validate whether this processing window and downstream channel delivery satisfy the requirement.

Multiple executions

A business journey can allow multiple executions. Review this choice when events can recur, because a later business event may initiate another audience read and the setting controls interaction with existing execution. This prevents a follow-up incident from unexpectedly duplicating communication or ending an intended path.

A unitary journey instead manages execution for each individual. Reentrance and whether a person is currently active determine whether another entry can occur.

Comparison

Scenario selection

• A loyalty member checks in on a mobile app: Unitary Event.
• A person becomes high value under streaming audience rules: Audience Qualification.
• A nightly audience should run at 8 a.m.: Read Audience.
• A regional outage should notify a prepared outage audience: Business Event followed by Read Audience.

Comparison drill

When practicing, rewrite one business scenario three ways: an identified person acts, a person's audience membership changes, and a non-person incident occurs. Then assign Unitary Event, Audience Qualification, or Business Event followed by Read Audience. The exercise forces attention to signal identity, who is selected, and processing time instead of relying on the scenario's industry vocabulary.