> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/admin-and-settings/taxonomy/segments.md).
# Segments
## Overview
The **Segments** taxonomy page is where you manage all Segment records in Birdie Settings.
Segments are one of the core taxonomy types in Birdie. They let you group feedback or customers by shared characteristics so teams can analyze data with more context.
This page centralizes the operational work of managing Segments as taxonomy items. Use it to review your catalog, create new Segments, and organize them into collections.
If you want the conceptual definition of Segments and how they are used in analysis, see [Segments](/core-concepts-and-entities/segments.md).\
## Viewing & Searching
The main tab shows the full Segment catalog as a list.
Each row includes:
* **Taxonomy ID**, such as `[SG-012]`
* **Segment name**, such as `Premium customers`
Use this view to review the segmentation structure already available in your workspace.
## Creating New Data
Click **New segment** to create a new Segment.
When creating a new Segment:
1. Give the Segment a clear and recognizable name.
1. Define the filter that represents this segment.
2. Save it to add it to the catalog.
Use names that clearly describe the audience, behavior, or profile being grouped.
## Collections Tab
The second tab groups Segments by **Segment collection**.\
This view is useful when you organize Segments by dimension, such as lifecycle, firmographics, usage, or plan type.
Use collections to:
* separate different segmentation dimensions
* keep analysis cleaner
* make comparisons easier inside the same group
For deeper guidance, see [Organizing Segments with Collections](/customer-intelligence/exploration-and-analysis/organizing-segments-with-collections.md).
## Best Practices
* Keep each Segment tied to one logic.
* Use consistent naming across collections.
* Avoid creating overlapping segments without a clear purpose.
* Group related Segments into the same collection.
## Related Articles
* [Taxonomy](/admin-and-settings/taxonomy.md)
* [Segments](/core-concepts-and-entities/segments.md)
* [Organizing Segments with Collections](/customer-intelligence/exploration-and-analysis/organizing-segments-with-collections.md)
---
# 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://ask.birdie.ai/admin-and-settings/taxonomy/segments.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.
