Skip to main content

Creating and Managing Metrics


Metrics rely on custom events.

Metrics are available to all customers on any plan. However, to run Metrics, custom events must be sent to DevCycle. Every organization receives 5 million free events to start with. Additional events will incur costs, which will be added to your existing plan. To learn more, read about our pricing, or contact us.

This article explains how to create, define, and manage all of the Metrics in a project.

Metrics provide a broad overview of your system. They may be used to quickly assess the health of your features across environments, visualize how quickly people are visiting your applications, or how much memory is being used by your servers as a feature rolls out. Metrics may be known as "Goals" on other platforms.

Within DevCycle, Metrics are their own items outside of a Feature and thus can be defined once and applied to as many features as desired. This gives the opportunity to attach and test Metrics with seemingly unrelated features and find unintended or hidden impacts.

Metrics Section

To view and create Metrics, first navigate to the Metrics section of the Dashboard

Metrics Section no Arrow

This section will contain a list of all of the Metrics on the current project, all of which are re-usable across any number of features at any time. This list contains some simple base info.

Below is a brief description of each column, with deeper explanations later in this document

  • Name - The name of the Metric. This name is the human-readable format of the Metric for easily discussing the Metrics. As explained later, the key is what will be used within the Management API.
  • Type - The "Type" of Metric represents the dimension or calculation used for the Metric. It may be a simple count, or a rate, or an average. These type definitions are described below in "Creating a Metric".
  • Event - This is the name of the event sent by the SDKs or APIs which is being used for this Metric.
  • Date Modified - Simple date explaining the last time someone made any modifications to a Metric which may have changed anything significant to the calculated results.

Creating a Metric

To create a Metric, navigate to the Metrics page as noted above, and click "Create a Metric"

Image of Metrics page with arrow pointing towards create button and tab

Metrics can also be created directly within any Feature from the Experimentation panel.

Upon clicking create, the following modal will show:

Image of empty creation modal

To set up a Metric, the following items are needed:

  • Name - This is the name of the Metric. It should be descriptive enough that any team member viewing it understands it and can both get the information necessary, and also decide if they would like to re-use the Metric for other Features.

  • Key - Like other DevCycle keys, this is how this Metric will be referenced in the Management API and all other non-dashboard interactions with this Metric.

  • Event - This is the EXACT event name that is sent by the DevCycle Track methods of the SDKs or via the DevCycle APIs. This event will be used in all calculations of the Metric. How it is used specifically is described below in How do Metrics get calculated?

  • "Optimize For" - DevCycle represents Metrics as a positive or negative depending on the desired optimization. Often times, tools will always assume that an increase is beneficial. However, in most engineering applications, the opposite is true! Things such as latency, load times, server load, and processing times are Metrics that should be decreased. DevCycle will make obvious whether a Metric is improving in the desired direction, and will soon notify you if a significant impact in either direction has been made.

  • Description (optional) - A meaningful description explaining what this Metric is for and why it is being tracked. In conjunction with DevCycle's Jira Integration, this can be useful for managers to get a greater depth of information when understanding Metrics.

  • Type - The type of a Metric defines how and what it is calculating and represented to the user. This "Type" is currently a set of the items defined below and available in the dropdown.


When making a Metric, the types of Metrics will contain a small definition

Type Definitions

Count per Unique User - This Metric type calculates the total number of times a unique user (or service) has sent this event. This can be something such as total number of clicks on a new feature, total number of API calls for a new service, total number of of views for a new advertisement, etc. This is also useful for error tracking -- A total count of specific errors is a great Metric to count when monitoring the rollout of a new release of a feature.

Count per Variable Evaluation - This type counts the total number of times this event has been seen ONLY when the actual related variable has been evaluated. This is a very useful case, as there may be evens which already exist within your system which could potentially also be impacted by this variable. In this case, this type of Metric represents the exact number of times that event has been sent ONLY after the related variable has since been evaluated for use.

Sum per User (numerical) - Each event can carry a numerical value with it, and this Metric will sum up the total number sent with the events per unique user. This type of Metric is great for tracking things such as Revenue, or number of total items purchased or interacted with. From an engineering view, things such as a total number of api calls per unique user may be something intended to decrease (for optimizations) or increase (for increased interaction).

