Skip to main content

Creating custom metrics

Company admins can define custom metrics for your company.

Written by Nona Vikman
Updated over a week ago

You can find custom metric builder from settings->Custom metrics:

Creating a new metric

To create a new metric, click on "Add custom metric" or make a copy on an existing metric. Give the metric a name (in all languages relevant to your company), and give it a definition (also in all necessary languages). The metric description should explain what is being calculated and with which filters. You can also explain the intended use cases for the metric, and name the creator, campaign, team, or store this metric is relevant for. Inthe future, the better your definition, the better our AI analyst can include your metric in its analyses.

Defining the formula

Next you need to create the formula. The options available are following: You can use any default metric, other custom metrics and constant values as the basis for your calculation. You can also do calculations between actual values, and, for exaple, Budgeted values. You can place filters on all metric values either to one, or any of your operands. And you can do multi-level operations, where the metric group decides the calculation order of your formula.

Next we will look at different types of formulas possible.

Formula types

Filtered metric

If your end goal is a single, filtered metric, without any operations, you start by choosing either a metric or a constant. Then you select a time series type (eg. Actual or budget), and then you apply filters is necessary.

Single metric can be used if you often need to exclude a certain parameter from your sales figures. Eg. if your webstore sales are always booked under a certain sales rep's account, you can create a metric "Brick and mortar sales" by simply creating a single metric and filtering out that particular sales rep.

Or if you want to create a filtered column in a table report (for example to be able to display certain category's sales on the side of total sales), you can do a filtered metric and use that metric in the table in addition to the "normal" sales metric.

Sum

This formula can be used for example in cases where you want to group costs together to create a metric such as: Wages + Salaries = Personnell costs

Subtract

Same as above, but other way around. Sales (w/o tax) - Costs of Goods Sold = Gross profit.

Multiply

Let's say you are selling pizza by slices, and you want to create a metric "Number of whole pizzas sold". If you have 8 slices in in one pizza, and all of your pizza slices have the word "Slice" in the product name, you could create the metric like this:

Units sold (or Sales (pcs)) Filtered by %Slice% in the field "Product name" * 8

Divide

There are many use cases for division formulas.

Calculating efficiency:

  • Sales (w/o tax) / Full time employees = Sales €/$/£ per FTE

Calculating averages:

  • Amount of orders / Sales days = Average daily order amount

Calculating proportional sales:

  • Sales (w/o tax) filtered by category "accessories" / Sales (w/o tax) = Accessory sales' proportion out of total sales

Calculating Margins:

  • Sales margin € (w/o tax) / Sales (w/o tax) = Sales margin %

Doing daily averages in a several-week period, when grouping is a weekday (e.g. siix week period):

  • Sales (no Tax) / 6 = Weekday average in a several week period

Multi-level calculations

You can now do do multi-step formulas in one custom metric, eg, if you want to sum up two things before dividing them with something else.

After you salect the first metric you can either add operation, or create a new group. The difference is the calculation order.

If you want your formula to be (Sales-CoGS)/Sales then select the sum button from the "Add operation" buttons, and the division button from the "Add operation (create new group)" buttons.


In case the calculation order does not matter (eg. addition or muptiplication only calculations), you can just use the "add operand" option.

Metric settings

Metric group

This selection defines, where your new formula will be listed in the Metric dropdown menus when eg. creating a new report.

Format

This selection defines how the resulting values of your metric will be displayed on reports. In the cases of single metric, sum, and subtraction you should use the format the base metrics for your calculation use (and of course it is a good practice to not sum or subtract metrics with formats that differ from another). For division calculation the format will depend on your end goal:

  • Is the result an average, or efficiency metric? -> use numeric (money or amount) depending in which format your Dividend is

  • Is the resulting metric a proportion or a margin? -> Use percentage format

Aggregation method

Defines how the values are summed up on the total rows of tables. In most cases monetary and unit values are aggregated with sum, where as division calculations, such as proportion metrics or margins should be aggregated with an average.

Decimals

The amount of decimals shown in the report for your metric when the results are rounded: By default, if the "Rounded" option on a table report is not ticket, 2 decimals are shown, but if you select "2" as the number of decimals when creating the metric, ticking the "rounded" option in tables will not affect the amount of decimals on your metric.

IMPORTANT TO NOTE!

Any changes you make to a metric will affect all the reports where that metric is used. So if you delete a metric, all the reports in which you or some one from your organisation have used that metric, will not function properly.

Troubleshooting

Sometimes it takes a while for a new metric to become visible on reports. If you want to use the metric instantly, you should refresh your browser before trying to add the metric to a report or dashboard.

The names of metrics can also appear strangely on the reports in the next few minutes after createing the metric, so allow a few minutes or refresh your browser again for the metric names to appear correctly.

You can watch the latest how-to-video from here:

Did this answer your question?