> For the complete documentation index, see [llms.txt](https://helpdesk.smaply.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.smaply.app/metrics/how-to-choose-a-metric-type.md).

# How to choose a metric type

The type you pick decides how a metric's data is shaped and how it renders on a card. You choose it from the **Type** dropdown in the metric builder, after you name the metric and pick a source. For the full build flow, see [How to create and configure a metric](/metrics/how-to-create-and-configure-a-metric.md).

<figure><img src="/files/lJKk4YOlBsdeSw1xW5pa" alt="The Type dropdown in the metric builder, open to show three options: Series, Number, and Comparison, each with an icon."><figcaption><p>The Type dropdown in the metric builder</p></figcaption></figure>

There are three types. Match the type to the question your data answers.

#### Series

A sequence of data points, such as monthly signups or responses broken down by category. Pick Series when you have many values to plot and you want to show a trend over time or a breakdown across categories.

Series data renders as a **Bar**, **Horizontal bar**, **Pie**, **Line**, or **Table** chart, chosen in the card options. A line chart suits a trend over time; bars and pie suit category breakdowns; a table suits exact figures.

<figure><img src="/files/ijXPgXMxxj9YVms7XehV" alt="A metric card rendering Series data as a line chart, showing a monthly trend with a data-point tooltip."><figcaption><p>Series rendered as a line chart</p></figcaption></figure>

#### Number

A single standalone value, such as current CSAT or total revenue. Pick Number when you want to spotlight one headline figure.

A Number renders either as the value on its own, or as a semi-circular gauge that shows the value against an optional target. Use the gauge when the figure is most meaningful relative to a goal.

<figure><img src="/files/t5bzb1TVmj9ZSiNyCV0J" alt="A metric card showing a single value on a semi-circular gauge, with the value positioned against a target range."><figcaption><p>Number rendered as a gauge against a target</p></figcaption></figure>

#### Comparison

Two values contrasted, such as this quarter against last. Pick Comparison when the story is the change between exactly two figures.

A Comparison renders as a value with a percentage-change line below it, or as two bars side by side. The percentage line shows the direction and size of the change at a glance.

<figure><img src="/files/1NAtMf1qAsLHqJ3k749V" alt="A metric card showing a single value with a percentage-change line below it, indicating a decrease."><figcaption><p>Comparison rendered with a percentage-change line</p></figcaption></figure>

#### Which type should I use?

|                | **Series**                               | **Number**                          | **Comparison**                                   |
| -------------- | ---------------------------------------- | ----------------------------------- | ------------------------------------------------ |
| **Best for**   | Trends over time or category breakdowns  | One headline figure                 | The change between two values                    |
| **Data shape** | Many data points                         | A single value                      | Exactly two values                               |
| **Renders as** | Bar, horizontal bar, pie, line, or table | A value or a gauge against a target | A value with a percentage change, or paired bars |

The type also sets which render options are available: Series gives you the five chart types, Number gives you the value or gauge, and Comparison gives you the percentage line or paired bars. You can change the render in the card options at any time. Once a type fits, build the metric in [How to create and configure a metric](/metrics/how-to-create-and-configure-a-metric.md).

<figure><img src="/files/TlFhbsiuEEdexwL9GAVB" alt="A metric card on a journey map rendering Series data as a vertical bar chart titled Website signups."><figcaption><p>A Series metric on a card</p></figcaption></figure>

#### Related topics

<table data-column-title-hidden data-view="cards"><thead><tr><th>Article</th><th>What it covers</th><th data-hidden data-card-target data-type="content-ref">Target</th></tr></thead><tbody><tr><td><strong>How to create and configure a metric</strong></td><td>Build a metric from name to saved card, for any source and type.</td><td><a href="/pages/UlZ0vwT23WaSlpB6ae7r">/pages/UlZ0vwT23WaSlpB6ae7r</a></td></tr><tr><td><strong>How to use manual metrics with CSV</strong></td><td>Enter Series data by hand, paste from a spreadsheet, or upload a CSV.</td><td><a href="/pages/S51TFnU5zyHLVAwsRNUD">/pages/S51TFnU5zyHLVAwsRNUD</a></td></tr><tr><td><strong>How to use metric cards</strong></td><td>Display a metric on a journey map and switch its chart type per card.</td><td><a href="/pages/598LDg8aKf90gVjRC9GG">/pages/598LDg8aKf90gVjRC9GG</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.smaply.app/metrics/how-to-choose-a-metric-type.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.