Use summary data

Select Add in Field groups.

In the Add field groups dialog, select Create new field group.

Enter a Display name for the field group, for example Example Summary Data. Optionally provide a description.

Select Add field groups.

You are back in the schema structure user interface. Select the new Example Summary Data in Field groups.

Select the next to the schema name Example summary Data Schema. A Field properties panel opens up allowing you to add details for a field.

1. Enter a Field name: campaign_id
2. Enter a Display name: campaign_id
3. Select a Type from the Select data type dropdown: String
4. Ensure Assign to Field group is selected, and select Example Summary Data from the dropdown.
5. Scroll down to the bottom, and select Apply.

Repeat the previous step for the other fields of the summary data. See the table below for the correct values.

To save your Example Summary Data field group as part of your schema, select Save. You see a confirmation when your schema is successfully saved.

Select Experience Platform from the     app switcher.

Select Datasets from the left rail.

Select Create dataset.

In the Datasets > Create datasets screen, select Create dataset from schema.

In the Select schema step of the Workflows > Create dataset from schema wizard, search for and select your Example Summary Data Schema.

Select Next.

In the Configure dataset step of the Workflows > Create dataset from schema wizard:

1. Enter a Name for the dataset, for example: Example Summary Data Dataset. Optionally provide a description.
2. Select Finish.

Select Experience Platform from the     app switcher.

Select Workflows from the left rail.

1. Select Map CSV to XDM schema from the Data ingestion options in the Workflows screen.
2. Select Launch from the Map CSV to XDM schema panel.

In the Dataflow detail step of the Workflows > Map CSV to XDM schema wizard:

1. Select Existing dataset for Target dataset.
2. Select Example Summary Data Dataset from the dropdown list.
3. Select Next.

In the Select data step of the Workflows > Map CSV to XDM schema wizard:

1. Drag and drop your file with summary data in CSV format onto Drag and drop files. Alternatively, use Choose files to select your file.
2. Ensure the Data format and Delimiter do have the correct values for your sample data. For example, Delimited as the Data format, and , as the Delimiter.
3. A sample (10 records) of your summary data is shown in Sample data.
4. Select Next.

In the Mapping step of the Workflows > Map CSV to XDM schema wizard:

1. Check whether all data fields of your Source Data are correctly mapped to the corresponding Target fields in your schema. For the sample data, no errors are reported as you explicitly named the fields in your schema similar to the field names in your sample data. Otherwise, you can use this screen to correct the mapping.
2. You can optionally select Validate to (once more) validate the data.
3. You can optionally select Preview data to open a dialog with a preview of the data once loaded into the dataset.
4. Select Finish.

Select Customer Journey Analytics from the     app switcher.

Select Connections from the top menu.

Select Create new connection.

In Connections > Untitled connection:

1. Enter a Connection name, for example Example Connection Using Summary Data.

2. Select the sandbox that contains the dataset you created and the other datasets you want to include from the Sandbox dropdown list.

3. Select less than 1 million from the Average number of daily events dropdown list.

4. Select Add datasets.

5. In the Select datasets step of the Add datasets wizard:

   1. Search and select Example Summary Data Dataset, Example Event Data Dataset, and Example Lookup Data Dataset.
   2. Select Next.

6. In the Datasets settings step of the Add datasets wizard:

   1. For the Example Event Data Dataset:

      1. Confirm the selections for Person ID (person_id) and Timestamp are correct.
      2. Select Web Data from the Data source type.
      3. Enable Import all new data.
      4. Enable Backfill all existing data.

   2. For the Example Lookup Data Dataset:

      1. Select tracking_code as the Key and tracking_code (Event datasets) as the Matching Key.
      2. Select Web Data from the Data source type.
      3. Enable Import all new data.
      4. Enable Backfill all existing data.

   3. For the Example Summary Data Dataset:

      1. Confirm the selections for Timestamp and Timezone are correct.
      2. Enable Import all new data.
      3. Enable Backfill all existing data.

   4. Select Add datasets.

In the Connections > Example Connection using Summary Data connection screen, select Save to save the connection.

Select Customer Journey Analytics from the     app switcher.

Select Connections from the top menu.

Select your connection, for example Example Connection Using Summary Data.

Select an appropriate date range in the Connection > Example Connection Using Summary data details.

1. Select and then select Last 7 days.
2. Select Apply.

Select Customer Journey Analytics from the     app switcher.

Select Data views from the top menu.

Select Create new data view.

In Data views, go through the wizard screens to configure your data view.

1. In the Configure step of Data views:

   1. Select your connection from Settings | Connection. For example, Example Connection Using Summary Data.
   2. Enter a Name for your data view, for example Example Data View Using Summary Data.
   3. Leave all other settings.
   4. Select Save and continue.