Average per User (numerical) - Similar to the sum per user, the average for user also uses the numerical value on each event. This type of Metric is extremely useful for tracking things such as the average latency per API call, or average size of an API call, hoping for a decrease. Load times, server load, api latency, or even your own internal build time can be candidates for a Metric which is re-used across every single feature for viewing the impact and reacting accordingly.

Future Types - If there are any types of Metric you'd like to see, or if your team would like a more flexible view into all of your data, do not hesitate to reach out to [email protected]. We will be increasing the number of types, as well as providing direct calculation control in the future. If such things are desired now, contact us to discuss direct data access, which will provide full access to all events and data for each of your projects.

Metric Details Page

After creating a Metric, or by clicking on one from the Metric list, you will be navigated to the Metric Details page. This page has the following sections.

Metric Definition

The Metric definition allows for modifying the Metric Name, Type, Definition, and Optimization.

Metric Testing

This section provides the ability to test a Metric against any feature in any environment and ensure it is working as intended.

It is also useful to use this testing section to quickly check a Metric against any given Feature to potentially find any unintended impacts if the Metric is not associated with a specific Feature.

When testing a Metric, navigate to the Testing section.

Metrics Testing Section

To run a test, the following fields must be set:

Feature - This is the specific feature this Metric should be applied to. Any event that has been sent since the creation of this Metric from a user receiving any variation of this feature will be part of this Metric. In the event that an error is shown, this means the event has not been seen from this feature yet.

Control - After selecting a Feature, a "control" variation must be selected. This is what will be used to show a comparative analysis against all other variations in a feature. Typically, an "off" or "Baseline" variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation.

Date Range - This range will default from the moment the Metric (or feature) was created, to now within 30 days. If 30 days have passed since the creation of the Metric or feature, the date range must be a 30 day range.

Environment - This will calculate the Metric using events from the specified environments.

Once these fields are set, the test can be ran by clicking the test button, resulting in a test result.

(For these documents, our own internal Metrics testing at this time were used!)

Metrics Testing Section with the button to an arrow

The results of this test will show the actual result which would be within a Feature if this Metric was associated with it!

Attaching Metrics to Features

Tracking metrics within a feature is an important aspect of data analysis, as it can provide valuable insights into the performance and behaviour of different features. Once a Metric has been created, it can be attached to any feature for use and analysis.

Here are some steps you can follow to track metrics within a feature:

  1. Select the feature you want to track: Within that feature, navigate to the Data & Results section of the page and click on Comparative Analysis.

    Comparative Analysis tab within a DevCycle feature's Data & Results view

  2. Choose the metric(s) associated with the feature: Create new metrics or attach existing ones to the feature by navigating to the Choose a Metric dropdown.

    Choose a Metric dropdown menu

  3. Attach the metric(s): Attach the metric from the dropdown menu by selecting it. For our example, let's use the metric Metric Testing, which has already been setup within our project.

    "Metric Testing" metric selected from the metrics dropdown

  4. Calculate results: Once one or more metrics have been selected, we can then run the metric calculation to generate insight into how the feature is doing.

    Feature metrics ready to be calcuated

    While the setup has some default values, the Metric requires the following fields to be filled:

    • Control - This is what will be used to show a comparative analysis against all other variations in a feature. Typically, an "off" or "Baseline" variation would act as the control. For more information on this, please refer to the Feature Experimentation documentation.

    • Date Range - This range will default from the moment the Metric (or feature) was created, to now within 30 days. If 30 days have passed since the creation of the Metric or feature, the date range must be a 30 day range.

    • Environment - This will calculate the Metric using events from the specified environments.

Once these fields are set, the calculation can be ran by clicking the calculate button, which will run for all Metrics for the Feature.

Arrow pointing to calculate button on Metric

Once calculated, if there is available data for the Feature, the results data will populate within the dashboard.

Calculation results

From here, useful information such as trends and patterns in the data can be used to make informed decisions about how to optimize the feature for performance improvements.

How do Metrics get calculated?

To calculate Metrics, DevCycle uses the custom events sent via its API or SDKs. Each Event has the information of which user sent it and which Feature and Variation they were in at that time. For optimal experiments, use Features with variations randomly distributed across users.

To read more on the queries behind the Metrics, see How Metrics Are Calculated

Running Experiments

With Metrics on a feature, experimentation can be easily executed on any Feature. At DevCycle we believe that experimentation should be a part of the natural lifecycle of all features. So no matter the feature type selected, experimentation will always be available for use.

To learn more on how to run experiments with DevCycle, read Feature Experimentation