# Stats

A horizontal arrangement of stat entries. Each entry is a simple `{title, description}` pair — title shown above as a label, description below as the value.

Use Stats for the classic KPI strip at the top of a dashboard or report — *Today's Sales: $12,400 / Transactions: 87 / Avg Order: $142*.

![Stats block as a four-tile KPI strip with label-value pairs across the top of a dashboard](/files/0LFyj5Ju6ji7KmjNLskZ)

## Available in

* Page modules
* Order Form modules
* Dashboard modules
* Public Page modules

Stats isn't available in Catalog, Modal, Reports, or Navigation modules.

## When to use

* KPI strips at the top of dashboards.
* Summary counters above a Report Widget.
* Quick at-a-glance numbers paired with labels.

For richer single-metric displays with trend indicators, prefix/suffix, or icons, you'd need a custom build — Stats is intentionally minimal.

## Settings

| Setting   | Description                                                      |
| --------- | ---------------------------------------------------------------- |
| **Items** | Array of stat entries. Each entry has a title and a description. |

Each item has:

* **Title** — the stat's label (shown above).
* **Description** — the stat's value (shown below).

## How it works

Stats renders the configured items as a row of label-value pairs. The container is constrained to a max width of 916px (so very wide layouts don't stretch the stats too thin).

The Description field accepts any text — numbers, currency strings, percentages, dates. It's not formatted automatically; format it the way you want it displayed.

{% hint style="info" %}
For stats that should update dynamically based on session data, use a **Report Widget** with a saved search instead. Stats is for static or pre-computed values.
{% endhint %}

## Examples

**Dashboard KPI strip.** Stats with four items: *Today's Sales / $12,400*, *Transactions / 87*, *Avg Order / $142*, *Items Sold / 312*.

**Report summary.** Stats above a Report Widget summarising the period: *Open Orders / 24*, *Awaiting Fulfilment / 11*, *On Hold / 3*.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Chart</strong></td><td>For visual data representation.</td><td><a href="/pages/TF6MsDgHAeqpfXzQEkOB">/pages/TF6MsDgHAeqpfXzQEkOB</a></td></tr><tr><td><strong>Report Widget</strong></td><td>For dynamic, query-driven data.</td><td><a href="/pages/iL4LHW8eadVrU4Dz2iRe">/pages/iL4LHW8eadVrU4Dz2iRe</a></td></tr><tr><td><strong>Card</strong></td><td>For non-numeric grouped content.</td><td><a href="/pages/CL25ytWkdJL9JVqPKkg2">/pages/CL25ytWkdJL9JVqPKkg2</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/content-components/stats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.