Adobe Journey Optimizer helps you deliver connected, contextual, and personalized experiences. It helps expose your customers to the next step in their customer journey.
You can import data generated by Journey Optimizer to perform advanced analysis in Customer Journey Analytics by performing the following steps:
Adobe Experience Platform serves as the central data source and link between Journey Optimizer and Customer Journey Analytics. See Get started with Datasets in the Journey Optimizer user guide for steps on how to send Journey Optimizer data to Platform as a Dataset.
Once Journey Optimizer data is in Adobe Experience Platform, you can Create a connection based on your Journey Optimizer Dataset. Select the Dataset that you sent to Platform.
After a connection is created, you can create one or more Data Views to configure the desired dimensions and metrics available in Customer Journey Analytics.
You can create the following metrics in a data view to achieve approximate parity with similar metrics in Journey Optimizer. See Component settings in the Data View Manager for details around how to customize dimensions and metrics.
Metric | Description | Data View settings |
---|---|---|
Bounces | The number of messages that bounced | Use the schema string element _experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus with the following settings:Component type: Metric Include exclude values: If any criteria are met Equals: bounce Equals: denylist |
Errors | The number of messages that errored out | Use the schema string element _experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus with the following settings:Component type: Metric Include exclude values: Equals error |
Excludes | The number of messages excluded | Use the schema string element _experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus with the following settings:Component type: Metric Include exclude values: Equals exclude |
Unsubscribes | The count of unsubscribes | Use the schema string element _experience.customerJourneyManagement.messageInteraction.interactionType with the following settings:Component type: Metric Include exclude values: Equals unsubscribe |
Clicks | The count of clicks within messages | Use the schema string element _experience.customerJourneyManagement.messageInteraction.interactionType with the following settings:Component type: Metric Include exclude values: Equals click |
Opens | The number of opened messages | Use the schema string element _experience.customerJourneyManagement.messageInteraction.interactionType with the following settings:Component type: Metric Include exclude values: Equals open |
Spam complaints | The count of spam complaints | Use the schema string element _experience.customerJourneyManagement.messageInteraction.interactionType with the following settings:Component type: Metric Include exclude values: Equals spam_complaint |
Messages successfully sent | The number of messages successfully sent | Use the schema string element _experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus with the following settings:Component type: Metric Include exclude values: Equals sent |
Sync failures | The total number of messages that failed to sync | Use the schema string element _experience.customerJourneyManagement.messageDeliveryfeedback.messageFailure.category with the following settings:Component type: Metric Include exclude values: Equals sync |
Once you have configured the desired dimensions and metrics for the Journey Optimizer dataset, you can also configure Calculated metrics for additional insights around that data. These calculated metrics are based on the above metrics created in the Data View Manager.
Calculated metric | Description | Formula |
---|---|---|
Total messages sent | The total number of messages sent, successful or failed | [Messages successfully sent] + [Bounces] + [Sync failures] |
Data discrepancies between products is typically between 1-2%. Larger discrepancies between products can potentially be attributed to the following: