Creating a data view involves either creating metrics and dimensions from schema elements or utilizing standard components. Most schema elements can be either a dimension or a metric depending on your business’s requirements. Once you drag a schema element into a data view, options appear on the right where you can adjust how the dimension or metric operates in CJA.
Provides overarching settings for the data view.
|Connection||This field links the data view to the connection that you established earlier, which contains one or more Adobe Experience Platform datasets.|
|Name||Required. The name of the data view. This value appears in the top-right dropdown in Analysis Workspace.|
|Description||Optional. Adobe recommends a detailed description so that users understand why the data view exists and who it is designed for.|
Designates the name of containers for the data view. Container names are frequently used in Filters.
|Person container name||Person (default). The Person container includes every session and event for visitors within the specified time frame. If your organization uses a different term (for example, “Visitor” or “User”), you can rename the container here.|
|Session container name||Session (default). The Session container lets you identify page interactions, campaigns, or conversions for a specific session. You can rename this container to ‘Visit’ or any other term your organization prefers.|
|Event container name||Event (default). The Event container defines individual events in a dataset. If your organization uses a different term (for example, “Hits” or “Page Views”), you can rename the container here.|
Indicates the calendar format that you want the data view to follow. You can have multiple data views based on the same Connection and give them different calendar types or time zones. These data views can allow teams that use different calendar types to accommodate their respective needs with the same underlying data.
|Time zone||Choose which time zone you want your data to be presented in. If you choose a time zone that operates on Daylight Savings Time, data is automatically adjusted to reflect that. In the spring when clocks adjust one hour ahead, a one-hour gap is present. In the fall when clocks adjust one hour behind, one hour is repeated during the DST shift.|
|Calendar Type||Determine how weeks of the month are grouped.
Gregorian: Standard calendar format. Quarters are grouped by month.
4-5-4 Retail: A standardized 4-5-4 retail calendar. The first and last months of the quarter contains 4 weeks, while the second month of the quarter consists of 5 weeks.
Custom (4-5-4): Similar to the 4-5-4 calendar except you can choose the first day of the year and which year that the “extra” week occurs.
Custom (4-4-5): The first and second months of each quarter contain 4 weeks, while the last week of each quarter consist of 5 weeks.
Custom (5-4-4): The first month of each quarter consists of 5 weeks, while the second and third month of each quarter consists of 4 weeks.
|First month of the year and First day of week||Visible for the Gregorian calendar type. Specify what month you want the calendar year to start on, and what day you want each week to start on.|
|First day of current year||Visible for custom calendar types. Specify what day of the year that you want the current year to start. The calendar automatically formats the first day of each week based on this value.|
|Year in which the “extra” week occurs||With most 364-day calendars (52 weeks of 7 days each), each year accumulates leftover days until they form an extra week. This extra week is then added to the last month of that year. Specify which year that you want the extra week added to.|
Next, you can create metrics and dimensions from schema elements. You can also use Standard components.
Log in to Customer Journey Analytics and go to the Data Views tab.
Click Add to create a data view, or click on an existing data view to edit it.
Click the Components tab.
You can see the Connection at the top left, which contains the datasets, and its Schema fields below. Note that the components already included are standard required components (system generated) for all data views. Adobe also applies the filter Contains data by default, so that only Schema fields that contain data appear. If you want a field that does not contain data, remove this filter.
Drag a schema field, such as
pageTitle, from the left rail into the Metrics or Dimensions section.
You can drag the same schema field into the dimensions or metrics sections multiple times and configure the same dimension or metric in different ways. For example, from the
pageTitle field, you can create a dimension called “Product Pages”, and another one “Error pages”, by using different Component settings on the right.
If you drag a schema field folder from the left rail, they are automatically sorted into typical sections. String fields end up in the Dimensions section and numeric schema types end up in the Metrics section. You can also click Add all and all schema fields are added to their respective locations.
Once you select the component, a number of settings appear on the right. Configure the component using Component settings. Available component settings depend on if the component is a dimension/metric and the schema data type. Settings include:
Duplicating metrics or dimensions and then modifying specific settings is an easy way to create multiple metrics or dimensions from a single schema field. Select the Duplicate setting underneath the metric’s or dimensions’s name at the top right. Modify the new dimension or metric and save it under a more descriptive name.
You can filter schema fields in the left rail by the following data types:
You can also filter by datasets and by whether a schema field contains data or whether it is an identity. By default, Adobe initially applies the Contains data filter to all data views.
You can add filters that apply to an entire data view. This filter is applied to any report that you run in Workspace. Drag a filter from the list in the left rail to the Add filters field.
Determine the time period of inactivity between events before a session expires and a new one is started.
A time period is required. You can optionally also force a new session to start when an event contains a certain metric.
Once all desired settings are specified, click Save and finish.