- Journey Optimizer documentation
- What’s new?
- Get started
- Journeys
- Campaigns
- Conflict management & prioritization
- Test & approve
- Communication channels
- Get started with communication channels
- Email channel
- In-app channel
- Push notification channel
- SMS / MMS channel
- Direct mail
- Web channel
- Code-based experience
- Content cards
- Landing pages
- Content management
- AI Assistant for content generation
- Work with Multilingual content
- Work with Content experiment
- Personalization
- Content templates
- Reusable content fragments
- Dynamic content
- Audiences, profiles & identity
- Integrations
- Track & monitor
- Live report
- All time report
- Journey reports
- Deliverability
- Alerts
- Exclusion reasons
- Decision capabilities
- Get started with decision capabilities
- Decisioning
- Get started with Decisioning
- Decisioning guardrails & limitations
- API reference
- Manage decision items
- Configure item selection
- Create selection strategies
- Create decision policies
- Report on Decisioning
- Decisioning use case
- Decision management
- Get started with Decision management
- Create components
- Create rankings
- Create & manage offers
- Create & manage decisions
- Use batch decisioning
- Collect event data
- Leverage context data
- Create Decision Management reports
- Export your offer catalog
- API Reference
- Getting started
- Create & manage offers using APIs
- Deliver offers using APIs
- Data management
- Channel configuration
- Journey configuration
- Connect your systems and environments
- Access control
- Privacy
Create journey reports
In addition to real-time reports and built-in reporting capabilities, Journey Optimizer can automatically send journey performance data to Adobe Experience Platform so it can be combined with other data for analysis purposes.
This feature is activated by default on all instances for journey steps events. You cannot modify or update the schemas and datasets that have been created during provisioning for step events. By default, these schemas and datasets are in read-only mode.
For example, you have set up a journey that sends multiple emails. This capability allows you to combine Journey Optimizer data with downstream event data like how many conversions occurred, how much engagement happened on the website, or how many transactions happened in the store. The journey information can be combined with data on Adobe Experience Platform, either from other digital properties or from offline properties to give a more comprehensive view of performance.
Journey Optimizer automatically creates the necessary schemas and streams into datasets to Adobe Experience Platform for each step an individual takes in a journey. A step event corresponds to an individual moving from one node to another in a journey. For example, in a journey that has an event, a condition and an action, three step events are sent to Adobe Experience Platform.
There are cases where multiple events can be created for the same node. For example, in the case of the Wait activity:
- One event is generated when the profile enters the wait (journeyNodeProcessed attribute is equal to false)
- One event is generated when the profile exits it (journeyNodeProcessed attribute is equal to true)
The list of XDM fields that are passed is comprehensive. Some contain system generated codes and others have human readable friendly names. Examples include the label of the journey activity or the step status: how many times an action timed out or ended in error.
Datasets cannot be turned on for real time profile service. Please make sure that the Profile toggle is turned off.
Journey Optimizer sends data as it occurs, in a streaming way. You can query this data using the Query Service. You can connect to Customer Journey Analytics or other BI tools to view data related to these steps.
The following schemas are created:
- Journey Step Event schema for Journey Orchestration – Journey step event that is tied to a Journey Metadata.
- Journey schema with Journey Fields for Journey Orchestration – Journey Metadata to describe Journeys.
The following datasets are passed:
- Journey Step Events
- Journeys
The lists of XDM fields passed to Adobe Experience Platform are detailed here:
Integration with Customer Journey Analytics
Journey Optimizer step events can be linked to other datasets in Adobe Customer Journey Analytics.
The general workflow is:
- Customer Journey Analytics ingests the “Journey Step Event” dataset.
- The profileID field in the associated “Journey Step Event schema for Journey Orchestration” is defined as an Identity field. In Customer Journey Analytics, you can then link this dataset to any other dataset that has the same value as the person based identifier.
- To use this dataset in Customer Journey Analytics, for cross-channel journey analysis, refer to Customer Journey Analytics documentation.
