> For the complete documentation index, see [llms.txt](https://docs.pushpushgo.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pushpushgo.company/subscribers/segments.md).
# Segments
{% hint style="info" %}
You can create up to 5 segments in each project.
{% endhint %}
Segments allow you to create conditions based on [Labels](/subscribers/labels.md). The latter determine if a subscriber belongs to a given segment.
Each segment has its properties:
\- **name** - unique within a project
\- **status** (draft, building, or ready) - every created segment is in the ‘building’ status and becomes ‘ready’ after it's calculated
\- **audience** - a precise number of current subscribers in a segment
After defining a segment, the building process begins. It may take a while - we need to scan each subscriber in the base and match them with the segment conditions. When the process ends, the segment switches to ‘ready’. It displays the number of subscribers within it. You can send messages to them.
Every time you change or add labels to a subscriber, it causes changes in the segments. They are rebuilding in real-time, following new subscriber descriptions per labels.
Segments allow you to send a push to a selected group much faster than [other targeting options](/campaigns/push-campaign.md).
You can find segments defined for a project in the Segments view.:
You can search segments by name or sort them, either alphabetically or chronologically (by creation date). The view allows you to delete, copy, and edit segments. You can create a campaign for a given segment with a ‘ready’ status by clicking on a green button with an arrow sign.
Deleting a segment won't be possible if it’s currently used in a planned campaign, a saved draft, or in a campaign that’s being sent. It prevents unnecessary complications and errors in campaigns.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.pushpushgo.company/subscribers/segments.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
