Create a Data View Using Adobe Experience Platform

Create a Data View in CJA


## Prepare data for analysis

After creating a data view, you need to prepare the data, select a data view to use for reports, set thecalendar, and optionally create calculated metrics and dimensions for the reports. Finally, you create basic and advanced reports and share them with stakeholders in your organization.

1. Create a project in CJA
2. Create calculated metrics and dimensions

## Task 1: Create a project in CJA

1. Return to the Data View Menu, shown and identified your data view create Omni Channel Data View.
   ![Adobe](/images/cja/cja95.png "Prepare data for analysis in CJA")
   Alternatively, you can navigate to the Project Menu, choose Create Project and select the data view to use.
2. Click the Create project from the menu list. The New Project page opens, as shown
   ![Adobe](/images/cja/cja96.png "Prepare data for analysis in CJA")
3. Click Create New Project. The New Project page opens, as shown:
4. In the Freeform section, ensure that the data view that you created is selected.
5. Click the date range below the data view. A calendar opens
   ![Adobe](/images/cja/cja97.png "Prepare data for analysis in CJA")
6. Select a start date and end date. For this exercise, select 2023-01-01 as the start date and current date as the end date. Alternatively, you can also type the dates in the start date and end date boxes that appear at the right while selecting the dates
7. Click the Show advanced settings link below the calendar to open the settings page, a s shown
   ![Adobe](/images/cja/cja98.png "Prepare data for analysis in CJA")
8. Select the Use rolling dates check box and click Apply to all panels to apply the changes.
9. Press the Ctrl + S keys (Windows) or the Command + S (Mac) keys. The Save Project dialog box opens, as shown:
   ![Adobe](/images/cja/cja99.png "Prepare data for analysis in CJA")
10. In the Project name box, type Omni Channel Project Analysis Reports.
11. In the Description box, type an appropriate description for the project.
12. Click Save to save the project.


Prepare data for analysis Using Adobe Customer Journey Analytics

Prepare Data for Analysis in CJA


1. Ensue the Adobe Experience Platform home is open
2. Scroll down the left pane, under DATA COLLECTION, click Data streams. The Data streams page opens.
3. Click New Data stream, as shown:

![Adobe](/images/data-stream1.PNG "data-stream image")
The New Data stream wizard opens
Preform the following as shown:

1. In the Name box, type Data stream name.
2. In the Description box, type name of Data stream description.
3. From the Event Schema drop down, select the Schema name
   ![Adobe](/images/data-stream2.PNG "data-stream image")
   Note: The Save and Add Mapping option helps map, transform, and validate date and from XDM. When configuring a Platform-enabled data stream, you can use data preparation capabilities to map your source data to XDM when sending it the Platform Edge Network. For now, you can skip the Save and Add Mapping option for data preparation.
4. Click Save. The Add service page opens..
5. Click Add Service, as shown:
   ![Adobe](/images/data-stream3.PNG "data-stream image")


Create a Data stream that sends customer records and event to Experience Platform

Create and Configure Data Stream


## Create calculated metrics and dimensions

Although we have organized all the components in the data view, you still need to adapt some of them, so that business users are ready to start their analysis. If you remember, we did not specifically bring in metrics such as Add to Cart, Product View or Purchases into the D ata V iew. However, we do have a dimension called Product Interaction Type.

1. Create Product Views derived from Event Type

   - On the Projects page, click the project that you created in Task 1 of this exercise, if it is not already opened, as shown
     ![Adobe](/images/cja/cja34.png "Create calculated metrics and dimensions")
     Note: Refresh your browser if the Add (+) is not visible to the right of the components

2. In the METRICS component section, click the + sign, as shown. The Calculated Metric Builder page opens.
3. In the Search components box on the left, type Event Type. The result of the search appears.
4. Drag Event Type component onto the Definitions section. The Create Filter fromDimension dialog box opens, as shown
   ![Adobe](/images/cja/cja35.png "Create calculated metrics and dimensions")
5. Click the Select value box, search or type commerce.productViews and press the Enter key. The value is updated in the dialog box, as shown:
   ![Adobe](/images/cja/cja36.png "Create calculated metrics and dimensions")
6. Click Done. The Summary and Definition sections of the Calculated metric builder page is updated.
7. In the Search components box, type Events. The Events (events) component appears in the search result.
8. Drag Events (events) to the Definitions section. The Calculated metric builder page is updated, as shown:
   ![Adobe](/images/cja/cja37.png "Create calculated metrics and dimensions")
9. In the Title box, type Product Views.
10. In the Description box, provide a description. For example, Product Views.
11. Click Save to save the calculated metric and verify that the Product Views - metric is listed in the METRICS section, as shown
    ![Adobe](/images/cja/cja38.png "Create calculated metrics and dimensions")

## Calculated Metrics for Product Add to Cart

1. In the METRICS component section, click the + sign. The Calculated metric builder page opens.
2. In the Search components box on the left, type Event Type. The result of the search appears.
3. Drag Event Type component onto the Definitions section. The Create Filter fromDimension dialog box opens, as shown
4. Click the Select value box, type commerce.productListAdds and press the Enter key. The value is updated in the dialog box, as shown:
   ![Adobe](/images/cja/cja39.png "Create calculated metrics and dimensions")
5. Click Done. The Summary and Definition sections of the Calculated metric builder page is updated.
6. Customer Journey Analytics Powered by Adobe Experience Platform 676. In the Search components box, type Events. The Events (events) component appears in the search result.
7. Drag Events (events) to the Definitions section. The Calculated metric builder page is updated.
8. In the Title box, type Add to Cart.
9. In the Description box, provide a description.
10. Click Save to save the calculated metric and verify that the Add to Cart metric is listed in the METRICS section.

## Create Calculated Metric for Product Purchases – Event Type

1. In the METRICS component section, click the + sign. The Calculated metric builder page opens.
2. In the Search components box on the left, type Event Type. The result of the search appears
3. Drag Product Interaction Type component onto the Definitions section. The Create Filter from Dimension dialog box opens, as shown.
4. Click the Select value box, type commerce.purchases and press the Enter key. The value is updated in the dialog box
5. Click Done. The Summary and Definition sections of the Calculated metric builder page is updated.
6. In the Search components box, type Events. The Events (events) component appears in the search result.
7. Drag Events (events) to the Definitions section. The Calculated metric builder page is updated.
8. In the Title box, type Purchases.
9. In the Description box, provide a description.
10. Click Save to save the calculated metric and verify that the Purchases metric is listed in the METRICS section, as shown
    ![Adobe](/images/cja/cja40.png "Create calculated metrics and dimensions")

## Calculate the Conversion Rate using the formula: purchases/session in percentage

Typically, conversion rate means Conversions / Sessions.

1. Click the Purchase metric that you created in the previous task and select the information icon, as shown. The Purchases pop-up window appears
   ![Adobe](/images/cja/cja41.png "Create calculated metrics and dimensions")
2. Click the Edit (pencil) icon. The Calculated metric builder page opens as shown
   ![Adobe](/images/cja/cja42.png "Create calculated metrics and dimensions")
3. In the Search components box, type Sessions. The Sessions (sessions) component appears in the search result.
4. Drag Sessions (sessions) to the Definitions section and place it below Events. The Calculated metric builder page is updated, as shown:
   ![Adobe](/images/cja/cja43.png "Create calculated metrics and dimensions")
5. Notice that the division operator is automatically selected.
6. Click the Format drop-down arrow and select Percent. In the Decimal places box, type or select 2, as shown
7. In the Decimal places box, type 2, as shown:
   ![Adobe](/images/cja/cja44.png "Create calculated metrics and dimensions")
8. In the Title box, type Conversion Rate.
9. In the Description box, provide a description.
10. Click Save as to save the calculated metrics without making changes to the Purchases calculated metrics. The Conversion Rate metric is listed in the METRICSsection, as shown
    ![Adobe](/images/cja/cja45.png "Create calculated metrics and dimensions")


Create calculated metrics and dimensions Using Adobe Customer Journey Analytics

Calculated Metrics and Dimensions


## Basic Analysis

Basic analysis enables you to analyze:

    - The data sources with maximum number of events, sessions, and people.
    - The online versus in- store revenue over  time.
    - The audience size by data sources, such as ad impression data, Adobe Analytics data, email data,POS data, call center data, and survey data.

Advanced Analysis:

Advanced analysis enables you to leverage the features of Analysis Workspace to perform advanced analysis and create reports, such as Flow diagram, fallout reports, and break down dimensions.

## Flow Diagram

Flow diagram enables you to:

    - View customer paths through your websites and app.
    - Analyze where customers go before and after specified checkpoints, such as entry,  a specific dimension, or exit.
    - Create filters by designating a specific point in a chosen path.

![Adobe](/images/cja/cja46.png "Creating Analysis Reports")

## Fallout Reports

Fallout reports enable you to:

    - Show where visitors left (fell out) and continued through (fell through) a predefined sequence of pages.
    - Display conversion and fallout rates between each step or touch point in a sequence.
    - Analyze conversion rates through specific processes on your site, such as a purchase or registration process.
    - Analyze general, wider-scope traffic flows.
    - Analyze correlations between events on your site. Correlations display percentage of people who looked at your privacy policy went on to purchase a product.

## Break down dimensions

Break down dimensions enable you to:

    - Break down your data in unlimited ways for your specific needs.
    - Break down metrics by dimension items or audience segments across selected time periods.You can also drill down further to a more granular level.
    - Build queries using relevant metrics, dimensions, segments, timelines, and other analysis breakdown values.

![Adobe](/images/cja/cja47.png "Creating Analysis Reports")

Any breakdown within a table can also have any attribution model applied to it. This attribution model can be the same or different from the parent column. For example, you can analyze linear orders on your marketing channels dimension but apply u-shaped orders to the specific tracking codes within a channel.

![Adobe](/images/cja/cja48.png "Creating Analysis Reports")

Note: - The number of breakdowns to show in the table is limited to 200. - This limit will increase for exporting breakdowns.

## Create Basic and Advanced Reports

Scenario: With your Data View done in step 4 of the CJA Workflow, you can now create reports and data visualization to prove answers to questions about customer experience while interacting with your brand. We will cover some of the queries done in Module 7 - Query Service so you can see how easy is to run the same queries and more but without using SQL and relying only on the drag and drop philosophy of Analysis Workspace.

## Tasks

Specifically, the reports and data visualization we will create in this will provides answers to the following questions:

    - How many product views do we have on a daily basis?
    - Top 5 Product Page by Page Name with events, session and people.
    - Call center interaction Type by topics and call feeling.
    - Product Interaction funnel, from viewing to buying.
    - What do people do on the site before reaching the Cancel Service page?
    - How are customers with a Positive Call center contact performing against the main  KPIs?
    - Which Page Name (Product) shows the maximum number of events, sessions, and people.

## Task 1: Create Analysis Report about How many product views do we have on a daily basis

1. Open CJA and click Projects on the top navigation bar. The available projects appear.
2. Click the project that you created in the previous exercise. For example, AMO - Omnichannel Project Analysis Reports. The Omnichannel Analysis project page open.

   ![Adobe](/images/cja/cja49.png "Creating Analysis Reports")

3. Find the Calculated Product View you created earlier from the Metrics list in the left trail. drag and drop it in to the canvas, on the top right with in the freeform table.
4. Automatically the dimension Day will be added to create your first table. Now you can see your question answered on the fly.
5. Click up arrow key on the right to the order of display from ascending to descending, as shown:

   ![Adobe](/images/cja/cja50.png "Creating Analysis Reports")

6. Create a Visualization report using the steps below:

   - Right- click on the metric summary.
   - Click on Visualize and then select Line as visualization, as shown

     ![Adobe](/images/cja/cja51.png "Creating Analysis Reports")

   - The Line graph displays, as shown:

     ![Adobe](/images/cja/cja52.png "Creating Analysis Reports")

   - The Line graph displays, as shown:

   ![Adobe](/images/cja/cja53.png "Creating Analysis Reports")

   - Click Lock Selection and select Selected Items to lock this visualization so that it always displays a timeline of Product Views, as shown:

   ![Adobe](/images/cja/cja54.png "Creating Analysis Reports")

   - Click the Freeform table name and type the text Daily Product Views.
   - Save the Project. The Tabular report displays as shown:

   ![Adobe](/images/cja/cja55.png "Creating Analysis Reports")

## Task 2: Create Analysis Report for the Top 5 Product Page by Page Name with events,session and people

1. Confirm or change the calendar as follows:

   - Start date: 2022-01-01.
   - End Date: Current date.
   - Set rolling date in the Advanced settings.
   - Apply the changes to all panels

2. Navigate to the Insert > Freeform on the Project Menu bar to add a new Freeform Table.
3. n the left side menu, find the Product Name – Dimension.
4. Drag and drop Product Name to replace onto the canvas of the Freeform. The result is as shown:

   ![Adobe](/images/cja/cja56.png "Creating Analysis Reports")

5. Right-click the value section of the Product Name dimension and navigate to Breakdown >Dimensions > Page Name. The result is as shown:

   ![Adobe](/images/cja/cja57.png "Creating Analysis Reports")

6. Add Sessions and People to the metrics section. The result is as shown:

   ![Adobe](/images/cja/cja58.png "Creating Analysis Reports")

7. Finally you can add more visualizations.

   - Highlight the Page Name section of the Table.
   - On the left side, under visualizations, search for Donut.
   - Take Donut, drag-and- drop it on top of the table in the canvas. Visualization reports opens, as shown.

   ![Adobe](/images/cja/cja59.png "Creating Analysis Reports")

   - Lock the Donut Visualization with the table.
   - Name the report as Top 5 Product Name by Page Name with events, session and people.
   - Save the Analysis Report.

## Task 3: Create an Analysis Report for Call Center Interaction types

1. Add a New Freeform Table to the Basic Analysis Reports Panel
2. Configure the Calendar parameters as follows:

   - Start date: 2022-01-01.
   - End Date: Current date.
   - Set rolling date in the Advanced settings.
   - Apply the changes to all panels.

3. Move the New Freeform table to the bottom of the Panel.
4. Drag and drop the Call Topic dimension over the Day dimension on the table.
5. Add Session and people the metrics sections. The results is as shown:
6. Name the report Call Center Interaction Analysis Report by topics
7. Gene rate a Horizontal Stack bar chart and lock the selected location.
8. Save the Project. The result is as shown below

   ![Adobe](/images/cja/cja60.png "Creating Analysis Reports")

## Task 4: Product Interaction funnel, from viewing to buying

1. Add a new Panel below the Basic Analysis Reports pane
2. Configure the Calendar parameters as follows:

   - Start date: 2022-01-01.
   - End Date: Current date.
   - Set rolling date in the Advanced settings.
   - Apply the changes to all panels.

3. Click the visualization Fallout in the new panel and name it as Advanced Analysis Reports, as shown:

   ![Adobe](/images/cja/cja61.png "Creating Analysis Reports")

4. Drop the menu below the Add touch points and select Event Type > commerce.productViews.The result is as shown:

   ![Adobe](/images/cja/cja62.png "Creating Analysis Reports")

5. Repeat step 4 to add Event Type > commerce.productListAdds and commerce.purchases, as shown:

   ![Adobe](/images/cja/cja63.png "Creating Analysis Reports")

6. Add a Freeform in the Advanced Analysis Reports Panel for Page Name as shown:
7. Save the Analysis Project

## Task 5 : What do people do on the site before reaching the Cancel Service pag

Flow diagrams:

    - Shows customer paths through your websites and  applications.
    - Visualize the customer journey through your website or application.
    - Analyze where customers go before and after specified checkpoints, such as entry, a  specific dimension, or  exit.

1. Make the Advance Analysis Reports your focus panel.
2. Click on the Visualization Object in the top left tra
3. Drag and drop Flow diagram from the list below the fallout report. The flow diagram windows opens.

   ![Adobe](/images/cja/cja64.png "Creating Analysis Reports")

4. Select the component tab in the left trail and search for Page Name Dimension.
5. Drag and drop the Page Name Dimension onto the Dimension or item in the middle of the flow diagram. The flow diagram displays the page flow, as shown:

   ![Adobe](/images/cja/cja65.png "Creating Analysis Reports")


Creating Analysis Reports in Using Adobe Customer Journey Analytics

Creating Analysis Reports in CJA


create a CJA Connections configured with Website datasets AEP Demo - Website Interactions, AEP Demo - Website Registration, and AEP Demo - Call Center Interactions. The product of the exercise is an enabled connection required for the creation of Data Views

1. Create a new CJA connection.
2. Add Experience Platform datasets to the connection.
3. Stitch together selected datasets in the connection.
4. Configure the naming and streaming details and enable the CJA connection.

## Task 1: Create a new CJA connection

1. Log into the Experience Platform UI with Cloud credentials. The Landing Page of the Platform UIopens, as shown:

![Adobe](/images/cja/cja68.png "Create and configure a connection")

2. Click the app selector icon at the upper- right corner and select Customer Journey Analytics. TheCustomer Journey Analytics page opens.
3. Verify that you have access to Projects, Connections, Data Views and Components tabs on the top navigation bar, as shown:

![Adobe](/images/cja/cja69.png "Create and configure a connection")

4. Click the Connections tab to view the available connections.
5. Click Create new Connection. The Create connection page opens. The page is categorized into three different sections, as shown:

![Adobe](/images/cja/cja70.png "Create and configure a connection")

There are four different areas in the CJA Connection Configuration:

1. Connection Settings

   - Name: Required
   - Description: Optional but Recommended
   - ags: Optional

2. dd datasets: Lists of available Experience Platform datasets.
3. Data setting.

   - Enable rolling data window: Allows you to Define data retention as a rolling window in months at a connection level.
   - Select number of months: Allows you delete older data and retain latest months dataSpecified by the number of months
   - Sandbox: The AEP Org containing data to be use
   - Average number of daily events: Select a range for the number of expected daily events for the entire connection.

4. Dataset list details: Add and Configure datasets in a connection

## Task 2: Configure the CJA Connection

1.  Provide the details of the Connection settings section, as shown:

    - Name: Omnichannel Data Connection-PROD- MMDDYYYY. For example, AMO – Omnichannel Data Connection- PROD-04202022.
    - Description (Optional): In the Description box, type a description for the connection. In this case, simply use the name as the description, i.e. Omnichannel DataConnection- PROD-04202022

2.  Configure the Data setting as follows:

    - Enable rolling data window: Unchecked
    - Sandbox: Prod
    - Average number of daily events: less than 1 million

3.  Add the datasets to the connection using the steps below:

    - Click Add datasets on the top right corner o r click Add datasets button in the Dataset list window. An Add dataset windows opens, as shown:

    ![Adobe](/images/cja/cja71.png "Create and configure a connection")

4.  Search for and select the following datasets to the CJA Connection

    - AEP Demo Luma Telco Website Interactions
    - AEP Demo Website Registration
    - AEP Demo Call Center Interactions

    The CJA Connection with the selected dataset is as shown:

    ![Adobe](/images/cja/cja72.png "Create and configure a connection")

5.  Click Next to continue to the Dataset setting phase, as show:

    ![Adobe](/images/cja/cja73.png "Create and configure a connection")

6.  Enable Import all new data and Backfill all existing data for all datasets in the connection.

    Click Add dataset to return to the CJA Connection settings, as shown:
    ![Adobe](/images/cja/cja74.png "Create and configure a connection")

7.  Click Connection preview button on the top right corner. The combined data from the selected dataset opens, as shown:
    ![Adobe](/images/cja/cja75.png "Create and configure a connection")

8.  Review and close the Connection preview window.
9.  Click Save to save the CJA Connection configuration.
10. Close the No Support.. Window Overly. The Connection Manager opens, as shown:

    ![Adobe](/images/cja/cja76.png "Create and configure a connection")

## Note:

Backfill historical data

Import all existing data lets you backfill historical data. Keep this in mind:

    - We have removed the backfill (historical data import) limitation. Previously, you could backfill a maximum of 2.5 billion rows on your own and otherwise required engineering involvement. Now,you can backfill data on your own, without any limitations.
    - We prioritize new data added to a dataset in the connection, so this new data has the lowest latency.
    - Any backfill (historical) data is imported at a slower rate. The latency is influenced by how much historical data you have, combined with the Average number of daily events  setting you selected.For example, if you have more than one billion rows of data per day, plus 3 years of historical data,that could take multiple weeks to import. On the other hand, if you have less than a million rows per day and one week of historical data, that would take less than an hour.
    - Backfilling applies to the whole connection, not to each dataset individually.
    - The  Adobe Analytics Source Connector  imports up to 13 months of data, irrespective of size.

## Data Available for Reporting

    - There is a latency of 1- 2 hours to get the data to appear in reporting once it is added.
    - Represents the total number of event dataset rows available for reporting, for the entire connection.This count is independent of any calendar settings.
    - You can Refresh and check the status Backfill data, as shown:

![Adobe](/images/cja/cja77.png "Create and configure a connection")

Click the Connection Link on the top right corner or the Menu bar of the screen to return to theCreate New Connection window, as shown:


Create and configure a connection Using Adobe Experience Platform

Create and configure a connection


## Business Need

![Adobe](/images/cja/cja.png "Create and Analyze Reports in CJA")

## Traditional BI Framework: Limitations

![Adobe](/images/cja/cja2.png "Create and Analyze Reports in CJA")

    - Business users do not know the questions ahead of time.
    - Insights and decisions are found in the process of discovery.
    - Many users can not write queries but need deep-dive insights.

## Why Adobe Customer Journey Analytics?

![Adobe](/images/cja/cja3.png "Create and Analyze Reports in CJA")

## Adobe Customer Journey Analytics - Use Cases

![Adobe](/images/cja/cja4.png "Create and Analyze Reports in CJA")

## Adobe Customer Journey Analytics vs. Adobe Analytics

![Adobe](/images/cja/cja5.png "Create and Analyze Reports in CJA")

Use Adobe Customer Journey Analytics for:

    - Multi channel data, such as call center or offline.
    - Data from larger ecosystem, such as Adobe Experience Platform.
    - Versatile architecture to collect and enrich data.
    - Cross channel attribution.

## Data Processing in Analytics and Customer Journey Analytics

![Adobe](/images/cja/cja6.png "Create and Analyze Reports in CJA")

## Adobe Customer Journey Analytics System

![Adobe](/images/cja/cja7.png "Create and Analyze Reports in CJA")

## What is Adobe Customer Journey Analytics?

An application that:

    - Is built on Experience Platform.
    - Brings Analysis Workspace capabilities in Experience Platform.
    - Contextualizes and visualizes data.
    - Stitches online and offline data together to create analysis reports.
    - Delivers context & clarity to the complex multi-channel journey.

## Adobe Customer Journey Analytics | Benefits

    - See the customer in the context of a complete journey across channels.
    - Make insights available to everyone.
    - Harness the power of data science for your analysts.
    - Visualize and interact with your datasets using ad-hoc reporting.
    - View non web data with digital data.
    - Exert greater control over your data customization.

## Adobe Experience Cloud Architecture

    ![Adobe](/images/cja/cja8.png "Create and Analyze Reports in CJA")

## Customer Journey Analytics Data Flow with Experience Platform

![Adobe](/images/cja/cja9.png "Create and Analyze Reports in CJA")

## Adobe Customer Journey Analytics | Architecture

![Adobe](/images/cja/cja10.png "Create and Analyze Reports in CJA")

## Adobe Customer Journey Analytics Workflow

![Adobe](/images/cja/cja11.png "Create and Analyze Reports in CJA")

## Connections in Adobe Customer Journey Analytics

    - Help integrate datasets from AdobeExperience Platform to Workspace.
    - Establish a connection between datasets inExperience Platform and Workspace.

![Adobe](/images/cja/cja12.png "Create and Analyze Reports in CJA")

## Data Views in Adobe Customer Journey Analytics

Enables you to determine how to interpret data from a connection

![Adobe](/images/cja/cja13.png "Create and Analyze Reports in CJA")

## Data Views | Capabilities

    - Change a component from a Metric to a Dimension and vice versa.
    - Create multiple metrics with different attribution models or with different look back windows.
    - Edit the ID of a component
    - Specify a friendly name that appears in Analysis Workspace
    - Tag a component
    - Create a metric or a dimension based on the values in the schema field

## Reporting Components

Components are the building blocks of reports

![Adobe](/images/cja/cja14.png "Create and Analyze Reports in CJA")

## Filters in Adobe Customer Journey Analytics

Filters help you to:

    - Identify subsets of visitors based on characteristics or website interactions.
    - Provide codified audience insights that you can build for your specific needs.

Filter containers

    - Based on a Person, Session, and Event level hierarchy using a nested container model.
    - The nested containers define person attributes and actions based on rules between the containers and within each container

![Adobe](/images/cja/cja15.png "Create and Analyze Reports in CJA")

## Calculated Metrics in Adobe Customer Journey Analytics

    - Custom metrics that you can create from the existing metrics.
    - Offer a highly flexible way of building, managing, and curating metrics.
    - Help drill the data to specific requirements

Using Calculated Metrics, you can:

    - Create metrics that are derived at report run time, without having to change the implementation.
    - Dig deeper into data across the existing metrics.
    - Incorporate statistical functions to help you better describe your data

## Create Reports on Multi- Channel Sales

Scenario: You are an analyst at We.Retail which is a retail company.We.Retail needs to study the campaign performance and the product purchase details on different channels for the last two months. You will create campaigns and purchase performance reports to help company visualize the status and analyze the next steps.

![Adobe](/images/cja/cja16.png "Create and Analyze Reports in CJA")

## Create Mobile Dashboard for Quick Analysis of Cross Channel Data

Scenario: You are an analyst atWe.Retail, the retail company and you want to create a mobile dashboard that helps you quickly analyze data per your convenient time and space. To achieve this, you will create a mobile dashboard that includes cross-channel traffic and conversion data.

![Adobe](/images/cja/cja17.png "Create and Analyze Reports in CJA")

## Create a Project Folder

Create a project folder, where you can group all related projects

![Adobe](/images/cja/cja18.png "Create and Analyze Reports in CJA")

## Create a Project

Create a project in the folder created by you

![Adobe](/images/cja/cja19.png "Create and Analyze Reports in CJA")

## Use Case

You are an analyst at the retail company LUMA. Your goal for the new fiscal year is to improve online and in-store sales by 10% and enhance customer support to inflate brand loyalty. To achieve this, you need to study the cross-channel traffic and conversion data. You also need to understand the call center data. To generate these data:

First, you create reports on:

     - Total calls and call satisfaction across channels.
     - Cross channel customer journey.
     - Multi-channel purchase and return funnel.
     - Online purchase and mobile app returns

Second, you dig deeper for targeted data by creating the following comparative analysis reports:

     - Cross channel average order value.
     - Multi-channel conversion rate.
     - Multi-channel daily average visits.
     - Combo charts on mobile app revenue.
     - Multi-touch attribution analysis on campaign channel orders.

Third, you decide to:

     - Create returning people revenue Histogram and publish audience to Adobe Experience Platform.
     - Share the project.

## Class Use Case Connection Datasets

![Adobe](/images/cja/cja20.png "Create and Analyze Reports in CJA")

## Components Created Through Dataview

![Adobe](/images/cja/cja21.png "Create and Analyze Reports in CJA")

## Create Reports on Cross Channel Calls and Call Satisfaction

Scenario: You will conduct data analysis by creating cross channel call center interaction report. You want to understand the various reasons that lead to call center calls across channels and the call satisfaction rate between 1– 10

![Adobe](/images/cja/cja22.png "Create and Analyze Reports in CJA")

## Create a Report on Cross Channel Customer Journey

Scenario: With call reason and call satisfaction data, you now want to understand the customer journey that spanned from different channels to call center and then from call center to web.

![Adobe](/images/cja/cja23.png "Create and Analyze Reports in CJA")

## Create a Fallout Report on Multi- Channel Purchase and Returns

Scenario: You now want to understand the fallout rate on purchases and returns across channels.

![Adobe](/images/cja/cja24.png "Create and Analyze Reports in CJA")

## Create a Report on Online Purchase and Mobile App Returns

Scenario: You now want to generate data on the purchases made online and then returned through mobile app in the last 90 days.

![Adobe](/images/cja/cja25.png "Create and Analyze Reports in CJA")

## Use Case

You are an analyst at the retail company LUMA. Your goal for the new fiscal year is to improve on line and in- store sales by 10% and enhance customer support to inflate brand loyalty. To achieve this, you need to study the cross-channel traffic and conversion data. You also need to understand the call center data. To generate these data:

First, you create reports on:

    - Total calls and call satisfaction across channels.
    - Cross channel customer journey.
    - Multi-channel purchase and return funnel
    - Online purchase and mobile app returns

Second, you dig deeper for targeted data by creating the following comparative analysis reports:

    - Cross channel average order value.
    - Multi-channel conversion rate.
    - Multi-channel daily average visits
    - Combo charts on mobile app revenue
    - Multi-touch attribution analysis on campaign channel orders

Third, you decide to:

    - Create returning people revenue Histogram and publish audience to Adobe Experience Platform.
    - Share the project.

## Create a Report on Cross Channel Average Order Value

Scenario: You want to dig deeper and create comparative analysis reports. You will start by creating cross channel average order value report.

![Adobe](/images/cja/cja26.png "Create and Analyze Reports in CJA")

## Create a Report on Multi- Channel Conversion Rate

Scenario: You now want to create a conversion rate report to identify the conversion rate across channels. You will generate these details over a product category.

![Adobe](/images/cja/cja27.png "Create and Analyze Reports in CJA")

## Create a Report on Multi- Channel Daily Average Visits

Scenario: Now that you have identified the conversion rate across channels, you want to capture data on the daily average visits across channels.

![Adobe](/images/cja/cja28.png "Create and Analyze Reports in CJA")

## Create Combo Reports to Analyze Mobile App Revenue Details

Scenario: You understand that most visits are coming from the Mobile App channel. You now want to understand the mobile app revenue details. Todo this, you will create combo charts to study Revenue,Average weekly purchases,and Monthly product views and orders all coming throughMobile App.

![Adobe](/images/cja/cja29.png "Create and Analyze Reports in CJA")

## Create a Multi- Touch Attribution Report to Analyze Orders ThroughCampaign Channels

Scenario: You now want to create the attribution data dashboards for cross-over and multi- touch data analysis. You decide to create metric settings and dataview settings attribution analysis dashboard.

![Adobe](/images/cja/cja30.png "Create and Analyze Reports in CJA")

## Use Case

You are an analyst at the retail company LUMA. Your goal for the new fiscal year is to improve online and in- store sales by 10% and enhance customer support to inflate brand loyalty. To achieve this, you need to study the cross-channel traffic and conversion data. You also need to understand the call center data. To generate these data:

First, you create reports on:

    - Total calls and call satisfaction across channels.
    - Cross channel customer journey.
    - Multi-channel purchase and return funnel.
    - Online purchase and mobile app returns.

Second, you dig deeper for targeted data by creating the following comparative analysis reports:

    - Cross channel average order value.
    - Multi-channel conversion rate.
    - Combo charts on mobile app revenue.
    - Multi-touch attribution analysis on campaign channel orders.

Third, you decide to:

    - Create returning people revenue Histogram and publish audience to Adobe Experience Platform.
    - Share the project.

## Audience Publishing in Adobe Customer Journey Analytics

![Adobe](/images/cja/cja31.png "Create and Analyze Reports in CJA")

## Project Sharing

1. Share the project with other Analysis Workspace users in the organization.
2. Any curation applied is reflected when recipients open the project.

Project Roles:

    - Edit – Can edit and save changes to the project.
    - Duplicate – Can copy the project but cannot edit.
    - View – Can only view the project.

## Create a Histogram for Returning People Revenue and Share Audience to Experience Platform

Scenario: You will create a report on the returning people revenue generation. You will also publish the audiences who made a purchase of maximum $100 to Adobe Experience Platform.

![Adobe](/images/cja/cja32.png "Create and Analyze Reports in CJA")

## Share the Project

Scenario: You have now completed creating the project that includes your cross-channel and multi-touch analytical data. You now want to share the project.

There are two options to share the project:

    - Share with Workspace users
    - Share with anyone

## Use Case

You are an analyst at the retail company LUMA. Your goal for the new fiscal year is to improve on lineand in- store sales by 10% and enhance customer support to inflate brand loyalty. To achieve this, you need to study the cross-channel traffic and conversion data. You also need to understand the call center data. To generate these data:

First, you create reports on:

    - Total calls and call satisfaction across channels.
    - Cross channel customer journey
    - Multi-channel purchase and return funnel
    - Online purchase and mobile app returns

Second, you dig deeper for targeted data by creating the following comparative analysis reports:

    - Cross channel average order value.
    - Multi-channel conversion rate.
    - Multi-channel daily average visits.
    - Combo charts on mobile app revenue.
    - Multi-touch attribution analysis on campaign channel orders.

Third, you decide to:

    - Create returning people revenue Histogram and publish audience to Adobe Experience Platform.
    - Share the project.

You have completed your journey as an analyst by creating various reports. Based on your analysis and experience, what are the possible suggestions that you can provide to your company to achieve the targeted goals?

Company goals:

    - Improve online and in store revenue by 10%.
    - Enhance customer support.


Create and Analyze Reports Using Adobe Customer Journey Analytics

Create and Analyze Reports in CJA


## Introduction

Experience Businesses focus on building a clear understanding of their customers’ needs and interests.
Data-driven customer insights play a critical role in creating meaningful experiences. Customer Journey
Analytics (CJA) powered by Adobe Experience Platform is an application service that enables you to
deliver context and clarity to the complex multi-channel customer journey. You can generate actionable
insights on the customer data and remove pain points from the customer conversion process to deliver
exceptional experiences. You can also learn about issues and take corrective actions to predict and
influence their future engagements.

## Objectives

After completing this module, you will be able to:

- Explain the features and benefits of CJA
- Describe the architecture of CJA powered by Experience Platform
- Explain the CJA terminologies
- Review Experience Platform schemas & datasets
- Explain connections in CJA
- Create and configure a connection
- Create a data view
- Prepare data for analysis reports in CJA
- Create basic and advanced reports

## Customer Journey Analytics: Overview

CJA is an application service built on top of Experience Platform that:

- Brings analysis workspace capabilities in Experience Platform
- Contextualizes and visualizes data
- Stitches online and offline (cross-channel) data together to create analysis reports
- Delivers context and clarity to the complex multi-channel customer journey

## Key CJA Use Cases

- View and analyze data sequentially, spanning multiple channels
- Democratize data access that will enable you to make business decisions with data-derived insights
- Use data science to unlock deep insights and analysis
- Visualize and interact with your datasets by using ad-hoc reporting
- View non-web data
- Apply greater control over your data customization

## CJA vs Adobe Analytics

CJA expands the scope of Analytics by offering easy-to-use cross-channel capabilities and removing the
limitations in the previous versions of Adobe Analytics. Some notable improvements are unlimited
variables and events, unlimited unique values: Experience Platform is not constrained to any unique
limitations, such as the 500k unique values in traditional report suites, ability to alter historical data and
obtain cross-report-suite data.

## Customer Journey Analytics Architecture

---

![Adobe](/images/customer-journey-analytics-img1.PNG "Customer Journey Analytics Architecture")

## CJA Integration with Experience Platform

---

![Adobe](/images/customer-journey-analytics-img2.PNG "CJA Integration with Experience Platform")

The data flow process from Experience Platform to CJA occurs in the following steps:

- Data Collection: Data can come through Adobe’s SDK, Adobe Solutions, third party tools andother technologies
- Data Ingestion: Data is received through streaming and batch files
- Data Persistence: Received data are organized into common set of schemas and cataloged in the Experience Data Model (XDM). XDM performs data governance and enables the Experience Platform’s Data Lake to act like a broker of raw data when it is requested.
- Data Analysis and Visualization

  - CJA integrates with Experience Platform through data connections
  - When CJA accesses the Data Lake, it pulls a copy of the dataset and the optimizes the data to a customization pattern
  - CJA uses a columnar format, stores data by columns rather than by rows, which enables fast access, filtration, and queries for analytical query processing
  - Data onboarded into Experience Platform is batched and uploaded every 15 minutes

- When a new data connection is setup with CJA, the processing under normal load takes less than 1hr. But for unusually high volume of data flow, it could take up to 24 hrs.

## CJA vs Adobe Analytics Terminologies

| CJA         |                              Description                               |                 Adobe Analytics Comparison |
| ----------- | :--------------------------------------------------------------------: | -----------------------------------------: |
| Data Schema |              Integrity constraints imposed on a database               |                                        N/A |
| Dataset     |         A schema and batches of data: Event Profile & Look up          | N/A, Click data, Attribute, Classification |
| Connection  |            Link between Experience Platform dataset and CJA            |                                        N/A |
| Data View   |                        User defined set of data                        |                Virtual Report Suites (VRS) |
| Components  | Building blocks of reports: Dimensions, Metrics, Filters, Date Ranges  |                       Components, Curation |
| Filter      | Subset of individuals based on characteristics: Person, Session, Event |               Segment Visitor, Visits, Hit |

## Data Schema

- A set of formulas called integrity constraints that are imposed by a database.
- A blueprint on how a database is to be constructed.

## Datasets

- An email, CRM, POS data, comes straight out Adobe Analytics on your website.
- A dataset consists of a schema and the batches of the data.
  The different types of dataset that are compatible with CJA are:
- Event: Represents the data that comes into the website by using any kind of interaction. Can be a sequence event such as clickstream data that has a timestamp, customer ID
- Profile: Is applied to your visitors or users or customers in the event data. Basically uploading CRM data about your customer and the data become customer attributes in Adobe Analytics
- Lookup: Is used to lookup values or keys found in either your event or profile data

## Connection

- Establishes a link between Experience Platform datasets and CJA.
- Enables you to integrate multiple datasets for your analysis and reporting

## Data View

- The user-defined set of data based on the dataset configuration with Experience Platform.
- A data view consists of multiple types of datasets for a holistic view of our customers.
- You can create different data views from the same connections with different settings.

## Components

- Components are the building block of reports
- The different types of components are:
  - Dimensions
  - Metrics
  - Filters
  - Data Ranges

## Filters:

- A subset of individuals based on the characteristics of individuals or dimensions we use to define the subset of users.
- Filters are called Segments in Adobe Analytics.
- Filters have different containers such as person, session, and event.


Services Powered by Experience Platform an Overview

Customer Journey Analytics CJA


The intent of this step is to review the datasets with their corresponding schemas to be used in CJA.
This will enable you to understand the underlying data structure of the datasets prior to the creation
and configuration of CJA connections, data views and customer journey visualization.

Perform the following tasks:

1. Connect to the Experience Platform User Interface (UI)
2. Review the following datasets and their corresponding schemas to understand the data and the structure:

| Dataset                             | Schema                                     |
| ----------------------------------- | ------------------------------------------ |
| AEP Demo - Website Interactions     | Website Interactions Schema                |
| AEP Demo - Website Registration     | AEP Demo - Website Registration Schema     |
| AEP Demo - Call Center Interactions | AEP Demo - Call Center Interactions Schema |

## Task 1: Connect to the Experience Platform UI

1. Navigate to https://experience.adobe.com/. The Adobe Experience Cloud page opens.
2. Click Experience Platform. The Adobe Experience Platform page opens.
3. Verify the instance link on the upper right. For example, Global Platform US.
4. Navigate to Data Management > Datasets. The Datasets page opens.
5. Click the Browse tab, if not open already. The available datasets appear.
6. Type Website in the Search box to filter the list of the datasets. The list will include AEP Demo Website Registrations and AEP Demo Website Interaction, as shown:
   ![Adobe](/images/customer-journey-analytics-img3.PNG "Connect to the Experience Platform UI")
7. Select the AEP Demo Website Interactions dataset. The AEP Demo Website Interactions Schema panel appears on the right.
8. Click the link below Schema. The AEP Demo Website Interactions Schema pop up appears.
9. Click AEP Demo Website Interactions Schema below the Schema name section in the pop up. The Schemas > AEP Demo Website Interactions Schema page opens on a separate tab.
   ![Adobe](/images/customer-journey-analytics-img4.PNG "Connect to the Experience Platform UI")
10. In the Structure section, expand adlsplatform<region> object schema, where <region> refers the region for which the instance is provisioned. For example, adlsplatformus. The available subobjects appear..
11. Expand the identification sub-object. The identification object displays the strings that include crmid, ecid, and emailId, as shown:
    ![Adobe](/images/customer-journey-analytics-img5.PNG "Connect to the Experience Platform UI")
12. Click Schemas on the upper left to return to the Schemas page.
13. Navigate to Data Management > Datasets. The Datasets page opens.
14. Click the Browse tab, if not open already. The available datasets appear.
15. Type Website in the Search box to filter the list of the datasets. The list of datasets appear.
16. Select the AEP Demo Website Registrations Data dataset. The AEP Demo Website Registrations Schema panel appears on the right.
17. Click the link below Schema. The AEP Demo Website Registrations Schema pop up appears.
18. Click AEP Demo Websites Registrations Schema below the Schema name section in the pop up. The Schemas > AEP Demo Websites Registrations Schema page opens on a separate tab.
19. In the Structure section, expand adlsplatform region object schema, where region refers the region for which the instance is provisioned. For example, adlsplatformus. The available subobjects appear.
20. Expand the identification sub-object. The identification object displays the strings, as shown:
    ![Adobe](/images/customer-journey-analytics-img6.PNG "Connect to the Experience Platform UI")
21. Click Schemas on the upper left to return to the Schemas page.
22. Navigate to Data Management > Datasets. The Datasets page opens.
23. Click the Browse tab. The available datasets appear.
24. Type Call center in the Search box. The dataset based on the filter appears.
25. Select the AEP Demo Call Center Interaction dataset. The AEP Demo Luma Telco Call Center Interactions Schema panel appears on the right.
26. Click the link below Schema. The AEP Demo Luma Telco Call Center Interactions Schema pop up appears.
27. Click AEP Demo Call Center Interactions Schema below the Schema name section in the pop up. The Schemas > AEP Demo Luma Telco Call Center Interactions Schema page opens on a separate tab.
28. In the Structure section, expand adlsplatform<region> object schema, where <region> refers the region for which the instance is provisioned. For example, adlsplatformus. The available subobjects appear.
29. Expand the identification sub-object. The identification object displays the strings, as shown:
    ![Adobe](/images/customer-journey-analytics-img7.PNG "Connect to the Experience Platform UI")

- Notice that the common strings in three schemas are:
  - ecid
  - emailId
  - mobilenr (primary)


Review Experience Platform schemas and datasets

Customer Journey Analytics Workflow


Connections enable you to create a link between Experience Platform datasets and CJA. You can
integrate multiple datasets for analysis and reporting.

The creation of connections is step 3 in CJA Workflow (in the diagram below) and it is how you pull the
data out of AEP into CJA Workspace in order to perform cross-channel analysis of your data.

## How to Create CJA Connections

Connection creation required permissions:
To create a CJA Connection, you need the following permissions in Adobe Admin Console:

## Adobe Experience Platform:

- Data Modeling: View Schemas, Manage Schemas
- Data Management: View Datasets, Manage Datasets
- Data Ingestion: Manage Sources

## Customer Journey Analytics:

- Product Admin Access

## Steps for Creating CJA Connection:

The steps involved in creating a connection are:

1. Select the sandbox in Experience Platform that contains the dataset in which you want to create a connection
2. Create a connection in CJA
3. Add the dataset to the connection
4. Provide the Connection Naming and Streaming details
5. Stitch together selected datasets in a Connection
6. Save the Connection configuration

## CJA Connection Setting Details:

Connection Setting UI
![Adobe](/images/customer-journey-analytics-img8.PNG "CJA Connections")
| Setting | Description |
|--------------|-----------|
| Connection name | Enter a unique name for the connection.|
| Connection description | Describe the purpose of this connection. |
| Sandbox | Choose a sandbox in Experience Platform that contains the dataset/s to which you want to create a connection |
| Sandbox | Once you have selected the sandbox, the left rail shows all the datasets in that sandbox that you can pull from. |
| Enable rolling data window | This checkbox, if checked, lets you define CJA data retention as a rolling window in months (1 month, 3 months, 6 months, etc.), at the connection level |
| Enable rolling data window | Data retention is based on event dataset timestamps and applies to event datasets only. No rolling data window setting exists for profile or lookup datasets since there are no applicable timestamps. However, if your connection includes any profile or lookup datasets (besides one or more event datasets), that data will be retained for the same time period |
| Enable rolling data window | The main benefit is that you store or report only on data that is applicable and useful and delete older data that is no longer useful. It helps you stay under your contract limits and reduces the risk of overage cost. |
| Enable rolling data window | If you leave the default (unchecked), the retention period will be superseded by the Adobe Experience Platform data retention setting. If you have 25 months’ worth of data in Experience Platform, CJA will get 25 months of data through backfill. If you deleted 10 of those months in Platform, CJA would retain the remaining 15 months. |
| Add datasets | Add datasets if no datasets appear in your dataset listing.|
| Dataset name | Select one or more dataset(s) you want to pull into Customer Journey Analytics and click Add.|
| Add datasets | Note: If you have a lot of datasets to choose from, you can search for the right one(s) using the Search datasets search bar above the list of datasets..|
| Last updated | For event datasets only, this setting is automatically set to the default timestamp field from event-based schemas in Experience Platform. “N/A” means that this dataset contains no data.|
| Schema | This is the schema based on which the dataset was created in Adobe Experience Platform. |
| Dataset type | For each dataset that you added to this connection, Customer Journey Analytics automatically sets the dataset type based on the data coming in.|
| Dataset type | There are 3 different dataset types: Event data, Profile data, and Lookup data. |
| Person ID | Select a person ID from the dropdown list of available identities. These identities were defined in the dataset schema in the Experience Platform. See below for information on how to use Identity Map as a Person ID. |
| Person ID | Note: If there are no person IDs to choose from, that means one or more person IDs have not been defined in the schema. |
| Key | Note: For lookup datasets only (such as \_id). |
| Matching Key | For lookup datasets only (such as \_id). |
| Import new data | Set to On or Off. |
| Backfill data | You can request to backfill the data in a dataset based on event timestamps. |
| Backfill data | For example, you can request to backfill the last 7 days’ worth of data, configure the right Person ID and test your connection for correct configuration. If everything looks good, you can backfill all the remaining data with ease. |
| Backfill data | In addition, you can enable the import of new data by dataset. For example, you can enable the import of new data for lookup data only. |
| Backfill status | Indicates whether any backfill data is processing. |

## Linking datasets in CJA Connections

Datasets in a CJA Connection are linked using the Person ID. The Person ID can be mapped in an
identity field defined in a schema associated with a dataset or identity Map if there are person IDs to
choose from. The Identity Map is available for any dataset that uses a schema based on the
ExperienceEvent XDM class. Identity Map allows you to upload key -> value pairs. The keys are identity
namespaces, and the value is a structure that holds the identity value.

When you select identity map as person ID in a CJA Connection, then you need two additional
configuration, Use Primary ID Namespace and Namespace if you do not use the Primary ID
Namespace.

## Identity Map Edge Cases

| Option                                   | No IDs are present in Identity Map | No IDs are marked as primary                                                                           | Multiple IDs are marked as primary                                                                                                                                                                    | Single ID is marked as primary                                                                        | Invalid namespace with an ID marked as primary                                                                                                                                                                                                         |
| ---------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Use Primary ID Namespace checked         | The row is dropped by CJA          | The row is dropped by CJA, as no primary ID is specified                                               | All IDs marked as primary, under all namespaces, are extracted into a list. They are then alphabetically sorted with this new sorting, the first namespace with its first ID is used as the Person ID | The single ID marked as primary is used as the Person ID                                              | Even though the namespace may be invalid not present in AEP, CJA will use the primary ID under that namespace as the Person ID                                                                                                                         |
| Specific Identity Map namespace selected | The row is dropped by CJA          | All IDs under the selected namespace are extracted into a list and the first is used as the Person ID. | All IDs under the selected namespace are extracted into a list and the first is used as the Person ID.                                                                                                | All IDs under the selected namespace are extracted into a list and the first is used as the Person ID | All IDs under the selected namespace are extracted into a list and the first is used as the Person ID. (Only a valid namespace can be selected at Connection creation time, so it is not possible for an invalid namespace/ID to be used as Person ID) |

## Connection Manager

The Connection Manager is the latest update to the Connection experience which adds two important
capabilities within the Connection Details page. It allows you to:

- Check the status of your connection’s datasets and of the ingestion process. This status check lets you know when your data is available so that you can go into Analysis Workspace and start analysis.
- Identify any data discrepancies due to misconfiguration. Are you missing any rows? If yes, what rows are missing and why? Did you misconfigure connections and cause missing data in CJA?

Specifically, with your Connection Manager, you can:

- View all your connections at a glance, including the owner, the sandbox, and when they were created and modified.
- View all datasets in a connection.
- Check the status of a connection.
- Delete a connection.
- Rename a connection.
- Create a data view from a connection.

## Connection Details Page

![Adobe](/images/customer-journey-analytics-img9.PNG "Connection Details Page")


Connections enable you to create a link between Platform datasets and CJA

Customer Journey CJA Connections


1. Create and build a library.
2. Install the Adobe Experience Platform Debugger Extension.
3. Validate the Luma Website configuration using Adobe Experience Platform Debugger and Preview Dataset.

## Create and Build a Library

1. Ensure the Adobe Experience Platform Data Collection page with your tag property is open.
2. On the left pane, click Publishing Flow, as shown:
   ![Adobe](/images/websdk/websdk56.png "Web SDK - Build, Validate, and Deploy")
   A page displaying various stages of publishing opens
3. Click Add Library, as shown:
   ![Adobe](/images/websdk/websdk57.png "Web SDK - Build, Validate, and Deploy")
   The Create Library page opens.
4. Perform the following actions, as shown:
   - In the Name box, type Luma Website Library.
   - From the Environment dropdown, select Development (development).
     ![Adobe](/images/websdk/websdk58.png "Web SDK - Build, Validate, and Deploy")
5. In the RESOURCE CHANGES section, click Add All Changed Resources, as shown:
   ![Adobe](/images/websdk/websdk59.png "Web SDK - Build, Validate, and Deploy")
6. Click Save & Build to Development.
   Your library is saved and appears under Development, as shown:
   ![Adobe](/images/websdk/websdk60.png "Web SDK - Build, Validate, and Deploy")
   The green dot next to the library name indicates that the build is successful.

## Install the Adobe Experience Platform Debugger Extension

1. Open a new browser window, type Adobe Experience Platform Debugger in the Search bar and press Enter.
2. Click the first Adobe Experience Platform Debugger link, as shown:
   ![Adobe](/images/websdk/websdk61.png "Web SDK - Build, Validate, and Deploy")
   The chrome web store page opens.
3. Click Add to Chrome on the top right, as shown:
   ![Adobe](/images/websdk/websdk62.png "Web SDK - Build, Validate, and Deploy")
   The Add Adobe Experience Platform Debugger confirmation dialog opens.
4. Click Add extension. The extension is added to your Chrome browser.
5. Click the Extensions icon in the browser, as shown:
   ![Adobe](/images/websdk/websdk63.png "Web SDK - Build, Validate, and Deploy")
   The Extensions dialog opens.
6. Click the Pin icon, as shown, to pin the extension to the browser:
   ![Adobe](/images/websdk/websdk64.png "Web SDK - Build, Validate, and Deploy")
   The Adobe Experience Platform Debugger extension icon appears in the browser bar, as shown:
   ![Adobe](/images/websdk/websdk65.png "Web SDK - Build, Validate, and Deploy")
7. Right- click the Adobe Experience Platform extension and click Manage Extensions, as shown:
   ![Adobe](/images/websdk/websdk66.png "Web SDK - Build, Validate, and Deploy")
   The Extensions page opens.
8. Scroll down the page, turn on the Allow in Incognito toggle key, as shown:
   ![Adobe](/images/websdk/websdk67.png "Web SDK - Build, Validate, and Deploy")
9. Close the browser tab.


Build, Validate, and Deploy DataCollection Library in Data Collect.

Web SDK - Build, Validate, and Deploy


1. Create an E vent Forwarding property
2. Configure a Data stream
3. Configure Event Forwarding to send event data to a non- Adobe application

## Create an Event Forwarding Property

1. Open the Adobe Experience Platform Data Collection > Tag Properties browser tab.
2. Click Tag Properties, as shown:
   ![Adobe](/images/websdk/websdk48.png "Web SDK - Event Forwarding")
   The Tag Properties page opens.
3. On the left pane, under DATA COLLECTION, click Event Forwarding, as shown:
   ![Adobe](/images/websdk/websdk49.png "Web SDK - Event Forwarding")
   The Event Forwarding Propertied page opens.
4. Click New Property. The Create Property page opens.
5. In the Name box, type Luma Server- Side Web SDK
   ![Adobe](/images/websdk/websdk50.png "Web SDK - Event Forwarding")
6. Verify whether the property that you created is listed on the Event Forwarding Properties page.

## Configure a Data stream

For Event Forwarding to use the data you send to the Edge network, you must link the newly createdE vent Forwarding property to the same Data stream used to send data to Adobe solutions.

1. Ensure the Event Forwarding Properties page is open.
2. On the left pane, under DATA COLLECTION, click Data streams, as shown:
   ![Adobe](/images/websdk/websdk51.png "Web SDK - Event Forwarding")
   The Data streams page opens.
3. In the Search box, type Luma Website Data stream and pressEnter. Your Data stream appears in the filter.
4. Click Luma Website Data stream as shown:
   ![Adobe](/images/websdk/websdk52.png "Web SDK - Event Forwarding")
   The Luma Website Data stream - page opens.
5. Click Add Service, as shown:
   ![Adobe](/images/websdk/websdk53.png "Web SDK - Event Forwarding")
   The Add Service page opens.
6. Perform the following actions, as shown:

   - From the Service (required) dropdown, select Event Forwarding.
   - Ensure the Enabled toggle key is set to Turned on.
   - From the Property dropdown, select Luma <date> Server - Side - WebSDK.
   - From the Environment dropdown, select Development.
     ![Adobe](/images/websdk/websdk54.png "Web SDK - Event Forwarding")

   Note: Repeat the steps 5 and 6 for Staging and nd Production Data streams when you are ready to promote the changes through the publishing flow.

7. Click Save. Your Data stream page opens.
8. Notice that the Event Forwarding service is added to your Data stream, as shown:
   ![Adobe](/images/websdk/websdk55.png "Web SDK - Event Forwarding")


Configure Event Forwarding in Adobe Data Collect.

Web SDK - Event Forwarding


1. Create the GlobalPageTop rule.
2. Create the productView rule.
3. Create the checkOut rule.
4. Create the addToCart rule

## Create the GlobalPageTop Rule

1. Ensure the Adobe Experience Platform Data Collection page with your tag property is open.
2. On the left pane, click Rules, as shown:
   ![Adobe](/images/websdk/websdk40.png "Web SDK - Create Rules in Data Collection")
   As you have not created any rule yet, a help video opens.
3. Click Create New Rule. The Create Rule page opens.
4. In the Name box, type GlobalPageTop.
5. In the IF section, under EVENTS, where you will define the event that triggers the rule, click Add, as shown:
   ![Adobe](/images/websdk/websdk41.png "Web SDK - Create Rules in Data Collection")
   The Event Configuration dialog opens.
6. From the Extension dropdown, ensure Core is selected.
7. From the Event Type dropdown, select Library Loaded (Page Top).
8. Click Keep Changes. The Create Rule page opens.
9. In the THEN section, under ACTIONS, where you will define the rule action, click Add, as shown:
   ![Adobe](/images/websdk/websdk42.png "Web SDK - Create Rules in Data Collection")
   The Action Configuration dialog opens.
10. From the Extension dropdown, select Adobe Experience Platform Web SDK.
11. From the Action Type dropdown, select Send event.
12. Configure Adobe Experience Platform Data Collection Module 3: Data Collection: Tag ConfigurationPage 57Adobe Copyright Protected12. Expand the ADVANCED OPTIONS section and ensure the Wait to run next action checkbox is selected.
13. On the right, in the Type box, type web.webpagedetails.pageViews.
14. To update the XDM data box, click the database icon. The Select Data Element dialog opens.
15. Click the pageView D ata Element that you created earlier and click Select. The Action Configuration dialog is updated.
16. Click Keep Changes. The Create Rule page opens.
17. Click Save. The rule is saved and listed on the Rules page.

## Create the productView Rule

1. Ensure the Rules page is open and click Add Rule. The Create Rule page opens
2. In the Name box, type productView.
3. In the IF section, under EVENTS, click Add. The Event Configuration dialog opens.
4. From the Extension dropdown, select Adobe Client Data Layer.
5. From the Event Type dropdown, select Data Pushed. The Data Pushed section opens.
6. On the Data Pushed section, under Listen to, select Specific Event, as shown:
   ![Adobe](/images/websdk/websdk43.png "Web SDK - Create Rules in Data Collection")
7. In the Event / Key to register for box, type productView.
8. Under the Time scope section, ensure All is selected.
9. Click Keep Changes. The Create Rule page opens.
10. In the THEN section, under ACTIONS, click Add. The Action Configuration dialog opens.
11. From the Extension dropdown, select Adobe Experience Platform Web SDK.
12. From the Action Type dropdown, select Send Event.
13. In the ADVANCED OPTIONS section, ensure the Wait to run next action checkbox is selected.
14. In the Type box, type commerce.productViews.
15. To update the XDM data box, click the database icon. The Select Data Element dialog opens.
16. Select the productView Data Element that you created earlier and click Select. The ActionConfiguration dialog is updated and should look similar to below screenshot:
    ![Adobe](/images/websdk/websdk44.png "Web SDK - Create Rules in Data Collection")
17. Click Keep Changes. The Create Rule page opens.
18. Click Save. The rule is saved and listed on the Rules page.

## Create the checkOut Rule

1. Ensure the Rules page is open and click Add Rule. The Create Rule page opens.
2. In the Name box, type checkOut.
3. In the IF section, under EVENTS, click Add. The Event Configuration dialog opens.
4. From the Extension dropdown, select Adobe Client Data Layer.
5. From the Event Type dropdown, select Data Pushed. The Data Pushed section opens.
6. On the Data Pushed section, under Listen to, select Specific Event.
7. In the Event / Key to register for box, type checkOut.
8. Under Time scope, ensure All is selected.
9. Click Keep Changes. The Create Rule page opens.
10. In the THEN section, under ACTIONS, click Add. The Action Configuration dialog opens.
11. From the Extension dropdown, select Adobe Experience Platform Web SDK.
12. From the Action Type dropdown, select Send event.
13. In the ADVANCED OPTIONS section, ensure the Wait to run next action check box is selected.
14. In the Type box, type commerce.purchases.
15. To update the XDM data box, click the database icon. The Select Data Element dialog opens.
16. Click the checkOut Data Element that you created earlier and click Select. The Action Configuration dialog is updated and should look similar to the below screenshot:
    ![Adobe](/images/websdk/websdk45.png "Web SDK - Create Rules in Data Collection")
17. Click Keep Changes. The Create Rule page opens.
18. Click Save. The rule is saved and listed on the Rules page.

## Create the addToCart Rule

1. Ensure the Rules page is open and click Add Rule. The Create Rule page opens.
2. In the Name box, type addToCart.
3. In the IF section, under EVENTS, click Add. The Event Configuration dialog opens.
4. From the Extension dropdown, select Adobe Client Data Layer.
5. From the Event Type dropdown, select Data Pushed. The Data Pushed section opens.
6. On the Data Pushed section, under Listen to, select Specific Event.
7. In the Event / Key to register for box, type addToCart.
8. Under Time scope, click All. The Event Configuration dialog appears.
9. Click Keep Changes. The Create Rule page opens.
10. In the THEN section, under ACTIONS, click Add. The Action Configuration page opens.
11. From the Extension dropdown, select Adobe Experience Platform Web SDK.
12. From the Action Type dropdown, select Send event.
13. In the ADVANCED OPTIONS section, ensure the Wait to run next action checkbox is selected.
14. In the Type box, type commerce.productListAdds.
15. To update the XDM data box, click the database icon. The Select Data Element dialog opens.
16. Click the addToCart Data Element that you created earlier and click Select. The Action Configuration dialog is updated and should look similar to the below screenshot:
    ![Adobe](/images/websdk/websdk46.png "Web SDK - Create Rules in Data Collection")
17. Click Keep Changes. The Create Rule page opens.
18. Click Save. The rule is saved and listed on the Rules page.


Web SDK -  Create Rules in Data Collection for a Luma Website.

Create Rules in Data Collection


Create Audiences and Activate Destinations in Adobe Real- TimeCustomer Data PlatformModule 2: Create Audiences and Activate Destinations in Real- TimeCDP B2C EditionPage 46Adobe Copyright ProtectedActivity 2.9: Compose Audience by Adding an Existing AudienceScenario: In this activity, you will compose an audience by adding an existing audience. Further, you will narrow down the target audience by excluding the bronze members and selecting only the top 1000profiles.

1. Ensure you are o n the CUSTOMER > Audiences page.
2. Click Create audience. The Create Audience dialog opens.
3. Ensure Compose audience is selected and click Create. The Create audience page opens.
4. Click the Audience block on the canvas. The Audience pane opens on the right.
5. Click Add audience. The Add audience dialog opens.
6. Select one of the audiences you created in a previous activity. For Example, Sequential Audience.
7. Click Add. The audience is added.
8. Click the + icon below the Audience block, as shown. Additional actions such as Exclude, Enrich, Rank,and Split are displayed.
   ![Adobe](/images/segments/segments40.png "Compose Audience by Adding an Existing Audience")
9. Click Exclude. The Exclude pane opens on the right.
10. From the Type dropdown, s elect Exclude using attribute. You can also exclude audiences using the audiences you have created already
11. To define the exclusion rule, click the pencil icon under the Attribute field. The Select a profile attribute dialog opens.
12. Click the loyaltyDetails folder. The folder opens with two attributes, level and points.
13. Select the level attribute and click Select. The Attribute box in the Exclude pane is updated.
14. In the Excluded values box, type bronze. The Exclude pane should now look, as shown:
    ![Adobe](/images/segments/segments40.png "Compose Audience by Adding an Existing Audience")
15. In the canvas, notice that the Estimated record output has changed. In this example, it is 42k in theAudience block and 31k in the Exclude block as you excluded the bronze members, as shown. The numbers in your sandbox may vary.
    ![Adobe](/images/segments/segments42.png "Compose Audience by Adding an Existing Audience")
16. Click the + icon below the Exclude block and click Rank. The Rank pane opens on the right.
17. Under Attribute, click the pencil icon. The Select a profile attribute dialog opens.
18. Click the loyaltyDetails folder. The folder opens.
19. Select the points attribute and click Select. The Attribute field in the Rank pane is updated.
20. Click the Rank By dropdown and select Descending order.
21. Turn on the Add profile limit key. T his option enables you to specify the maximum number of profiles to be included in the composition.
22. In the Included profiles box, type 1000. In the canvas, notice that the Estimated record output in theRank block changed to 1k. This is because, you specified the loyalty points ranking attribute and restricted the profile limit to 1000. Now, you can target the top 1000 profiles.
23. Click the Save audience block. The Save pane opens on the right.
24. In the Save name box, replace the existing name with a suitable name such as Top1000Profiles.
25. Click the icon next to the default Composition name at the top of the page. The Composition properties dialog opens.
26. In the Title box, provide a suitable name such as Exclude Bronze Members.
27. Click Save. The title is updated.
28. Click Publish. The audience is published.


Compose Audience by Adding an Existing in Adobe Real - Time Customer Data.

Compose Audience Adobe Real Time


## Perform the following tasks

- Create an audience for customers who purchased products in the past
- Create an audience of male customers who added a product to the website cart
- Create an audience of male customers who added a product using mobile phones
- Create a new audience of male purchasers, whose product add method was website or mobile phones
- Activate the audience to a destination

## Create an Audience for Customers Who Purchased Products in the Past

1. Click Create audience. The Create audience dialog opens.
2. Ensure the Build rule audience creation method is selected and click Create. The rule builder opens.
3. On the left pane, on the Events tab, type Purchase ID in the search box. The Purchase ID events type is displayed.
4. Drag and drop Purchase ID onto the rule builder.
5. Under Event Rules, click the equals drop - down arrow and select exists.
6. In the Name box on the right pane, type a suitable name such as Your initials Purchasers.
7. Click Save to save the audience.
   ![Adobe](/images/segments/segments43.png "Create an Audience from Existing Audiences")

## Create an Audience of Male Customers Who Added a Product to the Web site Cart

