> 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-details.md). # Segment details Segment details show a segment's definition, size, engagement and reachable users per channel. The detail page is the single view of one segment: what it is, how big it is, how engaged those users are, and how many of them you can actually reach on each channel.

Open it from the segment list with **View** in the row action menu, or by clicking the segment name. **Path:** `Targeting > Segments > View`

### Header The title shows the segment name with its ID, followed by: * **Status** — Ready, Calculating, or Not Active. * **Type** — Standard, Predictive, Product, or Connector. * **Created by** — who built the segment. * **Last updated** — when the audience was last recalculated. Segments are recalculated automatically every three hours. Check the status and the update time first. A recent update time confirms the audience reflects current data; an update time older than the three-hour cycle is worth checking before you rely on the audience. ### Metric cards

Metric	What it tells you
Total users	How many users matched the rules at the latest calculation.
Avg. click rate	How often this audience clicks the messages it receives.
Monthly app opens	How often these users open the app in a month.
Monthly revenue	The revenue this audience contributes in a month.

These describe the audience, not a campaign. They cover the people in the segment across all the messaging they receive, so they answer “is this a good audience to talk to” rather than “how did my last send perform” — that belongs in campaign reports. Use them to compare audience quality before committing to a campaign. A segment with high app opens tolerates more frequent messaging; one with a low click rate usually needs a different offer or a different channel rather than more sends. ### Reachability by channel Reachability breaks the audience down by channel — iOS, Android, Web, SMS, Email, and WhatsApp — as a user count and a share of the segment. This is the number that decides whether a campaign is worth building. Total users counts everyone matching the rules; reachability counts those who can receive the message on the channel you have in mind. A segment can be large and still be almost unreachable by email. The shares do not add up to 100%. Each channel is measured against the whole segment, and one user can be reachable on several at once. {% hint style="info" %} A channel at 0 usually means the audience never granted permission on it, or the channel is not enabled for the app. {% endhint %}

If reachability is too low for the channel you need, the fix is usually a permission rule rather than a bigger audience: add **Channel Permission** to the segment so it only holds users you can actually reach there. ### Targeting rules The rule logic is restated in plain language, the same wording shown while the segment was built. Use it to confirm the segment still describes the audience you intended. A segment with no filter rules shows **No rule created** and includes every user in the app. ### Actions From the segment you can: * **Send message** — start a campaign with this segment already selected. * **Edit** — reopen the rules in the builder. The change applies to the segment itself, so anything already targeting it follows the new definition from the next calculation. * **Export users** — export the audience; the file is emailed to you.

### Quick checks before you act * Is the status Ready and the update time within the three-hour cycle? * Does the user count match what the rules should produce? * Is the audience reachable on the channel you plan to use? * Do the engagement metrics support the campaign idea? For the full list and management view, see [Segment list](/netmera-user-guide/targeting/segments/segment-list.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://user.netmera.com/netmera-user-guide/targeting/segments/segment-details.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.