Creating Data Views

Create Data Views

To create a data view:

1. On the navigation bar, click Event TrackingData Views.
2. Click . 
3. On the Conditions tab, add one or more existing events.
   Note: Currently, events can be combined only with the Any of the following option (which is a logical OR association). As a result, creating a nested group (with ) has no discernible effect.
   1. Click .
   2. Enter the name of an event in the criteria’s text field, or click and select an event.
   3. (Optional) Refine the event’s attributes. Click . The attributes that you can modify are based on the attributes that are associated with the original event.

      Attributes that you modify do not affect the attributes for the event itself. The attributes in this panel affect how the event is processed for this data view only, so you can use an event in multiple contexts without changing its underlying definition.

   4. (Optional) After you add all the events, you can click to review the summary of how your events are used in this data view.
4. On the Attributes tab, review all of the attributes associated with this data view. This list is an intersection of the attributes from all of the events.
   Note: Data view attributes can be used in personalization variables if the attribute is listed on this tab.
5. On the Attribution tab, select touchpoints and enable attribution analysis. Attribution analysis for data views is disabled by default. For more information, see Enabling Attribution.
6. On the Orchestration tab, complete one of these actions:
   • Select Mark ready to change the status from Designing to Ready. A Ready status indicates that this item is ready to be published. When you are ready to promote an item from a Ready status to an Active status, click Publish.
     Note: When you publish an item, you are prompted to publish any dependent items that are marked Ready.

     Items with a Ready status can be changed back to a Designing status by clicking Return to designing. Changing this status to Designing prevents the item from being published.

     Note: If your item has a Ready status and a start date, the item is not automatically published when the start date is reached. For example, if you are creating a task, it must be published in order for the start date to activate the task.
   • Select Mark ready and publish to change the status from Designing to Active. Items with an Active status cannot be changed back to Designing.

   If the content of a published item is changed and saved, that item becomes out of sync with the published version. To synchronize the content, select Republish. Otherwise, the item stays out of sync with the published version and the updates are not delivered.

   For more information, see Republishing Out of Sync Items.

   Note: If a task or journey is using a data view that is published, you cannot modify the data view’s conditions. Other properties (such as the name) can be modified even if the data view is consumed by other items.
7. On the OrchestrationExternal Availability tab, select the agents that you want to send the data view to. You can click to view more information about the agents.
8. (Optional) Click and select Properties to perform these actions:
   • Add a name and a description for the event.
   • See folder information for the event.
   • Select Make the event available to the customer state profile to make the data for SAS Customer Intelligence 360 available to SAS Intelligent Decisioning so that SAS Intelligent Decisioning can return criteria for targeting and merge tags. The targeting and merge tag criteria are displayed in the Decision Flows and Models folder.
     Note: This option is accessible only after SAS Intelligent Decisioning is enabled for your tenant. For more information, contact SAS Technical Support.
9. Use your data view in a task or journey to complete these actions:
   • Set metrics for a journey or task.
   • Add a target audience to a task.

Manage Data Views

On the OrchestrationUsage tab, you can view which items use the data view and the items that the data view uses.

The ability to view dependencies between items enables you to see the items that a task depends on to work successfully. Usage information helps you identify how changes that you make to one item might affect another item.