2. In the Components step of Data views > Example Data View Using Summary Data:

   1. Add the following components to the Dimensions and Metrics list. Note that for clarity, the component names are modified from their default name, using Component name in Component settings in the component panel (at the right).

      Metrics

      table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4
      Component name	Dataset	Schema data type	Schema path
      Cost	Example Summary Data Dataset	Double	_tenant.cost
      Impressions	Example Summary Data Dataset	Integer	_tenant.impression
      Orders	Example Event Data Dataset	Integer	_tenant.orders
      Revenue	Example Event Data Dataset	Double	_tenant.revenue_amount

      Dimensions

      table 0-row-4 1-row-4 2-row-4 3-row-4 4-row-4 5-row-4 6-row-4 7-row-4 8-row-4 9-row-4 10-row-4
      Component name	Dataset	Schema data type	Schema path
      Ad Group (Lookup)	Example Lookup Data Dataset	String	_tenant.ad_group
      Ad Group (Summary)	Example Summary Data Dataset	String	_tenant.ad_group
      Campaign Id	Exammpe Summary Data Dataset	String	_tenant.campaign_id
      Campaign Name (Lookup)	Example Lookup Data Dataset	String	_tenant.campaign_name
      Campaign Name (Summary)	Example Summary Data Dataset	String	_tenant.campaign_name
      Network	Example Summary Data Dataset	String	_tenant.network
      Page Name	Example Event Data Dataset	String	_tenant.page_name
      Person Id	Example Event Data Dataset	String	_tenant.person_id
      Tracking Code (Event)	Example Event Data Dataset	String	_tenant.tracking_code
      Tracking Code (Lookup)	Example Lookup Data Dataset	String	_tenant.tracking_code

   2. Select the Tracking Code (Event) dimension in the Dimensions list. In the component panel:

      

      1. Unfold Summary Data Group.

      2. Enable Create grouping.

      3. Select Campaign Id from the Dimension dropdown list. This step ensures that event data and summary data is properly combined for reporting.

      4. You can optionally enable Hide in reporting. Hide in reporting ensures the selected dimension (Campaign Id) is hidden in Analysis Workspace and other Customer Journey Analytics reporting tools. If you have enabled this option, you can verify the option:

         1. Select the Campaign Id dimension in the Dimensions list.
         2. You notice that Hide component in reporting in Component settings is now automatically enabled.

   3. Create a new derived field, for example Campaign Name (Lookup Derived Field), to ensure you can report in Workspace using the Campaign Name (Lookup) dimension from the Example Lookup Data dataset.

      

      1. Select campaign_id for Value.
      2. Select Example Lookup Data Dataset from the Lookup dataset dropdown menu.
      3. Select tracking_code from the Matching Key dropdown menu.
      4. Select campaign_name from the Values to return dropdown menu.
      5. Select Save.

   4. Add the newly created derived field, Campaign Name (Lookup Derived Field), to the Dimensions component list.

   5. Select the Campaign Name (Lookup) dimension in the Dimensions list. In the component panel:

      

      1. Unfold Summary Data Group.
      2. Enable Create grouping.
      3. Select Campaign Name (Lookup Derived Field) from the Dimension dropdown list. This step ensures that the Campaign Name (Lookup) from the Example Lookup Data Dataset can be safely used in reporting (see Workspace).

   6. Select the Revenue metric from the Metrics list. In the component panel:

      

      1. Unfold Attribution.

         1. Select Last Touch from the Attribution Model dropdown list.
         2. Select 30 Day from the Lookback window dropdown list.

      2. Unfold Format.

         1. Select Currency from the Format dropdown list.
         2. Select 2 from the Decimal places dropdown list.

   7. Select the Orders metric from the Metrics list. In the component panel:

      

      1. Unfold Attribution.

         1. Select Last Touch from the Attribution Model dropdown list.
         2. Select 30 Day from the Lookback window dropdown list.

      2. Unfold Format.

         1. Select Decimal from the Format dropdown list.
         2. Select ▲ Good (green) from the Show upward trend as dropdown list.

   8. Select Save and continue.

3. In the Settings step of Data views:

   1. Leave all settings at their defaults.
   2. Select Save and finish.

Select Components > Calculated metrics.

Select Add to add a new calculated metric.

1. Specify Cost per Impression for the Name.
2. Select Currency for Format.
3. Specify 4 for Decimal places.
4. Use Cost (Summary) ÷ Impressions (Summary) as Definition.
5. Select Save.

Select Add to add another new calculated metric.

1. Specify Return on Ad Spend for the Name.
2. Select Currency for Format.
3. Select 2 for Decimal places.
4. Use Revenue (Last Touch | 30 Days) − Cost (Summary) as Definition.
5. Select Save.

Drag Cost per Impression from Metrics and drop the metric to add as an additional column to the Freeform table.

1. Select Column settings.
   1. Disable Percent.

Drag Return on Ad Spend from Metrics and drop the metric to add as an additional column to the Freeform table.

1. Select Column settings.

   1. Disable Percent.

   2. Enable Conditional formatting.

      1. Select Auto-generated.
      2. Select a preferred Conditional formatting palette.

2. Select Save to save your project.