Customer Journey Analytics provides a canvas to drag and drop dimensions, metrics, filters, and functions to create custom metrics based on container hierarchy logic, rules, and operators. This integrated development tool lets you build and save simple calculated metrics or complex advanced calculated metrics.
You can begin creating a calculated metric in any of the follows ways:
The following image and accompanying table explain some of the main areas and features of the Calculated metrics builder.
|Title||Naming the metric is mandatory. You cannot save the metric unless it is named.|
|Description||Give it a user-friendly description to show what it’s used for and to distinguish it from similar ones.
The description also appears within a report. It’s best NOT to put the formula into the description - instead, describe what this metric should and should not be used for. (The formula is generated as you build the metric, underneath the Summary heading. As a result, there is no need to add the formula to the description.)
|Format||Choices include Decimal, Time, Percent, and Currency.|
|Decimal Places||Shows how many decimal places will be shown in the report. The maximum number of decimal places you can specify is 10.|
|Show Upward Trend As…||This metric polarity setting shows whether Analytics should consider an upward trend in the metric as good (green) or bad (red). As a result, the report’s graph will show as green or red when it’s going up.|
|Currency||The base currency for this data view.|
|Tags||Tagging is a good way to organize metrics. All users can create tags and apply one or more tags to a metric. However, you can see tags only for those filters that you own or that have been shared with you. What kinds of tags should you create? Here are some suggestions for useful tags:
The Summary formula updates anytime you make a change to the metric definition. This formula also shows up in the metrics rail on the left when you hover over a metric and click the icon.
|Definition||This is where you drag in metrics/calculated metrics, filters, and/or functions to build the calculated metric.
|Operator||Divided by ( ) is the default operator, plus there are the +, -, and x operators.|
|Preview||Provides a quick read on any possible errors. The preview covers the last 90 days. This is a way of initially gauging whether you have selected the right components for your metric. An unexpected result would mean you need to take a second look at the metric definition.|
|Product compatibility||For any calculated metrics that you create in CJA, this value is always listed as Fully Processed Data. Calculated metrics can only include data from event datasets.|
|Add||For all types of calculated metrics, you can add containers and static numbers to the definition. For advanced calculated metrics, you can also add filters and functions.
|Gear icon (Metric Type, Attribution)||Selecting the gear icon next to a metric lets you specify the metric type and attribution models.|
|Plus (+) icon||Lets you create a new component, such as a new filter (which takes you to the Filter Builder .)|
|Search Components||This search bar lets you search for dimensions, metrics, filters (advanced calculated metrics only), and functions (advanced calculated metrics only).|
|List of Dimensions||Rather than leaving the Calculated metric builder in order to build a simple filter (in the Filter builder), e.g. “Page = Homepage”, you can drag in Page and select Homepage directly from the Calculated metric builder. This results in a much more streamlined workflow for creating filtered calculated metrics.|
|List of Metrics||Metrics come in 3 categories:
|List of Filters||(Advanced calculated metrics only) As an Admin, this list shows all filters created in your login company. If you are a non-Admin user, this list shows filters you own and those shared with you.|
|List of Functions||(Advanced calculated metrics only) Functions are divided into two lists: Basic (used most often) and Advanced .|
|Data view selector||This selector (at the top right) lets you switch to a different data view.|