> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/audience/creating-segments.md).
# Creating Segments
The How and Why of creating segments
Segments are one of the most important aspects of your Gleantap account. Everything from campaigns to automations is built upon segments and building your audience groups.
For this article, we will start with the basics: How to Create and Configure your segments.
The first thing you need to know is where to find the segment builder. You can do so by clicking on Audience on the left-hand side and then Segments.
Next, follow the below steps to create your segment.
Step 1: Navigate to Audience > Segments from the sidebar.
Step 2: Click on the green '+' button on the top right of the screen.
Step 3: Enter a segment name, and then indicate if the segment is Static or Dynamic. A static segment will not change size, while a dynamic segment will change size based on the criteria set.
Step 4a: Click on the 'Add Filter' button to start adding criteria for the segment.
Step 4b: In the flyout, select a filter category to see specific criteria that can be added. More on this here.
Step 5: When done making your segment, click Calculate, and then Save.
---
# 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://help.gleantap.com/audience/creating-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.
