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

# Segments

Build dynamic lists of products that meet conditions such as category, status or completeness, also for API keys or exports.

Segments are a feature of the system that allows you to easily create a list of products that meet specific conditions. Some examples:

* Attribute has value,
* Product completeness,
* The product belongs to a category,
* Product has status,
* Product type.

Segments are also used to make a set of products that can be assigned to a specific [API key](https://usermanual.ergonode.com/system/settings/api-keys.md).

{% hint style="info" %}
Segments are dynamic, which means that any changes in the product will be taken into consideration while evaluating segment conditions. That means that if you change anything in the product, segments will be recalculated and the number of products included in them may change automatically. This is done automatically and in the background, so having a lot of segments and lots of products may decrease performance, and you will need to wait a while till segments are recalculated.
{% endhint %}

A list created this way can also be used, for example, to send only some products via API, or be used with a module to [export a file in the .csv format](https://usermanual.ergonode.com/system/ergonode-transfer/exports/creating-a-new-export.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://usermanual.ergonode.com/products/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.