1. Click Create audience. The Create audience dialog opens.
2. Ensure the Build rule audience creation method is selected and click Create. The rule builder is displayed.
3. On the left pane, ensure you are on the Attribute tab and navigate to XDM Individual Profile > Adlsplatform Individual recognition > Core.
4. Drag and drop gender onto the rule builder. The gender attribute is added.
5. From the Select or type options drop-down menu, select male.
6. On the left pane, click the Events tab.
7. Under EVENT TYPES, look for Product List Adds and drag and drop into the rule builder.
8. Ensure Product List Adds you added now is selected. The Event Rules section is displayed at the bottom.
9. On the left pane, navigate to XDM ExperienceEvent > Product list items and drag and drop Product add method onto the Add event field section.
10. From the Select or type options drop-down menu, select Web.
11. In the Name box on the right pane, enter a suitable name such as Male - Product add method web.
12. Click Save to save the audience.
    ![Adobe](/images/segments/segments44.png "Create an Audience from Existing Audiences")

    ![Adobe](/images/segments/segments45.png "Create an Audience from Existing Audiences")

## Create an Audience of Male Customers Who Added a Product Using Mobile Phones

1. Click Create audience. The Create audience dialog opens.
2. Ensure the Build rule audience creation method is selected and click Create. The rule builder is displayed.
3. On the left pane, ensure you are on the Attribute tab and navigate to XDM Individual Profile > Adlsplatform Individual recognition > Core
4. Drag and drop gender onto the rule builder. The gender attribute is added.
5. From the Select or type options drop-down menu, select male.
6. On the left pane, click the Events tab.
7. Under EVENT TYPES, look for Product List Adds and drag and drop into the rule builder.
8. Ensure Product List Adds you added now is selected. The Event Rules section is displayed at the bottom.
9. On the left pane, navigate to XDM ExperienceEvent > Product list items and drag and drop Product add method onto the Add event field section.
10. From the Select or type options drop-down menu, select Mobile.
11. In the Name box on the right pane, enter a suitable name such as Male - Product add method Mobile.
12. Click Save to save the audience.
    ![Adobe](/images/segments/segments44.png "Create an Audience from Existing Audiences")

    ![Adobe](/images/segments/segments46.png "Create an Audience from Existing Audiences")

## Create a New Audience of Male Purchasers Whose Product Add Method was Website or Mobile Phones

1. Click Create audience. The Create audience dialog opens.
2. Ensure the Build rule audience creation method is selected and click Create. The rule builder opens.
3. On the left pane, click the Audiences tab. The available audiences are displayed.
4. Click Experience Platform. The audiences you have created so far are displayed.
5. Drag the Purchasers segment you created in Task 1 onto the rule builder. The attributes are updated.
6. Click the ellipsis on the right, as shown, and click Add Container. A container is added with an Add operation.
7. From the left pane, drag and drop the Male - Product add method web audience you created in Task 2 onto the Add attribute or audience section. The audience is updated in the container and a message indicating that the container must include at least 2 rules is displayed on the right.
8. From the left pane, drag and drop the Male - Product add method Mobile audience you created in T ask 3 below the audience you added in the previous step.
9. Click the And operator. Notice that it changes to Or. Now, you have created an audience of customers who have made a purchase and whose product add method is mobile or web. Similarly, you can create other audiences using the audiences you have already created, which saves you time and effort.
10. On the right pane, in the Name box, type a name for the audience. For example, Project.
11. Click Save to save the audience.
    ![Adobe](/images/segments/segments47.png "Create an Audience from Existing Audiences")

## Activate the Audience to a Destination

1. Ensure you are on the Browse tab of the Audiences page and click the your Project segment you created earlier. The your initials Project segment page opens.
2. In the Activated destination section, click Activate to destination. The Activate destination page opens.
3. In the Select destination section, select the Amazon S3 destination you configured earlier and click Next. The Scheduling section is displayed.
4. In the Scheduling section, under SCHEDULE, click Create Schedule, a shown. The Scheduling your segment name dialog opens.
5. Under Frequency, ensure Once is selected.
6. Select a future date from the calendar.
7. Click Create. The schedule is updated.
8. Click Next. The Select attributes section is displayed.
9. Retain the default attributes and click Next. The Review section is displayed.
10. Review the details and click Finish.


Create an Audience from Existing Audiences in Real - Time Customer Data.

Create an Audience in Adobe Real - Time


1. Ensure the Adobe Experience Platform home page is open.
2. Scroll down the left pane, under DATA COLLECTION, click Data streams. The Data streams page opens.
3. Click New Data stream, as shown.

   ![Adobe](/images/websdk/websdk.png "WebSdk - Configure Data stream")
   The New Data Stream wizard opens.

4. Perform the following, as shown:

   - In the Name box, type Luma Website Datastream - < today’s date> in mm-dd-yyyy format.
   - In the Description box, type Luma Website Datastream for Experience Platform Service.
   - From the Event Schema dropdown, select AEP Demo Website Interactions Schema
     ![Adobe](/images/websdk/websdk2.png "WebSdk - Configure Data stream")

   Note: The Save and Add Mapping option helps map, transform, and validate data to and from XDM. When configuring a Platform- enabled Data stream, you can use data preparation capabilities to map your source data to XDM when sending it to the PlatformEdge Network. For now, you can skip the Save and Add Mapping option for data preparation.

5. Click Save. The Add services page opens.
6. Click Add Service, as shown:
   ![Adobe](/images/websdk/websdk3.png "WebSdk - Configure Data stream")
   The Add Service page opens.
7. Perform the following, as shown:
   - From the Service (required) dropdown, select Adobe Experience Platform.
   - From the Event Dataset (required) dropdown, select AEP Demo – Website Interactions.
   - From the Profile Dataset dropdown, select AEP Demo – Website Registrations.
   - Ensure the Edge Segmentation checkbox is selected.
     ![Adobe](/images/websdk/websdk4.png "WebSdk - Configure Data stream")
8. Click Save to save the configuration with Experience Platform service enabled. The summary page of the Data stream configuration opens, as shown:
   ![Adobe](/images/websdk/websdk5.png "WebSdk - Configure Data stream")


Create and Configure Data stream with Experience Platform Service.

Web SDK - Configure Data Stream


1. Create Data Elements using Experience Cloud ID and Data Layer extension.
2. Create and configure Data Elements with Web SDK Extension.

## Create Data Elements using Experience Cloud ID and Data Layer Extensions

We will create Data Elements within your tag property that map to data collection variables from your website. You will map the D ata Elements to an XDM object that you created in the previous activity.

To create Data Elements within your tag property:

1. Ensure the Adobe Experience Platform Data Collection page is open.
2. On the left pane, click Data Elements, as shown:
   ![Adobe](/images/websdk/websdk21.png "Create and Configure Data Elements")
   As you have not created any data element yet, a help video opens.
3. Click Create New Data Element. The Create Data Element dialog opens.
4. To create an Execution Context ID (ECID) data element, perform the following actions:

   - In the Name box, type ECID.
   - From the Extension dropdown, select Experience Cloud ID Service.
   - From the Data Element Type dropdown, select ECID.
   - From the Storage Duration dropdown, select Visitor.
     The ECID data element configuration should look similar to the below screenshot, as shown:
     ![Adobe](/images/websdk/websdk22.png "Create and Configure Data Elements")

5. Click Save. The ECID data element is created and listed on the Data Elements tab, as shown:
   ![Adobe](/images/websdk/websdk23.png "Create and Configure Data Elements")

To create an Email data element, perform the following:

6. Click Add Data Element. The Create Data Element dialog opens.
7. Perform the following actions:

   - In the Name box, type Email.
   - From the Extension dropdown, select Adobe Client Data Layer.
   - From the Data Element Type dropdown, select Data Layer Computed State.
   - From the Storage Duration dropdown, select Visitor.
   - On the right, in the [Optional] Path box, type data.email.

     The Email data element configuration should look similar to the below screenshot, as shown:
     ![Adobe](/images/websdk/websdk24.png "Create and Configure Data Elements")

8. Click Save. The Email data element is created and listed on the Data Elements tab.
9. Similarly, perform steps 6 through 9 and create the following additional data elements using the information provided in the tables below:

   - pageName
   - pageType
   - pageSection
   - interactionType
   - productName
   - productCategory
   - productInteraction
   - productPrice
   - totalCart
   - productSku
   - quantity

## pageName

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | pageName                  |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.pageName             |

The pageName Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk25.png "Create and Configure Data Elements")

## pageType

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | pageType                  |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.pageType             |

The pageType Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk26.png "Create and Configure Data Elements")

## pageSection

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | pageSection               |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.pageSection          |

The pageSection Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk27.png "Create and Configure Data Elements")

## interactionType

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | interactionType           |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.interactionType      |

The interactionType Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk28.png "Create and Configure Data Elements")

## productName

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | productName               |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productName          |

The productName Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk29.png "Create and Configure Data Elements")

## productCategory

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | productCategory           |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productCategory      |

The productCategory Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk30.png "Create and Configure Data Elements")

## productInteraction

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | productInteraction        |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productInteraction   |

The productInteraction Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk31.png "Create and Configure Data Elements")

## productPrice

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | productPrice              |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productPrice         |

The productPrice Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk32.png "Create and Configure Data Elements")

## totalCart

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | totalCart                 |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.totalCart            |

The totalCart Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk33.png "Create and Configure Data Elements")

## productSKU

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | productSKU                |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productSKU           |

The productSKU Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk34.png "Create and Configure Data Elements")

## quantity

| Element           | Values                    |
| ----------------- | ------------------------- |
| Name              | quantity                  |
| Extension         | Adobe Client Data Layer   |
| Data Element Type | Data Layer Computed State |
| Storage Duration  | PageView                  |
| Path              | data.productSKU           |

The quantity Data Element configuration should look similar to the below screenshot:
![Adobe](/images/websdk/websdk35.png "Create and Configure Data Elements")

## Create Data Elements with Web SDK extension

- addToCat
- checkOut
- pageView
- productView

To create the addToCart Data Element:

1. Ensure the Data Elements page is open.
2. Click Add Data Element. The Create Data Element dialog opens.
3. Perform the following actions:
   - In the Name box, type addToCart.
   - From the Extension dropdown, select Adobe Experience Platform Web SDK.
   - From the Data Element Type dropdown, select XDM object.
   - On the right, from the Sandbox dropdown, select your assigned sandbox. The PRODUCTION Prod (vA7) sandbox is used for demonstration purpose.
   - From the Schema dropdown, select AEP Demo - Website Interactions Schema.
   - Click identityMap from the XDM Object, as shown:
     ![Adobe](/images/websdk/websdk36.png "Create and Configure Data Elements")
   - Click the database icon, as shown:
     ![Adobe](/images/websdk/websdk37.png "Create and Configure Data Elements")
     The Select Data Element dialog opens.
   - Select ECID Data Element that you created in the previous activity and click Select, as shown:
     ![Adobe](/images/websdk/websdk38.png "Create and Configure Data Elements")
     The Value box appears on the right.
   - Click productListItems array in the XDM Object. The Product list items with Population strategy options appear on the right, as shown:
     ![Adobe](/images/websdk/websdk39.png "Create and Configure Data Elements")
   - Click Provide entire array. The Data element box appears.
   - Type %cart.fix% in the Data element box.
   - Expand web > webInteraction and click name. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Select the pageName Data Element that you created in the previous activity and click Select.The Value box is now updated.
   - Expand web > webPageDetails and click name. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Select the pageName Data Element that you created in the previous activity and click Select.The Value box is now updated.
   - Under webPageDetails, click siteSection. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Select the pageSection Data Element that you created in the previous activity and click Select. The Value box is now updated.
4. Click Save. The Data Element is created and listed on the Data Elements tab.

To create the checkOut Data Element:

5. Ensure the Data Elements tab is open and click Add Data Element. The Create Data Element dialog opens.
6. Perform the following actions:
   - In the Name box, type checkOut.
   - From the Extension dropdown, select Adobe Experience Platform Web SDK.
   - From the Data Element Type dropdown, select XDM object.
   - On the right, from the Sandbox dropdown, select your assigned sandbox.
   - From the Schema dropdown, select AEP Demo - Website Interactions Schema.
   - Click identityMap from the XDM Object.
   - Click the database icon. The Select Data Element dialog opens.
   - Select ECID Data Element that you created in the previous activity and click Select. The Value box appears on the right.
   - Expand commerce > checkouts and click value. The Value box appears on the right.
   - Type 1 in the Value box.
   - Click order > currencyCode. The Value box appears on the right.
   - In the Value box, type USD.
   - Under order, click priceTotal. The Value box appears on the right
   - Click the database icon. The Select Data Element dialog opens.
   - Click the totalCart Data Element that you created in the previous activity and click Select. TheValue box is now updated.
   - Click eventType. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Click the interactionType D ata Element that you created in the previous activity and clickSelect. The Value box is now updated.
   - Click productListItems. The Population strategy options appear on the right.
   - Click Provide entire array. The Data Element box appears.
   - In the Data Element box, type %cart.fix%.
   - Expand web > webInteraction and click name. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
   - Expand web > webPageDetails and click name. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
   - Expand web > webPageDetails and click name. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
   - Under webPageDetails, click siteSection. The Value box appears on the right.
   - Click the database icon. The Select Data Element dialog opens.
   - Click the pageSection Data Element that you created in the previous activity and click Select.
     The Value box is now updated.
7. Click Save. The Data Element is created and listed on the Data Elements tab.

To create the pageView Data Element: 8. Ensure the Data Elements tab is open and click Add Data Element. The Create Data Element dialog opens. 9. Perform the following actions:

- In the Name box, type pageView.
- From the Extension dropdown, select Adobe Experience Platform Web SDK.
- From the Data Element Type dropdown, select XDM object.
- On the right, from the Sandbox dropdown, select your assigned sandbox.
- From the Schema dropdown, select AEP Demo - Website Interactions Schema.
- Click identityMap from the XDM Object.
- Click the database icon. The Select Data Element dialog opens.
- Select ECID Data Element that you created in the previous activity and click Select. The Value box appears on the right.
- Click productListItems. The Population strategy options appear on the right.
- Click Provide entire array. The Data Element box appears.
- I n the Data Element box, t ype %cart.fix%.
- Expand web > webInteraction and click name. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
- Expand web > webPageDetails and click name. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageName D ata Element that you created in the previous activity and click Select. The Value box is now updated
- Under webPageDetails, click siteSection. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageSection Data Element that you created in the previous activity and click Select.The Value box is now updated.

10. Click Save. The Data Element is created and listed on the Data Elements tab.

To create the productView Data Element:

11. Ensure the Data Elements tab is open and click Add Data Element. The Create Data Element dialog opens.
12. Perform the following actions:

- In the Name box, type productView.
- Select Adobe Experience Platform Web SDK from the Extension dropdown.
- Select XDM object from the Data Element Type dropdown.
- On the right, from the Sandbox dropdown, select your assigned sandbox. In this step,PRODUCTION Prod (vA7) is used for demonstration purpose.
- From the Schema dropdown, select AEP Demo - Website Interactions Schema.
- Click identityMap from the XDM Object.
- Click the database icon. The Select Data Element dialog opens.
- Select ECID Data Element that you created in the previous activity and click Select. The Value box appears on the right.
- Click productListItems. The Population strategy options appear on the right.
- Click Provide entire array. The Data Element box appears.
- In the Data Element box, t ype %cart.fix%.
- Expand commerce > productViews and click id. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Select the productSku D ata Element that you created in the previous activity and click Select. he Value box is now updated.
- Under commerce > productViews, click value. The Value box appears on the right.
- In the Value box, t ype 1.
- Click eventType. The Value box appears on the right.
- In the Value box, type commerce.productViews.
- Expand web > webInteraction and click name. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
- Expand web > webPageDetails and click name. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageName Data Element that you created in the previous activity and click Select. TheValue box is now updated.
- Under webPageDetails, click siteSection. The Value box appears on the right.
- Click the database icon. The Select Data Element dialog opens.
- Click the pageSection Data Element that you created in the previous activity and click Select.The Value box is now updated.

13. Click Save. The Data Element is created and listed on the Data Elements tab.


Create and Configure Data Elements for Luma Website.

Web SDK - Configure Data Elements


1. Go to the Adobe Experience Platform Data Collection browser tab.
2. On the left pane, under DATA COLLECTION, click Tags, as shown:

   ![Adobe](/images/websdk/websdk6.png "Web SDK - Create a Tag Property")
   The Tag Properties page opens

