> ## Documentation Index
> Fetch the complete documentation index at: https://launchdarkly.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Metric impact

<View title="Developer" />

<View title="Federal docs" />

<View title="EU docs" />

This topic explains how to use the metric **Impact** tab.

## The metric Impact tab

The metric **Impact** tab displays a list of complete experiment iterations that used the metric. Any experiment iterations that are currently running do not display on this list. This helps you understand how different flag variations have impacted the metric as part of your Experimentation program.

This list includes:

* The name of the experiment or flag the metric was attached to.
* The date the experiment iteration or guarded rollout ended.
* The variation that was served after the experiment iteration or guarded rollout ended.
* The relative difference from control, which is the difference in performance between the variation being tested and the control variation.

![The metric Impact tab.](https://mintcdn.com/launchdarkly/Y_qcqLWSC5ccm6eB/images/__LD_UI_no_test/metric-impact-tab.png?fit=max\&auto=format\&n=Y_qcqLWSC5ccm6eB\&q=85\&s=75caaecda0655e82db51f987ffc72880)

The metric Impact tab.

> You can also use the REST API: [Get metric](/docs/api/metrics/get-metric.md)

To refine your analysis, you can [apply metric event filters](/docs/home/metrics/event-filters.md) to a metric to limit which events are included in impact calculations. This is helpful when you want to measure the effect of a flag variation for events with specific context attributes, such as users where `country` = `CA` or `plan` = `enterprise`.