---
title: Add metric cards
slug: '2040'
canonical_url: https://docs.coveo.com/en/2040/
collection: coveo-analytics
source_format: adoc
---
# Add metric cards
[dashboards](https://docs.coveo.com/en/256/) offer many ways to review the data collected by [Coveo Analytics](https://docs.coveo.com/en/182/) (see [Review and manage dashboards](https://docs.coveo.com/en/1542/)).

You can, among other things, add metric cards to dashboards to quickly evaluate [metric](https://docs.coveo.com/en/263/) values, such as the number of clicks for a city in particular for the current week compared to the previous one.

## Add metric cards in dashboards

. In an existing dashboard, access Edit mode by clicking **Edit** in the upper-right corner.

> **Note**
>
> In a [new dashboard](https://docs.coveo.com/en/1631/), the report is in Edit mode by default.

. In a section, click **Add card to section** to access the **Add a Card** dialog.

> **Tip**
>
> You can also [duplicate an existing card](https://docs.coveo.com/en/1804/) with [copy16px], and then only modify what needs to be different.

. In the **Add a Card** dialog:

.. Select **Metric**.

**Example**

You can create a metric card representing the number of clicks for a city in particular.

![Metric card showing 2846 clicks in Seattle | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/metric-card-showing-manual-query-count.png)

.. In the first input, enter a meaningful **Card title** (for example, `Clicks in Seattle`).

> **Note**
>
> When you leave the box empty and save the dashboard, the card title will be the name of the selected metric (for example, `Click Event Count`).

.. Under **Metric**, click the dropdown menu, and then select one metric to be shown in the metric box (for example, **Click Event Count**). You can do one of the following:

*** Click the links (**Search**, **Click**, and **Custom**) to quickly browse [metrics](https://docs.coveo.com/en/2041/) by event category, and then select the one of your choice.

> **Note**
>
> Custom data can only be leveraged when using the UA Protocol.
> If your Coveo implementation uses the [Event Protocol](https://docs.coveo.com/en/o3r90189/), custom event types shouldn't be added to a report since they won't function as expected.

*** Click **All**, and then use the **Filter** box to find and select the metric of your choice.

.. (Optional) In the **Advanced Settings** section:

*** Click icon:filter-add-2[alt=filter-add-2,width=16], and then [create one or more dimension filters](https://docs.coveo.com/en/2050/) (for example, `City is Seattle`).

*** [[Trend]]When you want to see trend data relative to the previous equivalent period as the one that's currently selected, select the **Display trend data** option.

The trend value appears next to the metric value as a percentage with an up or a down arrow respectively indicating an increasing or a decreasing trend.

![Manual Query Count trend graph showing 12K value | Coveo](https://docs.coveo.com/en/assets/images/coveo-analytics/admin-ua-trend-value.png)

The option is turned off by default, because calculating the trends increases the dashboard complexity and slows down the dashboard generation.
Enable this option when you really want it.

*** When you report on a custom event and on a search or click event (you added a filter or selected a dimension or metric related) at the same time, or on an all event category metric or dimension (for example, Unique User IP and Browser), choose to **Create a relation using** the **Last search** or the **Visit** between the event categories.

> **Notes**
>
> * Select **Last search** in situations where the last query performed by the user is the reason for the custom event.
>  
> For example, in Salesforce, when agents attached a result to a case (`caseAttach`), the last query they made gave them the results they used to do the custom event.
> 
> * Select **Visit** in situations where none of the queries performed by the user during the visit resolved their matter.
>  
> For example, when one of your clients creates a case (`caseCreate`), they, more often than not, tried to get the information they needed by querying on the subject of their matter before doing the custom event.
> You can then use these queries to create knowledge base articles and therefore fill the content gap.
> 
> * The **Create a relation using** parameter has no effect when you report only on search and click events.
> 
> * **Last search** links each custom event to the query immediately preceding (if any) and **Visit** links each custom event to all queries performed during the user visit in which the custom event happened.

.. Click **Add Card**.

> **Note**
>
> Relevance metrics ([Average Click Rank](https://docs.coveo.com/en/2836/), [Search Event Clickthrough](https://docs.coveo.com/en/2837/), and [Relevance Index](https://docs.coveo.com/en/2838/)) values (if any) have a color that represents if the value is good (green), neutral (black), or poor (red) depending on predefined thresholds.
> 
> The predefined thresholds for each metric are the following:
> 
> * **Average Click Rank**: 1-3 = good (green), 3-6 = neutral (black), and > 6 = poor (red)
> 
> * **Search Event Clickthrough**: > 60% = good (green), 40-60% = neutral (black), and < 40% = poor (red)
> 
> * **Relevance Index**: > 0.7 = good (green), 0.5-0.7 = neutral (black), and < 0.5 = poor (red)
>  
> For example:
>  
> ![Metric value colors in metric card | Coveo](:https://docs.coveo.com/en/assets/images/coveo-analytics/metric-value-colors.png)

. Back on the dashboard, click **Save** in the upper-right corner.

## Required privileges


The following table indicates the required privileges to view and edit dashboards from the [**Reports**](https://platform.cloud.coveo.com/admin/#/orgid/usage/reports/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/usage/reports/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/usage/reports/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/usage/reports/)) page and associated panels (see [Manage privileges](https://docs.coveo.com/en/3151/) and [Privilege reference](https://docs.coveo.com/en/1707/)).

Access to dashboards or part of their content may be further restricted as a function of the member (see [Manage access to reports](https://docs.coveo.com/en/1888/) and [Manage permission filters](https://docs.coveo.com/en/1917/)).

[cols="3",options="header"]
|===
|Action
|Service - Domain
|Required access level

|View dashboards
|Analytics - Analytics data  
Analytics - Dimensions  
Analytics - Reports  
Organization - Organization
|View

.3+|Edit dashboards
|Analytics - Analytics data  
Analytics - Dimensions  
Organization - Organization
|View

|Analytics - Reports
|Edit

|Analytics - Administrate
|Allowed
|===