3. Click New Property. The Create Property dialog opens.
4. Perform the following, as shown:

   - In the Name box, type Luma Web Property.
   - In the Domains box, type enablementadobe.com.
     ![Adobe](/images/websdk/websdk7.png "Web SDK - Create a Tag Property")

5. Expand the ADVANCED OPTIONS section:

   - Ensure the Run rule components in sequence checkbox is selected.
   - Ensure the Return an empty string for missing data elements checkbox is not selected for this training.

   Note: You can s elect Return an empty string for missing data elements checkbox if you want undefined values to be empty rather than the default values.

6. Click Save. The new property is created and listed in the Tag Properties page.
7. In the Search box, type Luma Website Property. The property that you created in the previous activity appears in the filter list, as shown:
   ![Adobe](/images/websdk/websdk8.png "Web SDK - Create a Tag Property")


Web SDK - Create a Tag Property for a Luma Website.

Web SDK - Create a Tag Property


1. Install and configure Experience Platform Web SDK Extension.
2. Install and configure Experience Cloud ID Service Extension.
3. Install and configure Adobe Client Data Layer Extension.

## Install and Configure Experience Platform Web SDK Extension

Note: Ensure you have created a Data stream and a T ag property for Luma Website

1. Ensure the Tag Properties page with the property that you created in the previous activity is open.
2. Click Luma Website Property, as shown:
   ![Adobe](/images/websdk/websdk9.png "Web SDK - Configure Extensions")
   The Luma Website Property page opens.
3. On the left pane, click Extensions. The installed extensions are displayed.
4. Notice that the Core extension is installed by default, as shown:
   ![Adobe](/images/websdk/websdk10.png "Web SDK - Configure Extensions")
5. Click the Catalog tab, as shown:
   ![Adobe](/images/websdk/websdk11.png "Web SDK - Configure Extensions")
   All available extensions are displayed.
6. In the Search box, type Adobe Experience Platform and press Enter. The Adobe ExperiencePlatform Web SDK appears.
7. Click Install, as shown:
   ![Adobe](/images/websdk/websdk12.png "Web SDK - Configure Extensions")
   The Install Extension page opens. You can configure the extension in this page.
8. Scroll down the page and look for Data Streams.
9. From the Production Environment dropdown, select PRODUCTION Prod (VA7), as shown:
   ![Adobe](/images/websdk/websdk13.png "Web SDK - Configure Extensions")
10. From the Select a data stream dropdown, select the data stream that you created in previous activity,for example, Luma Website Data stream , as shown:
    ![Adobe](/images/websdk/websdk14.png "Web SDK - Configure Extensions")
11. From the Staging Environment and Development Environment dropdowns, select PRODUCTIONProd (VA7).
12. For the Select a data stream dropdowns under Staging Environment and DevelopmentEnvironment, select the Data stream that you created in previous activity, for example, Luma Website Data stream.
13. Click Save. The extension is configured and installed, and is now available on the Installed tab, as shown:
    ![Adobe](/images/websdk/websdk15.png "Web SDK - Configure Extensions")

    Note: You will use this extension in subsequent steps.

## Install the Experience Cloud ID Service

The Experience Cloud ID Service extension enables you to integrate the Experience Cloud ID Service with the property you created earlier. You will use this service for creating and storing unique and persistent identifiers for your website visitors.

1. Ensure the Installed tab of Luma Web Property.
2. Click Catalog to access the available extensions.
3. In the Search box, type Experience Cloud and press Enter. The Experience Cloud ID Service appears.
4. Click Install, as shown:
   ![Adobe](/images/websdk/websdk15.png "Web SDK - Configure Extensions")
   The Install Extension page opens.
5. Notice that the Marketing Cloud Organization ID box is updated by default. The ID is a 24- character,alphanumeric string followed by @AdobeOrg.

   Note: If the Marketing Cloud Organization ID box is not auto populated and if you do not know this ID, you need to contact the Customer Care.

6. Leave the Exclude specific paths box blank.

   Note: If you update Exclude specific paths, the Experience Cloud ID does not load when the URL matches any of the specified paths.

7. Leave the Opt In and Variables sections blank

   Note: In the Variables dropdown, you can set the name- value pairs as the ExperienceCloud ID instance properties, when required.

8. Click Save. The Experience Cloud ID Service extension will now be available on the Installed tab, as shown:
   ![Adobe](/images/websdk/websdk17.png "Web SDK - Configure Extensions")

## Install the Adobe Client Data layer Extension

1. Ensure the Installed tab of Luma Web Property is open.
2. Click Catalog to access the available extensions.
3. In the Search box, type Data Layer and press Enter. The Adobe Client Data Layer appears.
4. Click Install, as shown:
   ![Adobe](/images/websdk/websdk18.png "Web SDK - Configure Extensions")
   The Install Extension page opens.
5. In the Data Layer name box, replace adobeDataLayer with digitalData from Luma Website, as shown:
   ![Adobe](/images/websdk/websdk19.png "Web SDK - Configure Extensions")
6. Click Save. The extension is installed and will now be available on the Installed tab, as shown:
   ![Adobe](/images/websdk/websdk20.png "Web SDK - Configure Extensions")


Install and Configure Extensions in Data Collect.

Web SDK - Configure Extensions


Scenario: In this activity, you will compose audience by building a new custom rule using attributes and events. You will create an audience of customers who are 45 years or older and viewed a product on your website, so that you can create an email campaign specifically for them

1. Ensure you are on the CUSTOMER > Audiences page.
2. Click Create audience. The Create Audience dialog opens.
3. Ensure Compose audience is selected and click Create. The Create audience page opens.
4. Click the Audience block on the canvas, as shown. The Audience pane opens on the right. Notice that there are options to add existing audience or create a new custom rule using attributes and events. In this activity, you will build a new rule.
   ![Adobe](/images/segments/segments15.png "Compose Audience by Building Rule")
5. On the right pane, click Build rule. The Custom rule canvas opens.
6. On the left pane, ensure you are on the Attributes tab and navigate to XDM Individual Profile > Adlsplatform Individual recognition > Core.
7. Drag and drop age onto the canvas. The age attribute is added.
8. Click the equals drop- down arrow and select is greater than or equal to.
9. In the Enter a Number box, type 45. The age attribute should now look, as shown
   ![Adobe](/images/segments/segments16.png "Compose Audience by Building Rule")
10. On the left pane, click the Events tab.
11. Under EVENTS TYPE, search for Product Views and drag and drop it onto the rule builder. TheEvents section of the rule builder is updated, as shown:
    ![Adobe](/images/segments/segments17.png "Compose Audience by Building Rule")
12. On the right pane, click Refresh estimate to view an estimate of the qualified profiles.
13. Click Save to save the audience. The Composition page opens. Notice that the Audience block is updated, a shown, with information such as the method used to create audience (in this case, Rule builder), attributes and events used to build the rule, and estimated record output.
    ![Adobe](/images/segments/segments18.png "Compose Audience by Building Rule")
14. Click the Save audience tile. A pane opens on the right.
15. Replace the default title with a suitable name. For example, Email Campaign.
16. Click the icon next to the default Composition name, as shown. The Composition properties dialog opens.
    ![Adobe](/images/segments/segments19.png "Compose Audience by Building Rule")
17. In the Title box, replace the default name with a suitable name. For example, Audience Composition_Today’sDate.
18. Click Save. The title is updated.
19. Click Publish. The audience is published.
20. Click CUSTOMER > Audiences. The Audiences page opens.
21. Click the Composition tab. A list of audience appears with the audience you created. You can click the ellipsis next to the audience name to access additional actions such as Duplicate, Manage access, and Delete.


Compose Audience by Building a Custom Rule in Adobe Real - Time Customer Data.

Compose Audience by Building Rule


1. Create a third - party export restriction data usage police.
2. Apply data governance labels.

## Create a Third- party Export Restriction Data Usage Police

1. On the left navigation menu, go to PRIVACY > Policies. The Policies page opens.
2. Click Browse tab, if not already open. Existing policies are listed, as shown.
   ![Adobe](/images/policies/configure-policies.png "Configure Policies")
3. Observe that there is an out- of - the- box policy 3rd party export restriction associated with theC2 label and the marketing action Export to Third Party. For this activity, you will create a copy of this policy.

   Note: In real scenario, you will be selecting this default policy and enable the toggle key on the right pane to apply the policy

4. Click Create policy. The create policy wizard opens for you to combine multiple labels and marketing action restrictions and create a data usage policy.
5. The Choose type of policy dialog opens.
6. Select Data governance policy, as shown:
   ![Adobe](/images/policies/configure-policies2.png "Configure Policies")

   Note: You can create data governance policies with the Experience Platform licenses. Consent policies are only available for organizations that have purchased Adobe Healthcare Shield orAdobe Privacy & Security Shield.

7. Click Continue. The Configure page for Create policy opens.
8. Under Policy details section, in the Name box, type Third party export restriction. In this example, the name is John-Third party export restriction.
9. Optionally, provide a relevant description.
10. From the Name column, select C2, the label for No third- party export, as shown:
    ![Adobe](/images/policies/configure-policies3.png "Configure Policies")
11. Click Next. The Select marketing actions page opens.
12. From the MARKETING ACTIONS column, select Export to Third Party, as shown
    ![Adobe](/images/policies/configure-policies4.png "Configure Policies")
13. Click Next. The policy Review page opens, as shown:
    ![Adobe](/images/policies/configure-policies5.png "Configure Policies")
14. Verify the details and click Finish.
    The new policy is created and added to the Policies list, as shown:
    ![Adobe](/images/policies/configure-policies6.png "Configure Policies")
15. Observe that in the CREATED BY column, your name is displayed. Rest of the default policies show Adobe.
    Note: All data usage policies (including core policies provided by Adobe) are disabled by default. For an individual policy to be considered for enforcement, you must manually enable that policy.
16. From the NAME column, click the row of the policy created by you. Properties of the policy are displayed on the right pane.
17. Click the Disabled key to enable the selected policy, as shown
    ![Adobe](/images/policies/configure-policies7.png "Configure Policies")
    Note: Enforcement of governance policies is a key component to the framework.Enforcement happens downstream when data is activated and sent out of ExperiencePlatform, specifically with the Real-Time Customer Data Platform.

## Apply Data Governance L abel

1. On the left navigation menu, go to DATA MANAGEMENT > Schemas. The Schemas page opens.
2. Find and click the attributes- based schema you created in Module 2 Activity 2.1. The schema page opens. In this example, the John- Individual Profiles Schema is opened, as shown:
   ![Adobe](/images/policies/configure-policies8.png "Configure Policies")
3. Click Labels. The schema fields that can be associated with labels are listed. You can apply labels to individual fields in a schema.
4. From the FIELD NAME column, select the fields that you need to apply with the data usage policy. In this example, the field Mobilenr is selected, as shown:
   ![Adobe](/images/policies/configure-policies9.png "Configure Policies")

   Note: You can use the Search option to look for a specific field from the lengthy list of fields.

5. On the right pane, click Apply access and data governance labels. The Apply access and data governance labels page opens.
6. In the NAME column of the listed labels section, scroll down to C2 label and select it, as shown:
   ![Adobe](/images/policies/configure-policies10.png "Configure Policies")
   The data governance label is applied on the selected field of the schema. Observe that this is the label that restricts the data usage for third- party exports

   Note: There are many out- of -the-box labels. You can create your own by using the Create label button. The three main types of labels are: Contract labels, Identity labels, and Sensitive labels that correspond to common reasons data might be restricted. Each label has aFRIENDLY NAME and a NAME, which is an abbreviation of the type and the number. For example, the C2 label is for No third- party export.

7. Click Save to return to the schema’s Labels page. The applied data governance label is displayed in the schema’s Labels page, as shown:
   ![Adobe](/images/policies/configure-policies11.png "Configure Policies")

   When you create audiences downstream to connect with third-party applications, you will seethe impact of the data usage policy you have applied on the XDM schema fields.


Configure Data Usage Policies in Experience Platform.

Configure Data Usage Policies


Scenario: Your organization wants you to create an audience that captures customers who are not a part of the company’s loyalty program but have made purchases of less than or equal to $1000 in the past.This audience will be targeted later inform them about the benefits of joining the loyalty program.

1. Click CUSTOMER > Audiences. The Audiences page opens.
2. Click Create audience to create a new audience. The Create audience dialog opens.
3. Ensure the Build rule creation method is selected and click Create.
4. On the left pane, ensure you are on the Attributes tab and navigate to XDM Individual Profile > Adlsplatform loyaltyDetails.
5. Drag level onto the rule builder. The loyalty level attribute is added.
6. Click the equals drop - down arrow and select does not exist. This indicates the target customer is nota part of the loyalty program. The Attributes section should look, as shown:
   ![Adobe](/images/segments/segments28.png "Create an Aggregation Audience")
7. On the left pane, under Fields, click the Events tab.
8. Under EVENT TYPES, look for Purchases and drag and drop it onto the rule builder. The Purchases event type is added.
9. C lick Purchases. The Event Rules section opens.
10. Under Event Rules, click the ellipsis, as shown, and select Aggregate.
    ![Adobe](/images/segments/segments29.png "Create an Aggregation Audience")
11. Click the Sum drop-down arrow and select Average.
12. Click the Select an attribute box, as shown, to select the required attribute. A dialog opens.
    ![Adobe](/images/segments/segments30.png "Create an Aggregation Audience")
13. Click XDM ExperienceEvent > Commerce > Order > Price Total. The attribute is added.
14. Click the equals drop- down arrow and select is less than or equal to.
15. In the enter a number box, type 1000. The Event Rules section should look, as shown:
    ![Adobe](/images/segments/segments31.png "Create an Aggregation Audience")
16. On the right pane, click Refresh estimate to view the qualified profiles.
17. In the Name box, provide a name for the audience such as Aggregate Audience_Today’sDate.
18. Click Save and close to save the audience. The audience summary opens.


Create an Aggregation Audience in Adobe Real - Time Customer Data.

Create an Aggregation Audience


1. Ensure you are logged in to platform.adobe.com. The Home page opens.
2. On the top navigation bar, at the top- right of the Home page, verify that the correct training region is selected.
3. Ensure you are on the right sandbox provided to you by your Instructor.
4. On the left navigation pane, click CUSTOMER > Audiences. The Audiences page opens.
5. Click Create audience, as shown, to create a new audience. The Create audience dialog opens.
   ![Adobe](/images/segments/segment.png "Create an Audience Based on Attributes")
6. Select the Build rule creation method, as shown, and click Create.
   ![Adobe](/images/segments/segment2.png "Create an Audience Based on Attributes")
7. On the left pane, under Fields, ensure you are on the Attributes tab.
8. Under BROWSE ATTRIBUTES, click XDM Individual Profile. The available attributes for the XDMIndividual Profile attribute are listed, as shown:
   ![Adobe](/images/segments/segment3.png "Create an Audience Based on Attributes")
9. Click the Person folder. The fields under the Person folder are listed, as shown:
   ![Adobe](/images/segments/segment4.png "Create an Audience Based on Attributes")
10. Select Birth date (YYYY-MM- DD) and drag it onto the rule builder canvas, as shown:
    ![Adobe](/images/segments/segment5.png "Create an Audience Based on Attributes")
11. In the Attributes section, click the Today drop-down arrow and click Rolling range from the list that appears, as shown. A box appears pre populated with 1.
    ![Adobe](/images/segments/segment6.png "Create an Audience Based on Attributes")
12. Click the Day(s) drop- down arrow and select Years.
13. Click the to link. A box appears pre populated with 2.
14. Enter 18 in the first box and 45 in the second (to) box. The attributes should now look, as show:
    ![Adobe](/images/segments/segment7.png "Create an Audience Based on Attributes")
15. To include the customers who have email ID, ensure you are on the Fields > Attributes tab on the left pane.
16. Click XDM Individual Profile. The available attributes are listed.
17. Click Adlsplatform folder. For example, Adlsplatformapac.
    ![Adobe](/images/segments/segment8.png "Create an Audience Based on Attributes")
18. Navigate to Identification > core. All available fields under core are listed.
19. Drag email under the existing rule in the rule builder. While dragging, ensure the blue line appears under the existing, as shown.

    Note that the AND operator appears connecting the email rule with birth date.
    ![Adobe](/images/segments/segments9.png "Create an Audience Based on Attributes")

