> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/segments.md).

# Segments

This section covers everything you need to know about creating and managing Segments in Reo.Dev, including how to apply the right filters, perform key actions, and create impactful segments to identify high-intent opportunities.

### Guides

* [Creating Segments](/segments/creating-segments.md)
* [Basic & Advance Segments](/segments/basic-and-advanced-segments.md)
* [Filters 101](/segments/filters-101.md)
* [Segment Actions](/segments/segment-actions.md)
* [My Segments](/segments/my-segments.md)
* [Shared Segments](/segments/shared-segments.md)
* [Magic Segments](/segments/magic-segments.md)
* [Configuring Default Segment](https://docs.reo.dev/segments/configuring-default-segment)
* [Favourite Segment](/segments/pinned-segment.md)
* [Add notes for better collaboration and context](/segments/add-notes-for-better-collaboration-and-context.md)
* [CSV Exports for Segments](/segments/csv-exports-for-segments.md)
* [10 Advanced Segments to create to spot high-intent opportunities](/segments/10-advanced-segments-to-create-to-spot-high-intent-opportunities.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://docs.reo.dev/segments.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.