Creating a data view involves either creating metrics and dimensions from schema elements or utilizing standard components. Creating metrics or dimensions gives you an enormous amount of flexibility. Previously, the assumption was that if you had datasets in Adobe Experience Platform, string fields were used as dimensions and numeric fields were used as metrics. In order to change any of these fields, you had to edit your schema in Platform. The data views UI now allows a more freeform definition of metrics and dimensions. For more use cases, see Data views use cases.
|Connection||This field links the data view to the connection that you established earlier, which contains one or more Adobe Experience Platform dataset/s.|
|Name||Giving the data view a name is mandatory.|
|Description||A detailed description is not mandatory but is recommended.|
|Time zone||Choose which time zone you want your data to be presented in.|
|Tags||Tags let you organize your data views into categories.|
|Containers||You can rename your containers here and this is how they will appear in any Workspace project that is based on this data view. Containers are used in filters and fallout/flow, etc., to define how broad or narrow the scope or context is. Learn more|
|Person container name is…||Person (default). The Person container includes every visit and page view for visitors within a specified time frame. You can rename this to ‘User’ or any other term you prefer.|
|Session container name is…||Session (default). The Session container lets you identify page interactions, campaigns, or conversions for a specific session. You can rename this to ‘Visit’ or any other term you prefer.|
|Event container name is…||Event (default). The Event container defines which page events you would like to include or exclude from a filter.|
Next, you can create metrics and dimensions from schema elements. You can also use Standard components.
You can see the Connection at the top left, which contains the datasets, and its Schema fields below. Keep in mind that:
Now 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”, etc., by renaming the Component Name on the right. From the pageTitle; field, you can also create metrics from a string value. For example,you could create one or more Orders metrics with different attribution settings and different include/exclude values.
You can drag in whole schema field folders from the left rail and they will automatically be sorted into traditional sections. String fields will end up in the Dimensions section and numerics in the Metrics section. Or, you can click Add all and all schema fields will be added.
Once you select the component, you see a number of settings appear on the right. Configure the component using the settings described below.
|Component type||Required. Allows you to change a component from Metric to Dimension or vice versa.|
|Component Name||Required. Lets you specify the friendly name that will appear in Analysis Workspace. You can rename a component to give it a data-view-specific name.|
|Description||Optional, but recommended, to provide information on the component for other users.|
|Tags||Optional. Lets you tag the component with custom or out-of-the-box tags for easier searching/filtering in the Analysis Workspace UI.|
|Field Name||The name of the schema field.|
|Dataset type||Required. A non-editable field showing which dataset type (event, lookup, or profile) the component came from.|
|Dataset||Required. A non-editable field showing which type of field the component came from (e.g. String, Integer, etc.). This field can contain multiple datasets.|
|Schema type||Refers to whether the component is a string, integer, etc.|
|Component ID||Required. The CJA API uses this field to reference the component. You can click the edit icon and modify this component ID. However, changing this component ID breaks all existing Workspace projects that contain this component.
If you ever create another data view that uses a different field for a pageTitle dimension, you can rename it and make the dimension cross-data view compatible.
|Path||Required. A non-editable field showing the schema path that the component came from.|
|Hide component in reporting||Default = off. Lets you curate the component out of the Data View when used in reporting. This does not impact permissions, just component curation. In other words, you can hide the component from non-Admins in reporting. Admins can still access it by clicking Show All Components in an Analysis Workspace project.|
Format settings are for metrics only.
|Format||Lets you specify the formatting of a metric, as Decimal, Time, Percent, or Currency.|
|Decimal Places||Lets you specify the number of decimal places a metric should display.|
|Show upward trend as||Lets you specify whether an upward trend on this metric should be considered good (green) or bad (red).|
|Currency||This setting appears only if the selected metric format is Currency. A list of currency options are available. Defaults to no currency. This allows you to represent revenue in the currency of your choice in reporting. This is not a currency conversion, just a UI formatting option.|
|Set attribution||Lets you specify the attribution settings you want to apply to this metric by default when it is used. This default can be overridden in a Freeform Table or in a Calculated Metric.|
|Attribution model||Lets you specify a default attribution model - only active when you turn on the Use Non-default attribution model setting. Defaults to Last Touch. Options are: Last Touch, First Touch, Linear, Participation, Same Touch, U-Shaped, J Curve, Inverse J, Time Decay, Custom, Algorithmic. Some of these options create additional fields that need to be filled out - like Custom or Time Decay. You can create multiple metrics using the same field - this means you can have one Last touch revenue metric and one First Touch revenue metric, but based on the same revenue field in the schema.|
|Lookback window||Lets you specify a default lookback window to a metric - only active when you turn on the Use Non-default attribution model setting. Options are: Person (Reporting Window), Session, Custom. When Custom is selected, we also give you the option to select any number of days/weeks/months/etc. (up to 90 days), just like Attribution IQ. You can have multiple metrics using the same schema field, but each with a separate lookback window.|
This setting allows you to modify the underlying data that you are reporting on, at query time. It is not the same as a filter. But filters will respect this new dimension, as will pathing and attribution.
For example, you could create a dimension out of the pageTitle field, but call it “error pages” and include any page that contains the phrase “error”.
|Case sensitive||Default = On. This setting applies only to the Include/Exclude Values section. It allows you to say whether the include/exclude rule you are applying should be case sensitive.|
|Match||Lets you specify which values you would like to consider for reporting prior to attribution and filters (e.g., only use values containing the phrase “error”). You can specify: If all criteria are met, or If any criteria are met.|
|Criteria||Lets you specify the match logic that should be applied to a specific filter rule.
|Match operand||Lets you specify the match operand that the match operator should be applied to.
|Add rule||Lets you specify an additional match operator and operand.|
|Count instances||Lets you specify whether a numeric or date type field used as a metric should count the times it was set rather than the value itself.
If you want to add up the instances of a numeric field and want to simply add up the number of times a field was set rather than the actual value inside.
This is useful for creating an Orders metric from a Revenue field, for example. If revenue was set, then we want to count 1 single order rather than the numeric revenue amount.
No Value Options settings are analogous to Unspecified or None values in reporting. In the data views UI, on a component-by-component basis, you can decide how you want these values to be treated in reporting. You can also rename No value to something that better suits your environment, such as Null, Not set, or others.
Also note that whatever you specify in this field can be used for special UI treatment of the No Value line item in reporting as stated in the No Value Options setting.
|If shown, call No value…||This is where you can rename No value to something else.|
|Don’t show No value by default||Does not show this value in reporting.|
|Show No value by default||Does show this value in reporting.|
|Treat No value as a value||This setting will replace blank values in the data with the text that you specified under If shown, call No value … For example, if you had Mobile device types as the dimension, you could rename the No value item to “Desktop”. Note that when you change this field to a custom value, the custom value will be treated as a legitimate string value. Therefore, if you enter the value “Red” into this field, any instances of the string “Red” appearing in the data itself will also roll under the same line item that you have specified.|
For more information, see the topic on Persistence.
|Set persistence||Toggle key|
|Allocation||Lets you specify the allocation model used on a dimension for persistence. Options are: Most recent, Original, Instance, All. If you want a value to persist (similar to eVars in traditional Analytics), this is where you’d set it. The only key difference is that the maximum persistence you can set is 90 days. Also, Never expire is not an option.|
|Expiration||Lets you specify the persistence window for a dimension. Options are: Session (default), Person, Time, Metric. You might need to be able to expire the dimension on a purchase (such as internal search terms or other merchandising use cases). Metric lets you specify any of the defined metrics as the expiration for this dimension (e.g., a Purchase metric).|
For example, a bucket of ‘between 5 and up to 10’ will appear as a line item ‘5 to 10’ in Workspace reporting.
|Bucket value||Allows you to create a bucketed version of a numeric dimension. This lets you report on buckets of revenue or other numeric values as a dimension in reporting.|
|Up to||Lets you specify the boundaries of the first numeric dimension bucket. This applies to numeric dimensions only.|
|Between and up to||Lets you specify the boundaries of subsequent numeric dimension buckets.|
|Add bucket||Lets you add another bucket to numeric dimension bucketing.|
Besides creating metrics and dimensions from schema elements, you can also use standard components in your data views.
Standard components are components that are not generated from dataset schema fields but are instead system generated. Some system components are required in any data view to facilitate reporting capabilities in Analysis Workspace, while other system components are optional.
These required standard components are added to each data view by default.
|Component Name||Dimension or Metric||Notes|
|People||Metric||This metric is based on the person ID specified in a Connection.|
|Sessions||Metric||This metric is based on the sessionization settings specified below.|
|Events||Metric||This metric represents the number of rows from all event datasets in a Connection.|
|Day||Dimension||The ‘Day’ dimension reports the day that a given metric occurred. The first dimension item is the first day in the date range, and the last dimension item is the last day in the date range.|
|Week||Dimension||The ‘Week’ dimension reports the week that a given metric occurred. The first dimension item is the first week in the date range, and the last dimension item is the last week in the date range.|
|Month||Dimension||The Month dimension reports the month that a given metric occurred. The first dimension item is the first month in the date range, and the last dimension item is the last month in the date range.|
|Quarter||Dimension||The ‘Quarter’ dimension reports the quarter that a given metric occurred. The first dimension item is the first quarter in the date range, and the last dimension item is the last quarter in the date range.|
|Year||Dimension||The ‘Year’ dimension reports the year that a given metric occurred. The first dimension item is the first year in the date range, and the last dimension item is the most recent year in the date range.|
|Hour||Dimension||The ‘Hour’ dimension reports the hour that a given metric occurred (rounded down). The first dimension item is the first hour in the date range, and the last dimension item is the last hour in the date range.|
|Minute||Dimension||The ‘Minute’ dimension reports the minute that a given metric occurred (rounded down). The first dimension item is the first minute in the date range, and the last dimension item is the last minute in the date range.|
Optional Standard components are available under the Standard Components tab.
|Component Name||Dimension or Metric||Notes|
|Session Starts||Metric||This metric counts the number of events that were the first event of a session. When used in a filter definition (e.g. ‘Session Starts exists’), it filters down to just the first event of every session.|
|Session Ends||Metric||This metric counts the number of events that were the last event of a session. Similar to Session Starts, it can also be used in a filter definition to filter things down to the last event of every session.|
|Time Spent (seconds)||Metric||The Time Spent metric adds up the time between two different values for a dimension.|
|Time Spent per Event||Dimension||Time Spent per Event buckets the Time Spent metric into Event buckets.|
|Time Spent per Session||Dimension||Time Spent per Session buckets the Time Spent metric into Session buckets.|
|Time Spent per Person||Dimension||Time Spent per Person buckets the Time Spent metric into Person buckets.|
|Batch ID||Dimension||Represents the Experience Platform batch that an Event was part of.|
|Dataset ID||Dimension||Represents the Experience Platform dataset that an Event was part of.|
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, we apply the Contains data filter to all data views.
You can add filters that apply to your entire data view. This filter will be applied to any report that you run in Workspace.