> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/segments/breakdowns.md).
# Breakdowns
Understanding your audience composition is essential for optimizing your targeting strategy. With the **Segment Breakdown Insights**, you can now analyze how different criteria shape your segments in real-time.
This feature allows you to visualize field distributions directly within the Segment Builder, making it easier to refine your audience selection.
## How to check breakdowns
### In the segment builder
* Open the **Segment Builder**.
* Select or create a segment.
* Click on the Breakdown tab.
* Click on **Add Breakdown** to analyze a specific field.
* Choose the field you want to break down (categorical).
* Select a chart type that best represents the data.
* Toggle between percentage or absolute values for better insights.
* Click on Add Breakdown to see an other distribution.
### Once the Segments have been created
* **Navigate to your segment**: go to the Segments section in DinMo and click on the segment you want to analyze
* **Access the Analysis tab**
* **Go to the Breakdown tab**
* Click on **Add Breakdown** to analyze a specific field.
* Choose the field you want to break down (categorical).
* Select a chart type that best represents the data.
* Toggle between percentage or absolute values for better insights.
## Troubleshooting
* Make sure the field you want to breakdown with is categorical. To do so, go to the parent model schema and change the field to the Categorical type.
---
# 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.dinmo.io/segments/breakdowns.md?ask=&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.
