Study guide
1.3 Unitary Journeys vs Business Journeys
Adobe Certified Professional - Adobe Journey Optimizer Business Practitioner AD0-E607
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Structure & Journey Fundamentals
1.1 AD0-E607 Exam Logistics, Scope, and Adobe Journey Optimizer Architecture 1.2 Journey Lifecycle States and Canvas Management 1.3 Unitary Journeys vs Business Journeys
2 Chapter 2: Journey Triggers & Event Modeling
2.1 Audience-Based Entry with Read Audience & Audience Qualification 2.2 Unitary Event Triggers & Schema Requirements 2.3 Business Events & Audience Broadcast Execution
3 Chapter 3: Journey Orchestration, Timing & Logic
3.1 Condition Activities and Branching Logic 3.2 Wait Activities and Timing Modulation 3.3 Action Nodes and the Jump Activity
4 Chapter 4: Journey Testing, Execution & Operational Reporting
4.1 Validation, Simulation, Test Mode, and Dry Run Execution 4.2 Live & All-Time Reporting Dashboards 4.3 Error Handling, Discards, and Operational Governance
5 Chapter 5: Multi-Channel Content Design & Personalization
5.1 The Email Designer & Multi-Channel Canvas Structure 5.2 Personalization Syntax & Expression Editor 5.3 In-App Messaging & Web In-Browser Delivery
6 Chapter 6: Reusable Assets, Fragments & Content Experiments
6.1 Visual Fragments vs Expression Fragments 6.2 Assets Essentials Management and Content Templates 6.3 Content Experimentation and Pre-Deployment Proofing
7 Chapter 7: XDM Schemas, Ingestion & Real-Time Customer Profiles
7.1 Experience Data Model (XDM) Foundations for Journey Optimizer 7.2 Datasets, Profile Enablement & Ingestion Troubleshooting 7.3 Real-Time Customer Profile & Profile Merge Policies
8 Chapter 8: Identity Resolution, Segmentation & Data Governance
8.1 Identity Service, Namespaces & Identity Graphs 8.2 Segmentation Methods: Streaming, Batch, Edge & Sequential Logic 8.3 Data Usage Labeling & Enforcement (DULE), Consent, and Privacy
9 Chapter 9: Decision Management, Offer Rules & Ranking Policies
9.1 Decision Management Architecture & Offer Library Components 9.2 Offer Eligibility Rules, Constraints & Capping 9.3 Decision Policies, Ranking & Channel Integration
1.3 Unitary Journeys vs Business Journeys
Key Takeaways Explain This Topic AI
A unitary event represents an occurrence tied to one person; a business event represents a non-person business occurrence.
A business event uses an XDM ExperienceEvent-based time-series schema whose primary identity is not a people identity.
Business Event must be the first activity and is followed automatically by Read Audience; the audience is selected during authoring.
A business journey does not dynamically join a business key to profiles, and audience export can take roughly 15 minutes to one hour.
Unitary Event, Audience Qualification, and Business Event entry patterns cannot be mixed arbitrarily in one journey.
Last updated: October 2026
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:
Business Event is the first activity.
Journey Optimizer automatically places Read Audience after it.
The author selects the audience to read.
When the event arrives, Read Audience exports that audience and admits its members.
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
- Question Unitary Event Business Event
- Signal One person's occurrence Non-person business occurrence
- Identity Person identity for individual execution Non-people primary identity for the signal
- Canvas Entry event under unitary rules Must be first
- Next activity Other valid journey activities Automatically inserted Read Audience only
- Who enters? Person identified by the event Members of a preselected audience
- Timing Event-driven individual entry Event plus audience export
- Dynamic key-to-profile join? Not the pattern No
- 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 .
Warning
“One-to-many” describes the business outcome, not an automatic schema relationship lookup. The configured audience, Read Audience delay, and non-person event schema are the decisive facts.
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.