Data views use cases

These use cases show the flexibility and power of data views in Customer Journey Analytics.

Create an Orders metric from a pageTitle (string) schema field

For example, when creating a data view, you could create an Orders metric from a pageTitle schema field that is a string. Here are the steps:

  1. On the Components tab, drag the pageTitle into the Metrics section under Included Components.

  2. Now highlight the metric you just dragged in and rename it under Component Settings on the right:

  3. Open the Include/Exclude Values dialog on the right and specify the following:

    The “confirmation” phrase indicates that this is an order. After reviewing all the page titles where those criteria are met, a “1” will be counted for each instance. The result is a new metric (not a calculated metric.) A metric that has included/excluded values can be used everywhere any other metric can be used. It works with Attribution IQ, filters, and everywhere else you can use standard metrics.

  4. You can further specify an attribution model for this metric, such as Last Touch, with a Lookback window of Session.
    You can also create another Orders metric from the same field and specify a different attribution model for it, such as First Touch, and a different Lookback window, such as 30 days.

Use integers as dimensions

Previously, integers would automatically be treated as metrics in CJA. Now, numerics (including custom events from Adobe Analytics) can be treated as dimensions. Here is an example:

  1. Drag the call_length_min integer into the Dimensions section under Included Components:

  2. You can now add Value Bucketing to present this dimension in a bucketed fashion in reporting. (Without bucketing, each instance of this dimension would appear as a line item in Workspace reporting.)

For more information on other data views settings, see Create data views.
For a conceptual overview of data views, see Data views overview.

On this page