Documentation Experience Platform Mobile App Tutorial

Report and analyze using Customer Journey Analytics

Last update: June 17, 2024

Topics:
Mobile SDK

CREATED FOR:

Beginner
Intermediate
Developer

Learn how to report and analyze your mobile app interactions with Customer Journey Analytics.

The mobile app event data, which you collected and sent to Platform Edge Network in earlier lessons, is forwarded to the services configured in your datastream. If you followed the Send data to Experience Platform lesson, that data is now stored in an Experience Platform dataset and is available for Customer Journey Analytics to use for reporting and analysis.

Contrary to Adobe Analytics, Customer Journey Analytics uses data from datasets created in Experience Platform. Data is not sent directly to Customer Journey Analytics using the Adobe Experience Platform Mobile SDK, rather the data is sent to datasets. Connections are then configured in Customer Journey Analytics to select the datasets you’ll use in your reporting and analysis projects.

This lesson in the tutorial focuses on reporting and analyzing the data captured from the Luma tutorial app. One of the unique capabilities of Customer Journey Analytics is combining data from multiple sources (CRM, point-of-sale, loyalty application, call-center) and channels (web, mobile, offline) for gleaning deep insights into customer journeys. That capability is beyond the scope of this lesson. See Customer Journey Analytics overview for more information.

Prerequisites

Your organization must be provisioned and permission granted for Customer Journey Analytics. You must have administrator access to Customer Journey Analytics.

Learning objectives

In this lesson, you will:

Create a connection to define the datasets from Experience Platform you want to use in Customer Journey Analytics.
Create a data view to prepare the data from the datasets for your reporting and analysis
Create a project to build reports and visualizations so you can analyze the data from your mobile app.

The sequence is intentional. Connections use datasets, and data views use connections.

Create a connection

A connection in Customer Journey Analytics defines the datasets (and the data within these datasets) from Experience Platform that you want to use for reporting and analysis.

Navigate to the Customer Journey Analytics interface using the Apps menu in the top right.
Select Connections from the top menu bar.
Ensure you select the List tab in the Connections interface. You see a list of existing connections.
Select Create new connection.
In the Connections > Untitled connection screen, in Connection settings
1. Enter a Connection name, for example Luma App - AEP Mobile SDK Tutorial Connection.
2. Enter a Connection description, for example Connection for the Luma app used in the AEP Mobile SDK tutorial.
  
  In Data settings:
3. Select the sandbox that you have used to collect your mobile app data, for example Mobile and Web SDK Courses.
4. Select less than 1 million from the Average number of daily events.
5. Select Add datasets to select the datasets from Experience Platform you want to use in Customer Journey Analytics.
6. In the Add datasets wizard, Select datasets step,
  1. Select the following datasets:
    - Luma Mobile App Event Dataset, the dataset you created as part of the Create a dataset section in the Experience Platform lesson.
    - ODE DecisionEvents - sandbox name decisioning
    - AJO Push Tracking Event Datasets
  2. Select Next.
7. In the Add datasets wizard, Datasets settings step, you need to define the details for each of the event datasets.
  1. See the following tables for the proper setup:
    
    Dataset
    Person ID
    ①
    Timestamp
    ②
    Data source type ③
    Import all new data ④
    Backfill all existing data ⑤
    Luma Mobile App Event Dataset
    identityMap
    timestamp
    Mobile App Data
    enable
    enable
    ODE DecisionEvents - sandbox name decisioning
    identityMap
    timestamp
    Mobile App Data
    enable
    enable
    AJO Push Tracking Experience Event Dataset
    identityMap
    timestamp
    Mobile App Data
    enable
    enable
  2. Select Add datasets.
Back in the Connections > Luma App - AEP Mobile SDK Tutorial Connection, select Save to save your connection.

You have now defined your connection and Customer Journey Analytics adds the data from the datasets to its own internal database. This data collection can take some time, depending on the amount of data. For your tutorial app, anticipate a couple of hours for the data to appear in Customer Journey Analytics.

To view the status of your connection:

Select Connections in the main interface of Customer Journey Analytics.
Select the name of your connection, for example Luma App - AEP Mobile SDK Tutorial Connection.

In the Connections > Luma App - AEP Mobile SDK Tutorial Connection, you see:

Information on total records added, records skipped, and records deleted. Ensure you select All datasets and select an appropriate time period to view details about your connection. You can use to open a dialog to select the time period.
Information for individual datasets on records added, records skipped, records deleted, and more.

