> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/segment-dashboard.md).

# Segment dashboard

Where segment dashboards appear, and the scopes that decide it.

## Where segment dashboards appear

A dashboard is not attached to a segment one by one. It declares a **scope**, and the scope decides where it shows up.

| Scope                                        | Where the dashboard is displayed                                                                                                              |
| -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| `home`                                       | The datamart's home page.                                                                                                                     |
| `segments`                                   | The segments page.                                                                                                                            |
| `segments` with segment IDs in `segment_ids` | Only on that specific set of segments.                                                                                                        |
| `builders`                                   | The [Standard Segment Builder](/audience-and-activation/build-your-audiences/segment-reference/segment-builders/standard-segment-builder.md). |
| `builders` with builder IDs in `builder_ids` | Only on that specific set of standard segment builders.                                                                                       |

{% hint style="info" %}
So a dashboard for one particular segment is a `segments`-scoped dashboard carrying that segment's id - not a property of the segment itself. That is why a segment shows no dashboard until someone has built one at the right scope.
{% endhint %}

## Several dashboards at one scope

You can have multiple dashboards at the same scope. If there are several, tabs are created so you can switch between them; with only one, it is displayed without a tab.

{% hint style="success" %}
Prefer several small dashboards over one large one - it prevents too many requests being executed simultaneously.
{% endhint %}

## In the Standard Segment Builder

Dashboards at the `builders` scope update dynamically as you build a segment, which is what lets you see the audience taking shape before saving it. You have none by default; they have to be configured. A template can also carry its own assigned dashboard, so one template visualises data differently from the others. See [Templates](/audience-and-activation/build-your-audiences/segment-reference/segment-builders/standard-segment-builder.md#templates).

## Comparing segments

A segment's dashboards are also where you compare it with another segment, or with all the users of your datamart: each dashboard tab has a **Compare to segment** button. See [Compare segments](/audience-and-activation/analyze-your-data/compare-segments.md).

## Building one

Dashboard construction - sections, cards, the JSON behind them, and the API - is documented in the **Setup & Monitor** section, under *Create a custom dashboard*. Your Account manager can also set them up for you.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Segment metrics</strong></td><td>The figures shown on every segment, with or without a dashboard.</td><td><a href="/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/segment-metrics.md">Segment metrics</a></td></tr><tr><td><strong>Check your audience reach and stats</strong></td><td>What to look at, and in what order.</td><td><a href="/audience-and-activation/analyze-your-data/check-your-audience-reach-and-stats.md">Check your audience reach and stats</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/segment-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.