> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/targeting/segments/segment-list.md). # Segment list Find segments in the segment list, check status and size, and act on them without opening each one. The segment list is the management view for every segment in the app. Use it to find a segment, check whether it is ready, see how big it is, and act on it without opening it. **Path:** `Targeting > Segments`

### Find a segment Three controls narrow the list, and they work together: * **Search by name** — matches on the segment name. * **Type** — All types, Standard, Predictive, Product, or Connector. * **Status** — All, Ready, Calculating, or Not Active.

### Columns

Column	What it tells you
ID	The segment's numeric identifier, used when referring to it across the panel.
Name	The segment name. Sortable.
Users	How many users are in the segment as of the latest calculation. Sortable.
Message Sent	How many messages have been sent to this audience. Sortable.
Type	Standard, Predictive, Product, or Connector.
Status	Ready, Calculating, or Not Active.
Update Date	When the segment was last calculated. Segments are recalculated automatically every three hours. Sortable.
Actions	The action menu for that row.

{% hint style="info" %} **Status meanings** * **Ready** — the audience is calculated and the segment can be used in targeting. * **Calculating** — Netmera is resolving the rules, as it does automatically every three hours and whenever Refresh is used. The user count is not final yet. * **Not Active** — the segment is paused and is not being recalculated. {% endhint %} Read **Users** together with **Update Date**. The count comes from the latest calculation, which runs every three hours. An Update Date older than that cycle is worth checking before you rely on the audience, and **Refresh** brings in changes from the last few hours when a send cannot wait for the next run. ### Expand a row for a quick summary Click the **+** at the start of a row to open an inline summary without leaving the list. It shows: * **Description** — what the segment is for. * **Owner** — who created it. * **Reachability by channel** — how many users are reachable on iOS, Android, and Web, as a count and a share of the segment. * **Targeting rules** — the rule logic in plain language. The same panel carries **Send message**, **Edit**, **Export users**, and **Full preview** — the last opens the segment's own page, where the breakdown covers every channel rather than the three device platforms shown here.

Use the expanded row when you want to confirm you picked the right audience. Reachability is the more useful number before a campaign: a segment of 1,000 users with 30 reachable on email will not carry an email campaign. ### Row actions The **…** menu at the end of each row holds:

Action	What it does
View	Opens the segment detail page.
Edit	Opens the segment in the builder so the rules can be changed.
Send message	Starts a campaign with this segment already selected as the audience.
Export users	Exports the users in the segment. The file is emailed to you.
Refresh	Recalculates the audience now, instead of waiting for the next scheduled run, which happens every three hours.
Pause	Stops recalculation. The segment moves to Not Active.
Delete	Removes the segment.

{% hint style="info" %} **Editing a segment already in use** **Edit** changes the definition, not a copy of it. Campaigns and journeys reference the segment by name, so the next calculation changes who they target. When the current audience must stay untouched, build a new segment instead of editing the one in use. {% endhint %} {% hint style="info" %} **Two different exports** **Export users** here exports the audience of a saved segment. **Export audience** on the [Create Segment](/netmera-user-guide/targeting/segments/segment-list/create-a-segment.md) screen exports the users matching rules that have not been saved yet. Both run in the background and email the file. {% endhint %} ### Before you use a segment in a campaign * Is the status **Ready** rather than Calculating? * Does the user count look like what the rules should produce? * Is the audience reachable on the channel you plan to use? * Is the update date recent enough for the campaign you are about to send? ### Best practices * Name segments like queries: `inactive_30d`, `buyers_last_7d`, `cart_abandoners_24h`. * Fill in the description. It is the only context the next person gets from the list. * Keep rules focused — every extra condition narrows the audience in a way someone will have to reverse-engineer later. * Refresh before a send when the audience has to include changes from the last three hours. --- # 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://user.netmera.com/netmera-user-guide/targeting/segments/segment-list.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.