> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/main-features/members/segments.md).

# Segments

Members can be grouped into Segments based on their data, transactional data, or loyalty program behavior. Segments can be configured by the Administrator in the Segments module or sourced from external 3rd party systems [through API](https://apidocs.openloyalty.io/). Users are added to Segments automatically after meeting the requirement of being in a given Segment. Thanks to this, you can automate the processes of loyalty program management and those related to personalizing loyalty offers and facilitating marketing communication.

***

## Segments module overview

The Segments module contains all the functions related to segmentation. In this section, you can create Segments to which your Members will be assigned, change the Segment configuration, or download a list of Members assigned to a Segment.\
This is one of the main functionalities of our service, based on which you can add e.g. marketing activities.

<figure><img src="/files/wPzJrGPDhF32xBolRYfp" alt=""><figcaption></figcaption></figure>

***

## Browsing the Segment list

In the main-view table which contains the list of all Segments, you will find data with basic information about them.

<figure><img src="/files/wPzJrGPDhF32xBolRYfp" alt=""><figcaption></figcaption></figure>

* **Name** - Name of the Segment
* **Members** - number of added customers
* **Avg. transaction value** - average Transaction amount
* **Avg. number of transactions** - average Transactions
* **Avg. spending** - average spending
* **Created on** - the date when the Segment was created

For a more detailed overview of all Segments, you can search via name and/or use filters. They will help you find the Segment which has the data you are looking for.

#### Table Search by name:&#x20;

<figure><img src="/files/Gy6vdbFngOOTJqA7WCSH" alt=""><figcaption></figcaption></figure>

Once you start typing the name, the results will change automatically.&#x20;

#### Filters you can use:

* Active
* Avg. CLV
* Avg. number of transactions
* Avg. transaction value
* Created on
* Description
* Members
* Name

You can use one filter, or create and use several filters at the same time.

<figure><img src="/files/torRY9bVnf9IN62Wo5oX" alt=""><figcaption></figcaption></figure>

#### Sorting the Segment list

Sorting data is used when you (an Admin) would like to sort the Segments by specific data. This includes:

* **Name**
* **Members**
* **Avg. transaction value**
* **Avg. number of transactions**
* **Avg. CLV**
* **Created on**

#### As an Administrator, you can perform certain actions on the Segments. The actions you can take:

* Activate/deactivate Segment
* Edit Segment
* Remove Segment
* Download Members list


---

# 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://help.openloyalty.io/main-features/members/segments.md?ask=<question>&goal=<endgoal>
```

`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.