20. Click the equals operator drop-down arrow next to email and select exists. The rule builder should now look, as shown:
    ![Adobe](/images/segments/segments10.png "Create an Audience Based on Attributes")
21. On the left menu, type loyalty in the search box. The fields associated with loyalty are listed. Being a custom field, the loyalty program data will be in a folder named with your tenant ID. For example, Adlsplatformapac.
22. Click the loyaltyDetails folder. The available options are listed.
23. Drag the level field onto the rule builder, under the email attribute you added earlier.
24. Click the select or type options drop- down arrow and click gold from the list. The gold status is added. The segment is now defined with the customers who have an emailID, are aged 18 – 45 years,and are a part of the gold membership, as shown:
    ![Adobe](/images/segments/segments11.png "Create an Audience Based on Attributes")

    Note: You can select multiple values for loyalty status. As it is referenced as an enumeration in the XDM schema, the values are available from the Select or type options drop - down menu.

25. In the Audience properties pane on the right, click Refresh estimate. The estimated profile count is displayed. I t may take a few seconds to refresh the estimate
26. In the Name box, type Segment18 – 45GoldEmail.
27. Under Evaluation method, ensure Streaming is selected. If not, click the drop- down arrow and selectStreaming.
28. Click Save. A success message appears indicating the segment is saved.
29. Click Save and close. A summary of the newly created segment is displayed.

Note: T he summary also lists the sample profiles. You can click the profile IDs to view the details.

30. Click Edit audience on the profile summary page.
31. On the Audience properties pane, click Code view to view the segment definition for API. The code view is displayed, as shown schema.
    ![Adobe](/images/segments/segments12.png "Create an Audience Based on Attributes")
32. Click Cancel to return to the newly created segment page. Stay on this page for the next activity.


Create Audiences and Activate Destinations in Adobe Real - Time Customer Data.

Create an Audience Based on Attributes


1. On the left navigation pane, click CUSTOMER > Audiences. The Audiences page opens.
2. Click Create audience. The Create audience dialog opens.
3. Select Build rule as the audience creation method and click Create. The rule builder canvas opens.
4. Click the Events tab on the left pane. The existing events and event types are displayed, as shown.
   ![Adobe](/images/segments/segments13.png "Create an Audience Based Event")
5. Under the BROWSE CLASSES section, click XDM ExperienceEvent. All sub folders under the event are displayed.
6. In the XDM ExperienceEvent menu, scroll down and click the Product List items folder. The available fields under Product list items are displayed.
7. From the left pane, drag the Name field onto the rule builder canvas. The Name field is added.
8. Retain equals as the operator.
9. In the select or type options box, type Ray- Ban Rb2132 New Wayfarer Sunglasses and press Enter,as shown:
   ![Adobe](/images/segments/segments14.png "Create an Audience Based Event")
   The product name Ray- Ban Rb2132 New Wayfarer Sunglasses is added to the rule.
10. Click Refresh estimate on the right pane to view the number of profiles who qualify.
11. To name this segment, in the Name box on the right pane, type Sunglasses Event Segment.
12. Click Save and close. The segment is created, and the segment summary page is displayed.


Create Audiences Based on Events in Adobe Real - Time Customer Data.

Create an Audience Based on Events


1. Create and configure a dataset from the attributes XDM schema in experience platform.
2. Create a dataset from the events XDM schema in experience platform.

## Create and Configure a Dataset from the Attributes XDM Schema in Experience Platform

1. On the left menu, under DATA MANAGEMENT node, click Datasets. The Datasets page opens.
2. Click Browse, if not opened already to view the list of existing datasets.

Note: Depending upon your past activities the list varies. You may not see the exact list as given in the screenshots.

3. On the top - right, click Create dataset, as shown, to create a new dataset.
   ![Adobe](/images/datasets/create-individual-dataset.png "Create Datasets")
   The Create dataset page opens.
4. To create a dataset from the new XDM schema that you have created, click Create dataset from schema, as shown:
   ![Adobe](/images/datasets/create-individual-dataset2.png "Create Datasets")
   The Create dataset from schema page opens.
5. Under the Select schema section’s NAME column, click <your first name> - Individual ProfilesSchema. In this example, it is John - Individual Profiles Schema, as shown:
   ![Adobe](/images/datasets/create-individual-dataset3.png "Create Datasets")
6. After selecting the schema, click Next to continue. The Configure dataset section opens.
7. Configure the dataset. In the Name section, type <your first name> - Individual Profiles. In this example, it is John – Individual Profiles.
   Optionally, you can add a description to the dataset.
8. Click Finish to complete the dataset configuration.
   ![Adobe](/images/datasets/create-individual-dataset4.png "Create Datasets")
   The new dataset page opens under the Datasets section.
9. On the right pane, click the Profile key, to enable the new dataset to be part of ExperiencePlatform's Real- time Customer Profile. A confirmation dialog appears

   Note: If the schema on which the dataset is created is not enabled for Profile,then you will not be able to enable the Profile for the dataset as well.

10. Click Enable. The dataset is enabled for Real- time Customer Profile in Experience Platform, as shown:
    ![Adobe](/images/datasets/create-individual-dataset5.png "Create Datasets")
11. Scroll down to ADD DATA section and click Choose files, as shown:
    ![Adobe](/images/datasets/create-individual-dataset6.png "Create Datasets")
    The files explorer window opens.
12. Select the relevant regional CRMData_usa.json file provided to you by your Instructor. In this example, CRMData_usa.json is selected, as shown:
    ![Adobe](/images/datasets/create-individual-dataset7.png "Create Datasets")
13. Click Open to complete the data file selection and return to the Datasets page. The selected file is being uploaded to the dataset name Individual Profiles. The Datasets page is updated with the data processing activity. After the data loading is complete, the dataset is updated with the newly added data from the selected CRMData file, as shown:
    ![Adobe](/images/datasets/create-individual-dataset8.png "Create Datasets")
    Note: Data loading may take a minute or two. Refresh the page to view the Success status on the Dataset activity page


Create and Configure Datasets for Individual Profile in Experience Platform.

Create and Configure Dataset


## Create a Dataset from the Events XDM Schema in Experience Platform

1. On the left menu, under DATA MANAGEMENT node, click Datasets. The Datasets page opens.
2. Click Browse, if not opened already.
3. On the top - right, click Create dataset to create a new dataset. The Create dataset page opens.
4. To create a dataset from the new XDM schema that you have created, click Create dataset from schema.
   The Create dataset from schema page opens.
5. Under the Select schema section’s NAME column, click Website InteractionsSchema. In this example, it is John - Website Interactions Schema
6. After selecting the schema, click Next to continue. The Configure dataset section opens.
7. Configure the dataset. In the Name section, type <your first name> - Website InteractionsDataset. In this example, it is John - Website Interactions Dataset. Optionally, you can add a description to the dataset.
8. Click Finish to complete the dataset configuration. The new dataset page opens under theDatasets section, as shown:
   ![Adobe](/images/datasets/create-individual-dataset9.png "Create Datasets")
9. Click the newly created dataset. The dataset page opens on the Dataset activity tab, as shown:
   ![Adobe](/images/datasets/create-individual-dataset10.png "Create Datasets")
10. On the right pane, click the Profile key to enable the new dataset to be part of ExperiencePlatform's Real- time Customer Profile. You will not be able to enable the Profile as the schemafrom which the dataset is created, was not enabled for Profile.

Note: If the schema on which the dataset is created is not enabled for Profile, then you will not be able to enable the Profile for the dataset as well.


Create a Dataset  from  the Events XDM Schema in Experience Platform.

Create and Configure Event Dataset


Scenario: Create a dynamic audience for customers who have made two purchases this month, where the order value of second purchase is greater than the order value of the first purchase.

1. Click Create audience. The Create audience dialog opens.
2. Ensure the Build rule audience creation method is selected and click Create. The rule builder canvas opens.
3. On the left pane, click the Events tab.
4. Under EVENT TYPES, perform the following steps:

   - Search Purchases and drag and drop it onto the rule builder.
   - Search Any and drag and drop it onto the rule builder next to Purchases.
   - Search Purchases and drag and drop it next to the Any event type. The Events section should now look, as shown:
     ![Adobe](/images/segments/segments32.png "Create a Dynamic Audience")

5. Click the Any time drop- down arrow and select This Month.
6. On the left pane, ensure the Search box is clear, and notice that the three variables you added are displayed under the BROWSE VARIABLES section, as shown:
   ![Adobe](/images/segments/segments33.png "Create a Dynamic Audience")
7. Click Purchases 2, as shown. The variables are listed at the top
   ![Adobe](/images/segments/segments34.png "Create a Dynamic Audience")
8. Ensure you have selected Purchases, as shown. The Event Rule section is displayed at the bottom.
   ![Adobe](/images/segments/segments35.png "Create a Dynamic Audience")
9. On the left pane, navigate to Commerce > Order and drag Price Total onto the Add event section, as shown:
   ![Adobe](/images/segments/segments36.png "Create a Dynamic Audience")
10. Click the folder icon on the left pane, as shown, and click Variables.
    ![Adobe](/images/segments/segments37.png "Create a Dynamic Audience")
11. Under BROWSE VARIABLES, click Purchases 1. The variables are listed at the top
12. Navigate to Commerce > Order and drag Price Total onto the Add to compare operands box. TheAdd to compare operands box appears only after you drag Price Total variable onto the EventsRules section, as shown:
    ![Adobe](/images/segments/segments38.png "Create a Dynamic Audience")
13. Click the equals drop- down arrow and select is greater than. Now, you have a dynamic segment where the price total of purchase 2 is greater than the price total of purchase 1.
    ![Adobe](/images/segments/segments39.png "Create a Dynamic Audience")
14. In the Name box on the right pane, provide a name for the segment such as Dynamic Audience_Today’sDate.
15. Click Save and close to save the audience.


Create a Dynamic Audience in Adobe Real - Time Customer Data.

Create a Dynamic Audience


## Verify Multi-Entity Relationship i n Experience Platform

1. On the left navigation pane, click CUSTOMER > Identities. The Identities page opens.
2. Click Browse. The list of existing identities is displayed, as shown:
3. Scroll down to find Demo System - ProductSKU. This is the main identifier and reconciliation key between the two XDM schemas, Website Interactions schema and Product Catalog schema.
4. On the left navigation pane, click DATA MANAGEMENT > Schemas. The Schemas page opens on the Overview tab.
5. Click Browse. All the available schemas are listed.
6. Scroll down and click Product Catalog Schema. The Product Catalog Schema page opens displaying the structure of the schema, as shown:
   ![Adobe](/images/segments/segments24.png "Create a Multi-Entity Audience")
7. In the schema structure, navigate to \_adlsplatform | Object and expand it. The identity fields under the node are displayed, as shown. In this example, observe that productSKU | String is a defined identity.
   ![Adobe](/images/segments/segments25.png "Create a Multi-Entity Audience")
8. Note that a fingerprint icon appears inside the node indicating a defined identity.
9. Click Cancel to close the schema structure window to return to the Schemas page.
10. In the NAME column, scroll down to find and click Demo System - Event Schema for Website(Global v1.1). The Demo System - Event Schema for Website (Global v1.1) page opens.
11. On the Composition pane, scroll down to Relationships and click productListItems.SKU.
12. The productListItems.SKU relationship details are displayed, as shown. Observe the reference schema details on the Field properties pane.
    ![Adobe](/images/segments/segments26.png "Create a Multi-Entity Audience")
13. Click Cancel to return to the Schemas page.

## Create a Multi-Entity Audience in Experience Platform

1. On the left navigation pane, click CUSTOMER > Audiences. The Audiences page opens.
2. On the top-right, click Create audience. The Create audience dialog opens
3. Ensure the Build rule audience creation method is selected and click Create.
4. On the left pane, click the Events tab. The existing event classes and types are displayed.
5. In the search box, type color. The fields associated with color are listed.
6. Drag and drop productColor onto the rule builder. The productColor rule is added.
7. In the Events Rule section, retain equals as the operator.
8. In the productColor value box, type blue and click Enter. The selected color name appears under the value box. The rule should look, as shown
   ![Adobe](/images/segments/segments27.png "Create a Multi-Entity Audience")
9. On the Audience properties pane, click Refresh estimate to see the audience population, if any. You may not see any result if the instance has no previous data.
10. On the Audience properties, in the Name box, provide an audience name such as MultiEntityAudience_Today’sDate.
11. Ensure the Evaluation method is selected as Batch.
12. Click Save and Close. The audience summary is displayed.

    Note: Streaming segmentation does not support multi- entity segmentation yet. The batch segments take 24 hours to be evaluated, and, therefore, may not contain any data after the segment is created.


Create a Multi-Entity Audience in Adobe Real - Time Customer Data.

Create a Multi-Entity Audience


Scenario: Create a sequential audience based on the following shopping events of a customer who visited your website:

1. Customer visits a specific section of the webpage.
2. Customer visits a specific page and adds a product to the cart.
3. Customer does not proceed to purchase the product.

Creating a sequential audience with the above events in the same order will help you to target the customers who finalized a product but did not continue to purchase it. You can then send them promotional or reminder communications to complete the purchase.

To create a sequential audience for the above listed sequence

1. On the left navigation pane, under CUSTOMER > Audiences. The Audiences page opens.
2. Click Create audience. The Create audience dialog opens.
3. Select Build rule as the audience creation method and click Create. The rule builder canvas opens.
4. On the left pane, click the Events tab. The existing events and event types are displayed.
5. Under BROWSE CLASSES, click XDM ExperienceEvent. All sub folders under the event are displayed
6. In the search box, type Page Views. The field is listed, as shown:
   ![Adobe](/images/segments/segments20.png "Compose Audience by Building Rule")
7. From the left pane, under the EVENT TYPES, drag the field Page Views onto the rule builder canvas.
8. On the left pane search box, type Product List (Cart) Adds. The field is listed.
9. Drag the Product List (Cart) Adds field onto the rule builder canvas next to the existing rule, as shown:

   Note: To ensure the new rule is added next to the existing rule, look for a blue line on the right of the existing rule. The Product List (Cart) Adds event rule is added next to PageViews.
   ![Adobe](/images/segments/segments21.png "Compose Audience by Building Rule")

10. On the left pane search box, type Purchases. The field is listed.
11. From the left pane, under the EVENT TYPES, drag the Purchases field onto the rule builder canvas,next to the Product List Adds rule.
12. Click the clock icon between the rules Product List Adds and Purchases, as shown. The timing options appear.
    ![Adobe](/images/segments/segments22.png "Compose Audience by Building Rule")
13. Select the After checkbox. The timing options appear.
14. Type 1 to indicate a period of one week. The time span between the two rules in a segment is now set.This time span decides the sequence in sequential segmentation.
15. Click the Purchases rule. The Event Rules section appears.
16. On the Event rules section, click the Include drop-down arrow, as shown, and click Exclude.
    ![Adobe](/images/segments/segments23.png "Compose Audience by Building Rule")
    The rule changes to exclude the selected event page.
17. On the Audience properties pane, click Refresh estimate to view the qualified profiles.
18. In the Name box, type Sequential Audience_Today’sDate.
19. Click Save and Close. The audience details page opens.


Create a Sequential Audience in Adobe Real - Time Customer Data.

Create a Sequential Audience


Scenario: You have received a file that includes a list of audiences who have returned a product in the last 30 days. You want to import these audience, so that you can re target them with campaigns

1. Click CUSTOMER > Audiences. The Audiences page opens.
2. Click Import audience at the top- right of the page. The Workflows > Import audience CSV page opens in the Add data tab.
3. Click Choose files and select the Sample Audiences.csv file provided to you by your instructor. You can also drag and drop the file. The file is uploaded successfully and the sample data is displayed at the bottom of the page.
4. Click Next. The Configure tab opens.
5. In the Audience details section, replace the existing name in the Audience Name box with a relevant name such as Product Returns_Today’s_date.
6. Under Identity selection, perform the following steps to select the primary identity and namespace to use for profiles:

   - From the Primary identity field dropdown, select email.
   - Under Identity namespace value, click the pencil icon. The Select identity type dialog opens.
   - In the search box, type email, select Email from the results and click Select. The namespace value is updated and the Configure tab opens

7. Click Next. The Review tab opens with Audience details, Dataset details, S ample data, and Column data types details.

   You can modify the column data types, if required, by clicking Edit. For this activity, do not make any changes.

