Cross Channel Data
IMPORTANT: numbers shown in this guide, including screenshots, may differ from your reports due to different underlying datasets.
Goals
- Understand what types of cross-channel data exist in this data view.
- Identify the overlap between customers who interact on digital, airport and call centre channels.
- Explore the mobile-to-web research pattern.
Expanded Metrics and Dimensions
Scenario: Before forming a hypothesis, explore what data is available. With all of WKND's channels flowing into AEP, CJA lets you place web page views, airport check-ins, and call centre contacts side by side in a single table.
Task: Explore the interaction between metrics and dimensions across channels.
- Add a new freeform table: Click the
icon at the bottom of the panel →
icon.
- Rename it Expanded Metrics
- Add the following components:
- Dimensions: Interaction Channel
- Metrics: Events, Page Views, Calls, Bookings

Notice that bookings are available across multiple channels while calls are only coming from the call centre channel.
- Replace Interaction Channel for Call Reason: drag the Call Reason dimension over Interaction Channel in the table until the Replace prompt appears.

This is the reason for a call that a call center agent entered when they spoke with a customer on the phone, events and calls are associated with them but no page views. Call reasons are logged by the agent; they have no page-level context.
- Replace Call Reason with Page Name

Page Views are associated with each page, but there are no Calls associated with each Page. This is because there are no rows that are both Web and Call rows, they originate from entirely separate datasources and are ingested into separate datasets in Adobe Experience Platform.
This mutual exclusivity is precisely what makes the Call Deflection exercise later so powerful: we use attribution to infer the relationship between pages and calls even though they never share a row.
Cross-channel Customer Overlap
Scenario: Now that you understand the data shape, explore whether WKND's channels are serving distinct groups of customers or the same customers moving between them.
Task: Visualise how many customers interact across more than one channel.
Build a segment
Segments in CJA are similar to Segments in Adobe Analytics. And once these segments are built in CJA, they can be shared to Experience Platform, so you can use them in Real-time CDP, for example.
Using segments is one way that you can gain more insight into the cross channel data. You can create segments to understand which sessions were "web" only sessions, which were "call center" only and which were in fact "cross channel".
Keep in mind for CJA, there is no concept of "browser" session, the session calculation is controlled by the event timeout set in your data view. As long as the customers interacts on both channels within the timeout window their events will be considered part of the same session in CJA.
Create the Cross-Channel Sessions segment.
- On the main menu, click on Components > Create segment...

- Drag the Page Views metric, and drop it in the Definition section, over the text Drag & drop Metric(s), Segment(s), and/or Dimensions here..

- Change the operator from Equals to Exists.
- Drag the Calls metric, and drop it below the Page Views metric.
- Change the operator for the Calls metric from Equals to Exists.
- From the drop down list beside Include, select Session.
- Name your segment, [{{LASTNAME}}] - Cross-channel sessions
- Click Save.

This segment will find sessions where a customer had at least one Page View and at least one Call in a session.
You can repeat the same steps to create segments with only Web interactions or only Calls. To save time we have created these segments for you:
- Sessions including online channels
- Sessions including a call
- Sessions including airport
Analyse Overlaps
Use a Venn diagram in combination with session based segments to visualise the overlap of customers interacting online, at the airport and with the call centre.
- Add a Venn visualisation: click the
icon at the bottom of the panel, then the
icon.

- Label it Cross-channel Sessions.
- Add the following 3 segments:
- Sessions including online channels
- Sessions including a call
- Sessions including airport
- Set the metric to Sessions.
- Click Build.


Explore the overlaps by hovering over the intersecting circles.

The overlap between the sessions including a call and the sessions including online channels shows that a portion of customers may start their session online and call the call center directly after (the time window for a Session is defined as 30 minutes).
Save your changes: Use Project > Save (or Cmd+S / Ctrl+S).
Channel Pathing
Scenario: The mobile product team wants to understand whether mobile users are staying in-app or completing their journeys on a different device.
Task: Visualise the path customers take after a mobile interaction.
- Add a Flow diagram click the
icon at the bottom of the panel, and then
icon.
- Label it Channel Pathing.
- In the Starts with drop down, search for Interaction Channel dimension, click the arrow and select Mobile.

Notes on Dimension configuration:
- Dropping a dimension as the Entry point will show the top first value seen in that dimension either at a Session or Person level.
- Dropping a dimension as the Exit point will show the top last value seen for a dimension at a Session or Person level.
- Dropping a dimension or a dimensional element in the middle will show you how often that element is the entry or exit, as well as the top elements a person saw prior or after from a pathing perspective. This can also be configured at the Session or Person level.
Click to Build.

Notice there are a lot of people moving to the website after starting on the mobile app.
An interesting way to do further analysis around the types of customers that follow this specific path is to create a segment of these customers.
- Right-click on the Web node to open the menu.
- Select Create segment for this path.

This will open the Segment builder UI with a pre-built definition based on the chosen path.
- Click Cancel as there is no need to save the segment in this exercise.

Save your Changes: Use Project > Save (or Cmd+S / Ctrl+S) after completing each section.
Congratulations, this completes the Cross Channel Data Analysis exercise!