Create a data view

After the records have been added from the datasets to Customer Journey Analytics, you can create a data view to define which components of the data you want to report on.

A data view is a container specific to Customer Journey Analytics that lets you determine how to interpret data from a connection. You can configure standard and schema fields from any of the datasets that you have defined in your Connection as components (dimensions, metrics) in Analysis Workspace.

A data view in Customer Journey Analytics offers enormous flexibility in properly setting up and defining the data from your connection. In this tutorial, you use only the functionality that is required for your reporting and analysis. See Data views for more information.

To create your data view:

Navigate to the Customer Journey Analytics interface using the Apps menu in the top right.
Select Data views from the top menu bar.
Select Create new data view.
In Data views >, ensure that the Configure tab is selected.
1. Select your connection from the Settings Connection dropdown list, for example Luma App - AEP Mobile SDK Tutorial Connection.
2. Enter a Name for your data view, for example: Luma App - AEP Mobile SDK Tutorial Data view.
3. Select Save and continue.
In the Components tab of the Luma App - AEP Mobile SDK Tutorial Data view, you can define the metrics and dimension you want to use when reporting on your mobile app. By default, a number of standard metrics and dimensions (jointly referred to a components) are already configured for your data view. But your data view requires more components.
To add a schema field from your previously defined schema or out-of-the-box schemas (see Create a schema lesson), as a component (dimension or metric):
1. Find the schema field:
  - search for the component using the Search schema fields search field. For example, productListAdd, or
  - traverse down to the schema field within Event datasets .
    For example, Event datasets commerce productListAdds
2. Drag the specific schema field from the Schema fields pane and drop it on the METRICS or DIMENSIONS list in the Included components pane.
3. You can configure the settings of a component. Select the component and configure settings in the right pane.
  For example, you can rename commerce.productListAdds to Product Add To Lists using the COMPONENT SETTINGS > Component name field in the right pane.
  
  Or configure INCLUDE EXCLUDE VALUES.
4. Now that you understand how to add fields to your data view and configure the resulting component, use the tables below for a list of schema fields to add as metrics or dimensions. Use the Schema Path column value from the table below to search for or traverse to the specific schema field. Once metrics and dimensions are added, check the Component Settings column value in the table whether specific settings are required for a component, like its Component name or defining INCLUDE EXCLUDE VALUES.
  
  METRICS
  
  Component Name
  Dataset
  Schema Data Type
  Schema Path
  Component Settings
  Dismiss
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.dismiss
  Component Name: Dismiss
  Unsubscribe
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.unsubscribe
  Component Name: Unsubscribe
  Trigger
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.trigger
  Component Name: Trigger
  Display
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.display
  Component Name: Display
  Send
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.send
  Component Name: Send
  Interact
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  Integer
  _experience.decisioning.
  propositionEventType.interact
  Component Name: Interact
  Location Events
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset, ODE DecisionEvents - mobile-and-web-sdk-courses decisioning
  String
  Event Type
  Component Name: Location Events
  
  Product Views
  Luma Mobile App Event Dataset
  Double
  commerce.productViews.value
  Component Name: Product Views
  Product Add To Lists
  Luma Mobile App Event Dataset
  Double
  commerce.productListAdds.value
  Component Name: Product Add To Lists
  Purchases
  Luma Mobile App Event Dataset
  Double
  commerce.purchases.value
  Component Name: Purchases
  Save For Laters
  Luma Mobile App Event Dataset
  Double
  commerce.saveForLaters.value
  Component Name: Save For Laters
  App Interactions
  Luma Mobile App Event Dataset
  Double
  _techmarketingdemos.appInformation.
  appInteraction.appAction.value
  Component Name: App Interactions
  Screen Views
  Luma Mobile App Event Dataset
  Double
  _techmarketingdemos.appInformation.
  appStateDetails.screenView.value
  Component Name: Screen Views
  
  NOTE
  Note how the schema field for the Location Events metric is using INCLUDE EXCLUDE VALUES to count event types that contain location.
  
  Your data view configuration for METRICS should match below after you have added all schema fields from the table above as a metric component:
  
  DIMENSIONS
  
  Component Name
  Dataset
  Schema Data Type
  Schema Path
  Component Settings
  City
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset
  String
  placeContext.geo.city
  Component Name: City
  Event Types
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset, ODE DecisionEvents - mobile-and-web-sdk-courses decisioning
  String
  eventType
  Component Name: Event Types
  Decision Option Name
  AJO Push Tracking Experience Event Dataset, Luma Mobile App Event Dataset, ODE DecisionEvents - mobile-and-web-sdk-courses decisioning
  String
  _experience.decisioning.
  propositions.items.name
  Component Name: Decision Option Name
  App Interaction Name
  Luma Mobile App Event Dataset
  String
  _techmarketingdemos.appInformation.
  appInteraction.name
  Component Name: App Interaction Name
  Screen Name
  Luma Mobile App Event Dataset
  String
  _techmarketingdemos.appInformation.
  appStateDetails.screenName
  Component Name: Screen Name
  Activity Name
  ODE DecisionEvents - mobile-and-web-sdk-courses decisioning
  String
  _experience.decisioning.
  propositionDetails.activity.name
  Component Name: Activity Name
  Offer Name
  ODE DecisionEvents - mobile-and-web-sdk-courses decisioning
  String
  _experience.decisioning.
  propositionDetails.selections.name
  Component Name: Offer Name
  
  Your data view configuration for DIMENSIONS should match below after you have added all schema fields from the table above as a dimension component:
5. Select Save and continue.
The Settings tab of the Luma App - AEP Mobile SDK Tutorial Data view allows you to configure filters and session settings. For this tutorial, no additional configuration is required.
- Select Save and finish.

You have defined your data view and everything is in place to start building your reports and visualizations.

Create a project

Workspace projects are used in Customer Journey Analytics to build reports and visualizations. There are many possibilities to build comprehensive reports and engaging visualizations, but this is outside the scope of this tutorial. See Workspace Overview and Build a new project for more information.

In this section of the lesson, you create a project that shows reports and visualizations on:

App Usage: using the information on screen and app interactions.
Commerce: using the commerce events, like product view, add to cart and purchase.
Offers: using the offers displayed events in the app.
Store Visits: using the (simulated) geofence events from the app.

To create your project:

Navigate to the Customer Journey Analytics interface using the Apps menu in the top right.
Select Workspace from the top menu bar.
Select Create project.
1. Select Blank Workspace project from the popup dialog.
2. Select Create.
You are presented with the New project interface. In this interface, you build your reports and visualizations.
Select the name of the project (New project) and provide your own name for the project. For example, Luma App - AEP Mobile SDK Tutorial Project.
To save the project, select Project > Save.
In the Save dialog, ignore all other fields and select Save.

IMPORTANT

Remember to save your project regularly, otherwise your changes are lost. You can quickly save your project using ctrl + s (Windows) or ⌘ (cmd) + s (macOS).

You have now set up your project. A Freeform table is provided by default. Before you add components, ensure your Freeform panel is using the correct data view and time period.

Select your data view from the dropdown list. For example, Luma App - AEP Mobile SDK Tutorial Data view. If you cannot see your data view in the list, select Show all at the bottom of the dropdown list.
To define the appropriate time period for the panel, select the default preset This month enter a custom start and end date, or use a Preset (like Last 6 full months) and select Apply.

App Usage

Now you’re ready to report on how the app is used. You have added the necessary code in the app to register app interactions and which screens are used in the app (see the Track Events lesson) and you now want to report on this data.

Screen Names

To report on the screens viewed in the app:

Rename your Freeform panel to App Usage.
Rename your Freeform table to Screen Names.
Select Show all below the METRICS list.
Drag and drop the Screen Views component on Drop a metric here (or any other component).

Your freeform table now shows screen views for each day for your selected time period. However, you want to show the number of screen views for each of the different screens used in the app.
To show the DIMENSIONS list of components, select to remove the Metrics filter from the components rail.
Select Show all below the DIMENSIONS list.
Drag and drop the Screen Name component on the Day header. The operation shows Replace to indicate the replacement of the dimension.

Your first Freeform table in your report is complete.

CJA Projects 10

NOTE

Save your project before proceeding.

App Interactions

Next, you’ll build a Freeform table to report on how users interacted with the app.

Select and from the popup to add a new Freeform table.
Rename Freeform table (2) to App Interactions.
Drag and drop the App Interactions metric on Drop a metric here (or any other component).
Drag and drop the App Interaction Name dimension on the Day header to replace this dimension.

