/Docs

Managing Metrics

Metrics are created and managed at the project level, which means you define them once and reuse them across as many experiments as you need. This page covers how to create new metrics, edit existing ones, delete metrics you no longer need, and understand how metrics behave when attached to multiple experiments.

Creating a metric

1

Navigate to the Metrics page

Open your project and click Metrics in the left sidebar. This page lists all metrics that have been created for the current project.
2

Click New Metric

Click the New metric button in the top-right corner of the page. The metric creation panel opens.
3

Choose the metric type

Select from Click, Pageview, or Custom. Each type has different configuration fields. See the individual metric type pages for detailed instructions.
4

Fill in the details

Enter a name and complete the type-specific fields (CSS selector for click metrics, URL pattern and match type for pageview metrics, or just a name for custom events).
5

Save

Click Save. The metric is immediately available to use in experiments.

Choosing how a metric is analysed (the measure). Click, Pageview, and Custom describe what is being tracked. Howthe metric is analysed — as a conversion rate, a per-visitor value, a percentile, a rate, or a composite — is picked separately in the experiment builder's Metrics step. The same Metric can be analysed with different measures across different experiments without re-instrumenting.

Editing an existing metric

To edit a metric, find it in the Metrics list and click on it (or click the edit icon). The same configuration panel will open with the current values pre-filled. Make your changes and click Save.

Edits affect all experiments using this metric
Metrics are shared across experiments. If you change the CSS selector on a click metric that is being used in three running experiments, all three experiments will immediately start using the new selector. Be careful when editing metrics that are attached to active experiments — an incorrect change could cause those experiments to stop recording conversions.

Deleting a metric

To delete a metric, open it from the Metrics list and click the Delete button. You will be asked to confirm before the deletion proceeds.

Cannot delete metrics used in active experiments
A vs B will not allow you to delete a metric that is currently attached to a running or paused experiment. You must first remove the metric from any active experiments, or wait until those experiments are concluded, before you can delete it. This protects the integrity of your running experiments.

Deleting a metric that was used in past (completed) experiments does not remove the historical conversion data from those results. The results pages for completed experiments will continue to show the data that was collected while the metric was active.

Reusing metrics across experiments

One of the key advantages of project-level metrics is reuse. You create a "Purchase Completed" metric once, and every experiment in your project can use it as a primary or secondary metric. This ensures consistency — the same CSS selector, the same URL pattern, the same custom event ID — across all your experiments.

When you create or edit an experiment in the experiment builder, Step 4 (Metrics) shows a searchable list of all project metrics. Select one as the primary metric and optionally add others as secondary metrics.

Keeping metrics organized

As your project grows, the metrics list can become long. A few conventions that help keep things tidy:

  • Use descriptive names — include the element type and context: Pricing Page CTA Click, Signup Form Submit, Checkout Confirmation Pageview.
  • Avoid duplicates — before creating a new metric, search the list to see if one already exists for the same action. Two metrics tracking the same button with slightly different selectors leads to inconsistent data across experiments.
  • Delete stale metrics — metrics that are no longer attached to any experiment and have not been used in months can be safely deleted to keep the list clean.
Tip
Custom event metrics have a short ID that you reference in your JavaScript code. If you delete a custom event metric and recreate it, the new metric will have a different short ID. You will need to update the avsb.track.event() calls in your code to use the new ID.