> 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.md).

# Segments

Segments are reusable audiences built from behavior, profile, tag, response, platform and location rules.

A segment is a reusable audience definition. You describe who belongs to it with filter rules — behavior, profile attributes, tags, message responses, platform, location — and Netmera keeps working out which users match.

Once a segment exists, you select it by name wherever an audience is needed: campaign targeting, journeys, and analytics. The rules live in one place, so a change to the definition reaches every campaign that uses it.

**Path:** `Targeting > Segments`

### Segment types

The list holds every segment in the app, whatever created it. The **type** filter separates them:

<table><thead><tr><th width="142.57421875">Type</th><th>Where it comes from</th></tr></thead><tbody><tr><td><strong>Standard</strong></td><td>Built by hand from filter rules on the Create Segment screen.</td></tr><tr><td><strong>Predictive</strong></td><td>Generated by an AI model that scores users on how likely an event is.</td></tr><tr><td><strong>Product</strong></td><td>Built around product or catalog data.</td></tr><tr><td><strong>Connector</strong></td><td>Synced in from an external tool through a connector.</td></tr></tbody></table>

### Start here (most-used topics)

<table data-view="cards"><thead><tr><th>What you want to do</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Browse, filter, and manage the segment list</td><td><a href="/netmera-user-guide/targeting/segments/segment-list.md">Segment list</a></td></tr><tr><td>Build a new segment from filter rules</td><td><a href="/netmera-user-guide/targeting/segments/segment-list/create-a-segment.md">Create a segment</a></td></tr><tr><td>Inspect one segment and its audience</td><td><a href="/netmera-user-guide/targeting/segments/segment-details.md">Segment details</a></td></tr><tr><td>Import or sync segments through connectors</td><td><a href="/netmera-user-guide/targeting/segments/connector-segments.md">Connector segments</a></td></tr><tr><td>Predict who will convert or churn (AI-based)</td><td><a href="/netmera-user-guide/targeting/segments/predictive-segments.md">Predictive segments</a></td></tr></tbody></table>

### Quickstart: build a segment you can target

{% stepper %}
{% step %}

#### Start from the question you want to answer

Examples:

* “Who opened the app in the last 30 days?”
* “Who has an email address on file?”
* “Who added to cart but did not purchase?”
  {% endstep %}

{% step %}

#### Click Create Segment

Name the segment and describe what it is for. The description is what the next person reads before reusing it.
{% endstep %}

{% step %}

#### Add filter rules

Pick a filter category, then the value. Combine several rules in a group with **AND** or **OR**, and add more groups when the logic needs nesting.
{% endstep %}

{% step %}

#### Check the audience before saving

**Rule Description** restates your rules as sentences, and **Calculate exact size** returns the real number of users the rules match.
{% endstep %}

{% step %}

#### Save and use it

Saved segments are selectable in campaign targeting, journeys, and analytics filters.
{% endstep %}
{% endstepper %}

### How a segment stays current

A segment stores rules, not a fixed list of users. The membership is resolved by calculation, so the number you see is the result of the last run rather than a live count.

* **Update Date** in the list tells you when that run happened.
* **Refresh** forces a new calculation when you need the audience to reflect something that just changed.
* **Pause** stops recalculation and moves the segment to **Not Active**. The definition is kept, so resuming picks up where it left off.

This is why a rule change reaches every campaign using the segment: campaigns reference the segment, and the segment resolves to users at calculation time.

### Key concepts

* **Filter rule** — one condition, such as a behavior, a profile attribute, or a channel permission.
* **Filter group** — a set of rules joined by **AND** or **OR**. Groups are what let a segment mix both operators.
* **Rule Description** — the plain-language restatement of the rules, shown while you build.
* **Audience size** — the number of users matching the rules, on demand rather than continuously.
* **Reachability** — how many of those users can actually be reached on each channel.
* **Tags vs segments** — tags are static labels you attach to users; segments are rules that resolve to users.

Related: [Tags](/netmera-user-guide/targeting/tags.md).

### Related prerequisites

Segments can only filter on data Netmera already holds. Before a rule can work, the underlying data has to exist:

* Behavior and Response rules need tracked events — see [Events](/netmera-user-guide/customer-data/events.md).
* Profile Attribute rules need attributes collected on the user — see [Profile attributes](/netmera-user-guide/customer-data/profile-attributes.md).

If a rule returns nobody, the data behind it is the first thing to check.


---

# 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://user.netmera.com/netmera-user-guide/targeting/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.