Your second report is now ready, showing app interactions.
CJA Projects 12

The information is limited mainly because you implemented MobileSDK.shared.sendAppInteractionEvent(actionName: "<actionName>") API calls only on the login screen. If you add this API call into more screens of your app, this report becomes more informative.

NOTE

Save your project before proceeding.

Commerce

You now want to report, in a separate panel, on commerce events occurring in the app.

Commerce Events

Select outside of the current App Usage panel, to create a new panel.
Ensure you select the appropriate time period.
Select Freeform table to create a new Freeform table.
Rename Panel to Commerce.
Rename Freeform table to Commerce Events.
Drag and drop Product Views metric on to Drop a metric here (or any other component).
Drag and drop the Product Add To Lists metric to the right of the Product Views column to insert this column in the freeform table. Ensure + Add (in blue) is shown when inserting the column.
Repeat the previous step to add the Save For Laters metric and the Purchases metric to the freeform table.
Drag and drop the Month dimension on top of the Day dimension to change the reporting from daily to monthly.

Your Commerce Events report is complete.

CJA Projects 16

NOTE

Save your project before proceeding.

Fallout

Next, you’ll build a fallout visualization for the commerce funnel that shows how many users that viewed products added these products to their cart, and from there, how many users saved these products for later.

Select within the Commerce panel and from the popup select (representing the Fallout visualization).
Select Product Views from the Add touchpoint dropdown list.

Alternatively, you can drag and drop the Products View dimension below the All people dimension in the Fallout visualization.
Repeat the above step for Product Add To Lists and Purchases dimensions.

Your Fallout visualization report is complete.
CJA Projects 19

NOTE

Save your project before proceeding.

Offers

You want to report on how many offers and what offers are displayed to the users of your app.

Monthly Overview

Select outside of the current Commerce panel, to create a new panel.
Rename the Panel to Offers.
Ensure you select the appropriate period.
Select Freeform table to create a new freeform table.
Rename the Freeform table to Monthly Overview.
Drag and drop the Display metric on to Drop a metric here (or any other component).
Drag and drop the Month dimension on the Day column to replace the dimension.

Your Monthly Overview for Offers is complete.

CJA Projects 20

NOTE

Save your project before proceeding.

Offers to People

You also want to have a report showing which offers were shown in what numbers to the users of the app.

Select within the Offers panel and from the popup to add a new Freeform table.
Rename Freeform table (2) to People.
Drag and drop the People metric on to Drop a metric here (or any other component).
Drag and drop the Activity Name on the Day column to replace the dimension.
Right-click on the row, identifying one or more of the offer decisions you defined in the Create and display offers with Decision Management lesson. For example, Luma - Mobile App Decision.
From the context menu, select Breakdown > Dimensions > Offer Name. This selection will breakdown the Activity Name dimension into Offer Names.

Your Offers to People report is complete.

CJA Projects 21

NOTE

Save your project before proceeding.

Store Visits

Finally, you want to report on store visits.

Select outside of the current Offers panel, to create a new panel.
Rename the Panel to Store Visits.
Ensure you select the appropriate period.
Select Freeform table to create a new freeform table.
Rename **Freeform table ** to Store Entries / Exits Across Cities.
Drag and drop the Location Events metric on to Drop a metric here (or any other component). The report now shows a daily overview of all the location events that occurred in the app. Remember how you specifically configured this dimension as part of your data view.
Drag and drop the City dimension on the Day column header to replace the dimension. The report now shows the cities for the location events.
To remove geolocation events with no cities associated to it select , and from the Search popup, turn off Include “No value”, then select Apply.

This action removes the No value row from the report.
Select all rows in the table, right-click, and from the context menu select Breakdown > Dimension > Event Types.

Your Store Visits reportis complete. You now have a report showing users being in and out of the vicinity of your store locations (as you defined these locations in the Places lesson).

CJA Project 23

Note that if you really want to report on people physically visiting your store, you can use beacons. But hopefully, you have captured the concept of reporting on geolocation data.

Next steps

You should now have a basic understanding of how to report and visualize on your mobile app usage, interactions, and more using Customer Journey Analytics.

SUCCESS

Thank you for investing your time in learning about Adobe Experience Platform Mobile SDK. If you have questions, want to share general feedback, or have suggestions on future content, share them on this Experience League Community discussion post.

Next: Conclusion and next steps

recommendation-more-help