8. After reviewing all details, click Finish. The audience was saved successfully message appears at the bottom of the page.
9. On the Browse tab of the Audiences page, click the audience you imported now. The Detail page opens.
10. In the Ingestion details card, notice details such as records ingested, records failed, and profile segments. The processing may take a few minutes.
11. Click Apply access labels at the top- right of the page. The Apply access and data governance labels dialog opens. You can apply the relevant data governance labels here.
12. Select C2 and C3 labels and click Save. The policy labels are applied and listed in the Audience summary card.
13. Click Edit properties in the Audience summary card. The Edit properties dialog opens.
14. In the Tags field, type and select one or more tags. For example, type Imported_Audiences and selectCreate “Imported_Audiences” from the option displayed. The tag is created.
15. Click Save. Notice that the tag name is listed under Tags in the Audience summary card.


Import Audience in Adobe Real - Time Customer Data.

Import Audience


Let's create a new XDM schema to capture the customer interactions on a website.This is an event or time series type schema. Unlike a attributes or record- type schema, this event schema manages the events as they occur. So, events schemas are Time Series- type schema.

1. Create an event XDM schema.
2. Add field groups to the XDM schema.
3. Define identity mapping.

## Create an Event XDM Schema

1. On the browser, navigate to Experience Platform Home page.
2. On the left menu, under DATA MANAGEMENT, click Schemas. The Schemas page opens.
3. On the top- right, click Create schema to create a new schema. A drop - down list of schema types is displayed.
4. Click XDM ExperienceEvent, as shown, to create an event XDM schema.
   ![Adobe](/images/schema/event-xdm-schema.png "Create an event XDM schema")
   The Untitled schema page opens.

5. On the right pane Schema properties section, in the Display name box, type Web Site Interactions Schema as shown:
   ![Adobe](/images/schema/event-xdm-schema2.png "Create an event XDM schema")
6. Click Save to save the schema. The Schema saved successfully message appears. The newly created schema displays a default class containing some fields and field structures. Observe that under the Class section, XDM ExperienceEvent class is listed

## UI updates:

![Adobe](/images/schema/event-xdm-schema3.png "Create an event XDM schema")

![Adobe](/images/schema/event-xdm-schema4.png "Create an event XDM schema")

## Add Field Groups to the XDM Schema

1. On the left pane, under the Composition > Field groups section, click Add, as shown, to add the field groups.
   ![Adobe](/images/schema/event-xdm-schema5.png "Create an event XDM schema")
   The Add field groups page opens.
2. Retain the selection of Use existing field groups.
3. From the NAME column, select the following field groups, by clicking the checkboxes, as shown:

   - IdentityMap
   - Search Details
   - Orchestration eventID
   - AEP Web SDK ExperienceEvent
   - Campaign Marketing Details
   - Experience Event - Proposition Reference
   - Experience Event - Proposition Interactions
   - Commerce details

     ![Adobe](/images/schema/event-xdm-schema6.png "Create an event XDM schema")

4. On the top- right, click Add field groups to add the selected field groups to the schema. The added field groups appear on the schema Composition pane, as shown
5. Click Save to save the edits to the schema.

## Add Custom Field groups

1. On the left pane, under the Composition > Field groups section, click Add to add a new field group. The Add field groups page opens.
2. Click the option Create a new field group. The Create a new field group section opens.
3. In the Display name section, type ExperienceEvent Core v2.1.
4. In the Description section, type ExperienceEvent Core v2.1, as shown:
   ![Adobe](/images/schema/event-xdm-schema7.png "Create an event XDM schema")
5. Click Add field groups to add the newly created field group to the schema. The schema structure is updated with the newly added field group. However, the new field group is still empty. You will add fields to the new field group.
6. On the left pane, under the Field groups section, click the newly added field groupExperienceEvent Core v2.1.
7. Next to your schema name, click the add field icon, as shown:
   ![Adobe](/images/schema/event-xdm-schema8.png "Create an event XDM schema")
   A new field named Untitled Field | Type is added to the schema.
8. To define the new field, click Untitled Field I Type. The Field properties pane opens on the right.
9. Provide the following details, as shown:

   - In the Field name box, type identification.
   - In the Display name box, type identification.
   - From the Type drop- down menu, select Object.
   - Click the Field Group drop- down arrow to select the previously created ProfileIdentification field group.
     ![Adobe](/images/schema/event-xdm-schema9.png "Create an event XDM schema")
   - Click Apply to complete creating the object field. The newly created identification object is added to the structure, as shown:
     ![Adobe](/images/schema/event-xdm-schema10.png "Create an event XDM schema")
     The new field represents a custom object under your Experience Platform Tenant ID. In this example, the tenant ID is \_adlsplatformapac.

     Note: You can check the Tenant ID for your Experience Platform instance in yourEnvironment Variables. In these activities, the name of the Tenant ID is based on theExperience Platform instance you are using, such as EMEA, US, JAPAN, and APAC.

     You will now add ecid, emailId, and phoneNumber fields to this identification object.

10. Click the add field icon next to identification | Object, as shown:
    ![Adobe](/images/schema/event-xdm-schema11.png "Create an event XDM schema")
11. A new field named Untitled Field | Type is added under identification. The Field properties pane appear on the right.
12. To configure the values for the ecid field on the Field properties pane, perform the following steps:

    - In the Field name box, type ecid.
    - In the Display name box, type ecid.
    - emailIdSha256 (primary)
    - From the Type drop- down menu, select String, as shown:
      ![Adobe](/images/schema/event-xdm-schema12.png "Create an event XDM schema")
    - Scroll down and click Apply to save the field. After the initial field configuration is complete,the ecid field appears under the identification | Object node.

13. Click the add field icon next to identification | Object to add another new field for emailId. A new field named Untitled Field | Type is added under identification | Object. Empty field detail boxes appear on the right pane.
14. To configure the values for the emailId field, perform the following steps:

    - In the Field name box, type emailId.
    - In the Display name box, type emailId.
    - From the Type drop- down menu, select String.
    - Scroll down and click Apply to save. The phoneNumber field appears under the identification | Object:
      ![Adobe](/images/schema/event-xdm-schema13.png "Create an event XDM schema")

15. Click the add field icon next to the identification | Object to add another new field for phoneNumber. A new field named Untitled Field | Type is added under identification | Object.Empty field detail boxes appear on the right pane.
16. To configure the values for the p honeNumber field, perform the following steps:

    - In the Field name box, type phoneNumber.
    - In the Display name box, type phoneNumber.
    - From the Type drop- down menu, select String.
    - Scroll down and click Apply to save the field. After the initial field configuration is complete,the emailId field appears under identification | Object node, as shown:

17. Observe that in the field group structure, each field is defined as String type, as shown:

    ![Adobe](/images/schema/event-xdm-schema14.png "Create an event XDM schema")

18. Click Save to save the changes to the schema.


Create a new XDM schema to capture the customer interactions on a website.

Create Event XDM Schema


1. Create attributes based XDM schema.
2. Add field groups to the XDM schema.
3. Add a custom field group to the XDM schema.
4. Define identity mapping.

## Create Attributes- Based XDM Schema

1. On the browser, navigate to Experience Platform Home page.
2. On the left menu, under DATA MANAGEMENT, click Schemas. The Schemas page opens.
3. On the top- right, click Create schema to create a new schema. A drop- down list of schema types is displayed, as shown.

![Adobe](/images/schema/profile-xdm-schema.png "Create Attributes- Based XDM Schema")

4. Click XDM Individual Profile to create attributes based XDM schema. The Untitled schema page opens.
5. On the right pane Schema properties section, in the Display name box, type name of the Schema.
6. Click Save to save the schema. The Schema saved successfully message appears. The newly created schema displays a default class containing some fields and field structures. Observe that under the Class section, XDM Individual Profile is listed, as shown:

![Adobe](/images/schema/profile-xdm-schema2.png "Create Attributes- Based XDM Schema")

\*\* When ingesting the data against this schema, some fields are required. For example, \_id is a required field with a unique id representing a specific data ingestion.

## UI updates:

![Adobe](/images/schema/profile-xdm-schema3.png "Create Attributes- Based XDM Schema")

![Adobe](/images/schema/profile-xdm-schema4.png "Create Attributes- Based XDM Schema")

## Add Field Groups to the XDM Schema

1. On the left pane, under the Composition > Field groups section, click Add, as shown, to add the demographic details field group.
   ![Adobe](/images/schema/profile-xdm-schema5.png "Create Attributes- Based XDM Schema")
   The Add field groups page opens.
2. Retain the selection of Use existing field groups.
3. From the NAME column, select the following field groups, as shown:

   - Demographic Details
   - Personal Contact Details
   - Preference Details
     ![Adobe](/images/schema/profile-xdm-schema6.png "Create Attributes- Based XDM Schema")

4. On the top - right, click Add field groups to add the selected field groups to the schema. The added field groups appear on the schema Composition pane, as shown
   ![Adobe](/images/schema/profile-xdm-schema7.png "Create Attributes- Based XDM Schema")
5. Click Save to save the edits.

## Add a Custom Field Group to the XDM Schema

1. On the left pane, under the Composition > Field groups section, click Add to add a new field group. The Add field groups page opens.
2. Click the option Create a new field group. The Create a new field group section opens.
3. In the Display name section, type Profile Identification name.
4. In the Description section, type Profile Identification name.
   In this example, the display name and description are defined as John Profile Identification, as shown:
   ![Adobe](/images/schema/profile-xdm-schema8.png "Create Attributes- Based XDM Schema")
5. Click Add field groups to add the newly created field group to the schema. The schema structure is updated with the newly added field group. However, the new field group is still empty. You will add fields to the new field group.
6. On the left pane, under the Field groups section, click the newly added field group your Profile Identification.
7. Next to your schema name, click the add field icon, as shown:
   ![Adobe](/images/schema/profile-xdm-schema9.png "Create Attributes- Based XDM Schema")

A new field named Untitled Field | Type is added to the schema and the Field properties pane opens on the right. The new field represents a custom object under your Experience PlatformTenant ID.

Note: You can check the Tenant ID for your Experience Platform instance in yourEnvironment Variables. In these activities, the name of the Tenant ID is based on theExperience Platform regional instance you are using, such as EMEA, US, JAPAN, and APAC.

8. On the Field properties pane, provide the following definitions:

   - In the Field name box, type identification.
   - In the Display name box, type identification.
   - From the Type drop- down menu, select Object.
   - Click the Field Group drop- down arrow to select the previously created Profile Identification field group, as shown
     ![Adobe](/images/schema/profile-xdm-schema10.png "Create Attributes- Based XDM Schema")
   - Click Apply to save your changes. The Apply button is enabled after you select the respective field group. The new identification object is added to the schema under the tenantID node.

   You will now add ecid, emailId, emailIdSha256, and mobilenr fields to this identification object.

9. Click the add field icon next to identification | Object, as shown:
   ![Adobe](/images/schema/profile-xdm-schema11.png "Create Attributes- Based XDM Schema")
   A new field named Untitled Field | Type is added under identification. The Field properties pane boxes appear on the right.
10. To configure the values for the ecid field, perform the following steps:

    - In the Field name box, type ecid.
    - In the Display name box, type ecid.
    - From the Type drop - down menu, select String, as shown:
      ![Adobe](/images/schema/profile-xdm-schema13.png "Create Attributes- Based XDM Schema")
    - Scroll down and click Apply, as shown, to save the field.
      ![Adobe](/images/schema/profile-xdm-schema14.png "Create Attributes- Based XDM Schema")

After the initial field configuration is complete, the ecid field appears under the identification | Object node.

11. Click the add field icon next to identification | Object to add another new field for emailId. A new field named Untitled Field | Type is added under identification | Object. The Field properties pane appears on the right.
12. To configure the values for the emailId field, perform the following steps:

    - In the Field name box, type emailId.
    - In the Display name box, type emailId.
    - From the Type drop- down menu, select String.
    - Scroll down and click Apply to save the field. After the initial field configuration is complete,the emailId field appears under identification | Object node, as shown:
      ![Adobe](/images/schema/profile-xdm-schema15.png "Create Attributes- Based XDM Schema")

13. Click the add field icon next to identification| Object to add another new field for emailIdSha256.A new field named Untitled Field | Type is added under the identification| Object. The Field properties pane appears on the right.
14. To configure the values for the emailIdSha256 field, perform the following steps:

    - In the Field name box, type emailIdSha256.
    - In the Display name box, type emailIdSha256.
    - From the Type drop- down menu, select String.
    - Scroll down and click Apply to save the field. After the initial field configuration is complete,the emailIdSha256 field appears under identification| Object, as shown:
      ![Adobe](/images/schema/profile-xdm-schema16.png "Create Attributes- Based XDM Schema")

15. Click the add field icon next to the identification | Object to add another new field for mobilenr. A new field named Untitled Field | Type is added under identification | Object. The Field properties pane appears on the right
16. To configure the values for the mobilenr field, perform the following steps:

    - In the Field name box, type mobilenr.
    - In the Display name box, type mobilenr.
    - From the Type drop- down menu, select String.
    - Scroll down and click Apply to save. The mobilenr field appears under the identification |Object, as shown:
      ![Adobe](/images/schema/profile-xdm-schema17.png "Create Attributes- Based XDM Schema")
    - Observe that in the field group structure, each field is defined as String type.

## Define Identity Mapping

The newly created fields under the identification | Object are not defined as identity fields, yet.You will define the following fields in the schema Individual Profiles Schema as identifiers:

    - ecid (secondary)
    - emailId (primary)
    - emailIdSha256 (primary)
    - mobilenr (secondary)

1. On the Structure pane, under identification | Object, click ecid. The corresponding field properties are displayed on the right pane.
2. In the Field properties section, scroll down and click the Identity check box, as shown:
   ![Adobe](/images/schema/profile-xdm-schema18.png "Create Attributes- Based XDM Schema")
3. From the Identity namespace drop- down menu, select ECID, as shown:
   ![Adobe](/images/schema/profile-xdm-schema19.png "Create Attributes- Based XDM Schema")
4. Click Apply, as shown, to save the changes. The ecid field under the identification object is updated as a secondary identifier.
   ![Adobe](/images/schema/profile-xdm-schema20.png "Create Attributes- Based XDM Schema")
5. On the Structure pane, under identification | Object, click emailId. The corresponding field properties are displayed on the right pane.
6. In the Field properties section, scroll down and click the Identity checkbox.
7. Click the Primary Identity checkbox.
8. From the Identity namespace drop- down menu, select Email, as shown:
   ![Adobe](/images/schema/profile-xdm-schema21.png "Create Attributes- Based XDM Schema")
9. Click Apply to save the changes. The emailId field is updated as a primary identifier.
10. On the Structure pane, under identification | Object, click emailIdSha256. The corresponding field properties are displayed on the right pane.
11. In the Field properties section, scroll down and click the Identity checkbox.
12. From the Identity namespace drop- down menu, select EmailIdSha256(lowercase).
13. Click Apply to save the changes. The emailIdSha256 field is updated as a secondary identifier.
14. On the Structure pane, under identification | Object, click mobilenr. The corresponding field properties are displayed on the right pane.
15. In the Field properties section, scroll down and click the Identity checkbox.
16. From the Identity namespace drop- down menu, select Phone.
17. Click Apply to save the changes. The mobilenr field is updated as a secondary identifier. Observe that all the above identities are now listed under identities section, as shown:
    ![Adobe](/images/schema/profile-xdm-schema22.png "Create Attributes- Based XDM Schema")
18. On the top- right, click Save to save the changes to the schema.
19. To enable the newly created XDM schema with Real- time Customer Profile, perform the following steps:

    - Under the Composition pane, click the schema name,<your name>- Individual Profiles Schema. The Schema properties section opens on the right pane.
    - Click the Profile key, as shown:
      ![Adobe](/images/schema/profile-xdm-schema23.png "Create Attributes- Based XDM Schema")
      The Enable for profile confirmation box appears.
    - Click Enable, as shown:
      ![Adobe](/images/schema/profile-xdm-schema24.png "Create Attributes- Based XDM Schema")
      Configure and Manage Adobe Experience PlatformModule 2: Model the Incoming Data in ExperiencePlatform25c. Click Enable, as shown:On the Field properties pane, the Profile button changes to enabled now. The new XDMschema is now configured to be part of the Real- time Customer Profile.

20. Click Save to save changes to the schema.


Create a new XDM schema to capture the customer identity details and attributes.

All Adobe Blogs | List View