DocumentationCustomer Journey AnalyticsCustomer Journey Analytics Guide

Integrate Journey Optimizer with Customer Journey Analytics

Last update: Thu Jun 27 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin

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 configure data generated by Journey Optimizer to perform advanced analysis in Customer Journey Analytics. You can configure this integration automatically. If needed, you can make additional, manual customizations to the datasets, dimensions, or metrics that are available in your connection or data views.

Automatically configure Journey Optimizer integration

AVAILABILITY
The functionality described in this section is in the Limited Testing phase of release and might not be available yet in your environment. This note will be removed when the functionality is generally available. For information about the Customer Journey Analytics release process, see Customer Journey Analytics feature releases.

Journey Optimizer supports using Customer Journey Analytics as the reporting engine. See Get started with the new Reporting interface in the Journey Optimizer documentation.

When you have enabled Customer Journey Analytics reporting for Journey Optimizer, automatically a connection and data view are created for the specific sandbox.

Connection

The connection has the name AJO Enabled Connection (sandbox name) and has the following out of the box values for configuration and datasets:

Connection settings
Value
Connection name
AJO Enabled Connection (sandbox name)
Connection description
Describe your connection here
Tags
Select tags
Data settings
Value
Enable rolling data window
Enabled. Selected number of months 13.
Sandbox
name of sandbox (disabled; you cannot modify this setting).
Average number of daily events
less than 1 million (disabled; you cannot modify this setting).
Dataset name
Schema
Dataset type
Data source type
Person Id
Key
Matching Key
Import new data
Backfill data
AJO Entity Dataset
AJO Entity Record Schema
Lookup
Other
-
_id
_experience. decisioning. propositions. scopeDetails. correlationID
Status Green On
Status Gray Off
Journey Step Events
Journey Step Event schema for Journey Orchestration
Event
Other
IdentityMap(<primary>)
-
-
Status Green On
Status Gray Off
AJO Email Tracking Experience Event Dataset
AJO Email Tracking Experience Event Schema
Event
Other
IdentityMap(<primary>)
-
-
Status Green On
Status Gray Off
AJO Email Tracking Experience Event Dataset
AJO Email Tracking Experience Event Schema
Event
Other
IdentityMap(<primary>)
-
-
Status Green On
Status Gray Off
AJO Message Feedback Event Dataset
AJO Message Feedback Event Schema
Event
Other
IdentityMap(<primary>)
-
-
Status Green On
Status Gray Off
AJO Push Tracking Experience Event Dataset
AJO Push Tracking Experience Event Schema
Event
Other
IdentityMap(<primary>)
-
-
Status Green On
Status Gray Off

Data view

The data view has the name AJO Enable Data View (sandbox name).

  • In the Configure tab, the following values are configured out of the box.

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 layout-fixed
    Settings Value
    Connection AJO Enabled Connection (sandbox name)
    Name AJO Enabled Data View (sandbox name)
    External ID AJO_Enabled_Data_View__sandbox_name_ (derived from the name)
    Description undefined
    table 0-row-2 1-row-2
    Compatibility Value
    Set as default data view in Adobe Journey Optimizer Enabled (default).

    This configuration option allows you to designate a data view to use with Journey Optimizer, without the need for manual configuration. For information how to enable this configuration option (if not already enabled by default), see the Compatibility section in Create or edit a data view.

    When you disable the option, a dialog prompts you whether you want to continue changing the default data view. When you select Continue, you need to select another data view as the default data view. Select Confirm to confirm your selection. Select Cancel to cancel changing the default data view.
    table 0-row-2 1-row-2 2-row-2 3-row-2
    Containers Value
    Person container name Person
    Session container name Session
    Event container name Event
    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Calendar Value
    Time zone Time zone conforming to your location
    Calendar type Gregorian
    First month of the year January
    First day of the week Sunday

  • In the Components tab:

    • All metrics and dimensions that have (AJO) appended to their name are added automatically as part of this automatic configuration.
    • Some of the metrics or dimensions, that have been added automatically, are based on derived fields. These derived fields are specifically created for this integration. For example, the metric Landing Page Clicks (AJO) is based on the Landing Page Clicks derived field.
    • Some of the metrics or dimensions have additional configuration. For example, Spam Complaint (AJO) does have Format and Include Exclude Values settings applied.
    • All automatically added metrics and dimensions do have a context label named :name_of_metric_or_dimension. For example, the Landing Page Clicks (AJO) metric has the context label :Landing page clicks (AJO).

  • In the Settings tab, no specific configuration values are applied

IMPORTANT
Modifying any of the automatically configured values for the connection and data view does have consequences for the Journey Optimizer reporting that is relying upon and using the automatically configured Customer Journey Analytics integration.

Manually configure a data view to be used with Journey Optimizer

The following sections describe how you can manually use data, generated by Journey Optimizer, to perform advanced analysis in Customer Journey Analytics. This is necessary only if the automatic configuration option is insufficient for your needs.

Send data from Journey Optimizer to Experience Platform

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 Experience Platform as a dataset.

Create a connection in Customer Journey Analytics

Once Journey Optimizer data is in Adobe Experience Platform, you can Create a connection based on your Journey Optimizer datasets. Or you can add Journey Optimizer datasets to an existing connection.

Select and configure the following datasets:

Dataset
Dataset type
Connection settings
Description
AJO Message Feedback Event Dataset
Event
Person ID: IdentityMap
Contains message delivery events, such as ‘Sends’ and ‘Bounces’.
AJO Email Tracking Experience Event Dataset
Event
Person ID: IdentityMap
Contains email tracking events such as ‘Opens’, ‘Clicks’, and ‘Unsubscribes’.
AJO Push Tracking Experience Event Dataset
Event
Person ID: IdentityMap
Contains push tracking events such as ‘App Launches’.
Journey Step Events
Event
Person ID: _experience.journeyOrchestration.
stepEvents.profileID
Contains events showing which profiles participated in each node of the journey.
AJO Entity Dataset
Lookup
Key: _id
Matching Key: _experience.decisioning.propositions.
scopeDetails.correlationID
Contains classifications that associate Journey and Campaign metadata to all Journey Optimizer event data.

Configure the Data view to accommodate Journey Optimizer dimensions and metrics

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.

NOTE
Data discrepancies between Journey Optimizer and Customer Journey Analytics are typically less than 1-2%. Larger discrepancies are possible for data collected within the last two hours. Use date ranges excluding today to mitigate discrepancies involving processing time.

Configure dimensions in the data view

You can create the following dimensions in a data view to achieve approximate parity with similar dimensions in Journey Optimizer. See Component settings in the Data View Manager for details on dimension customization options.

Dimension
Schema element
Component settings
Journey Name
_experience.customerJourneyManagement.
entities.journey.journeyName
Component type: Dimension
Journey Name & Version
_experience.customerJourneyManagement.
entities.journey.journeyNameAndVersion
Component type: Dimension
Journey Node Name
_experience.customerJourneyManagement.
entities.journey.journeyNodeName
Component type: Dimension
Journey Node Type
_experience.customerJourneyManagement.
entities.journey.journeyNodeType
Component type: Dimension
Campaign name
_experience.customerJourneyManagement.
entities.campaign.name
Component type: Dimension
Channel
_experience.customerJourneyManagement.
entities.channelDetails.channel._id
Component type: Dimension
Push Title
_experience.customerJourneyManagement.
entities.channelDetails.push.title
Component type: Dimension
Email Subject
_experience.customerJourneyManagement.
entities.channelDetails.email.subject
Component type: Dimension
Link Label
_experience.customerJourneyManagement.
messageInteraction.label
Component type: Dimension
Experiment Name
_experience.customerJourneyManagement.
entities.experiment.experimentName
Component type: Dimension
Context Labels: Experimentation Experiment
Treatment Name
_experience.customerJourneyManagement.
entities.experiment.treatmentName
Component type: Dimension
Context Labels: Experimentation Variant
Email Delivery Failure Reason
_experience.customerJourneyManagement.
messageDeliveryfeedback.messageFailure.reason
Component type: Dimension
Email Delivery Exclusion Reason
_experience.customerJourneyManagement.
messageDeliveryfeedback.messageExclusion.reason
Component type: Dimension
Element Label
_experience.decisioning.propositionAction.label
Component type: Dimension

Configure metrics in the data view

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 metrics customization options.

Metric
Description
Schema element
Component settings
Bounces
The number of messages that bounced, including both immediate bounces and bounces after delivery.
_experience.customerJourneyManagement.
messageDeliveryfeedback.feedbackStatus
Component type: Metric
Include exclude values: If any criteria are met
Equals: bounce, Equals: denylist
Bounces After Delivery
Some email services report emails delivered, then bounce them later.
_experience.customerJourneyManagement.
messageDeliveryfeedback.messageFailure.category
Component type: Metric
Include exclude values: Equals async
Email Clicks
The count of clicks within messages.
_experience.customerJourneyManagement.
messageInteraction.interactionType
Component type: Metric
Include exclude values: Equals click
Email Opens
The number of opened messages.
_experience.customerJourneyManagement.
messageInteraction.interactionType
Component type: Metric
Include exclude values: Equals open
Errors
The number of messages that errored out.
_experience.customerJourneyManagement.
messageDeliveryfeedback.feedbackStatus
Component type: Metric
Include exclude values: Equals error
Excludes
The number of messages excluded.
_experience.customerJourneyManagement.
messageDeliveryfeedback.feedbackStatus
Component type: Metric
Include exclude values: Equals exclude
Sends
The number of messages that email providers accepted.
_experience.customerJourneyManagement.
messageDeliveryfeedback.feedbackStatus
Component type: Metric
Include exclude values: Equals sent
Spam Complaints
The count of spam complaints.
_experience.customerJourneyManagement.
messageInteraction.interactionType
Component type: Metric
Include exclude values: Equals spam_complaint
Unsubscribes
The count of unsubscribes.
_experience.customerJourneyManagement.
messageInteraction.interactionType
Component type: Metric
Include exclude values: Equals unsubscribe
Edge Sends
The number of times the edge network sends a message to either the Web or Mobile SDK
Use the schema string element _experience.decisioning.propositionEventType.send
Inbound Displays
The number of times a Web or InApp message is shown to the user
Use the schema string element _experience.decisioning.propositionEventType.display
Inbound Clicks
The count of Web or InApp message clicks
Use the schema string element _experience.decisioning.propositionEventType.interact
InApp Triggers
The number of times the decisioning engine suggested the message should be displayed. The Mobile SDK could override the decision, reducing the number of actual displays.
Use the schema string element _experience.decisioning.propositionEventType.trigger
InApp Dismissals
The number of times an InApp message is removed from the UI by the SDK
Use the schema string element _experience.decisioning.propositionEventType.dismiss

Configure calculated metrics in Analysis Workspace

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
Messages Sent
The total number of messages sent. Includes successful or failed messages.
[Sends] + [Bounces] - [Bounces After Delivery]
Messages Delivered
The number of emails delivered to customers.
[Sends] - [Bounces After Delivery]
recommendation-more-help
080e5213-7aa2-40d6-9dba-18945e892f79