Component settings

Last update: 2024-02-06
  • Created for:
  • Admin

The following information describes the settings that a data view component uses.

Component settings described in this section

Setting Description/Use case
Component type Required. Allows you to change a component from Metric to Dimension or the opposite way. Changing this drop-down selection shifts the component to its respective included components area.
Component Name Required. Lets you specify the friendly name that appears in Analysis Workspace. You can rename a component to give it a name specific to the data view.
Description Optional, but recommended. Provides information on the component to 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.
Context labels Optional. A drop-down list of available system-defined labels that can be applied to a component. These labels may be required to define a set of components used for reporting in Analysis Workspace projects or panels.
Schema 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 A non-editable field showing which dataset that the component originated from. This field can contain multiple datasets.
Schema Type A non-editable field showing the data type of the component. While you can use any supported schema field type in Platform, not all fields types are supported in Customer Journey Analytics. The following data types are supported: Integer, Int, Long, Double, Float, Number, Short, Byte, String, and Boolean. Only the String schema data type is allowed in Lookup datasets currently.
Component ID Required. The Customer Journey Analytics API uses this field to reference the component. Each component in a data view must be unique. Adobe automatically generates an ID for each component; however, you can click the edit icon and modify the component ID. Changing the component ID breaks all existing Workspace projects that contain this component. While each component needs a unique ID in a single data view, you can use the same component ID in other data views. If you use the same component ID in other data views, you can make Workspace projects compatible across data views.
For profile and lookup based components, the component ID has an ID prefix based on the dataset ID (for example: When you want to reuse a profile or lookup based component, like, in your Workspace project, and configure this component in different data views, ensure you rename the component ID uniquely (for example: across your data views.
Path Required. A non-editable field showing the schema path that the component came from.
Data Usage Labels Any data usage labels that were assigned to this component in Adobe Experience Platform. Learn more.
Hide component in reporting Lets you curate the component out of the data view for non-admins. Admins can still access it by clicking Show All Components in an Analysis Workspace project.

Here is a video on component settings in data views:

On this page