> ## Documentation Index
> Fetch the complete documentation index at: https://help.statisfy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Segments

> Create reusable customer segments based on conditions for use in campaigns, views, and notifications.

Segments let you define reusable groups of accounts or contacts based on specific conditions. Use segments to target campaigns, filter views, and trigger notifications.

### What Are Segments?

A segment is a saved set of filter conditions that dynamically matches records. Unlike static lists, segments automatically update as records change — accounts that meet the conditions are included, and those that no longer match are excluded.

### Accessing Segments

Navigate to **Admin > Settings > Segments**. Admin permissions are required to create and manage segments.

### Creating a Segment

1. Click **Create Segment**
2. Configure the segment:

**Segment Name:**
Enter a descriptive name (e.g., "Enterprise Accounts at Risk", "High-Value Contacts").

**Entity Type:**
Select what the segment filters. Statisfy supports segments on most core entities:

| Entity                | Typical Use                                                                                                               |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Accounts**          | Group customers by ARR, health, renewal date, etc.                                                                        |
| **People / Contacts** | Identify champions, executive sponsors, power users                                                                       |
| **Opportunities**     | Filter deals by stage, amount, close date                                                                                 |
| **Tasks**             | Bucket open, overdue, or high-priority tasks                                                                              |
| **Activities**        | Match specific activity types or sources                                                                                  |
| **Projects**          | Track onboarding or implementation projects                                                                               |
| **Calendar Events**   | Filter upcoming meetings by scope, participants, or account — used by the **Upcoming Meeting V2** trigger in Agent Studio |
| **Documents**         | Filter knowledge-base or rich-text documents by tag, owner, or content — used when targeting document-driven flows        |

**Conditions:**
Add one or more conditions to define which records match the segment.

Each condition includes:

* **Field** — The field to evaluate (e.g., ARR, Health, Renewal Date)
* **Operator** — How to compare (see operators below)
* **Value** — The comparison value

### Operators

| Operator                  | Applies To             | Description                                   |
| ------------------------- | ---------------------- | --------------------------------------------- |
| **Equals**                | All types              | Exact match                                   |
| **Does not equal**        | All types              | Does not match                                |
| **Contains**              | Text                   | Field contains the value                      |
| **Does not contain**      | Text                   | Field does not contain the value              |
| **Begins with**           | Text                   | Field starts with the value                   |
| **Ends with**             | Text                   | Field ends with the value                     |
| **Greater than**          | Number, Date           | Field is above the value                      |
| **Greater than or equal** | Number, Date           | Field is at or above the value                |
| **Less than**             | Number, Date           | Field is below the value                      |
| **Less than or equal**    | Number, Date           | Field is at or below the value                |
| **Is in**                 | Dropdown, Multi-select | Field matches one of the listed values        |
| **Is not in**             | Dropdown, Multi-select | Field does not match any of the listed values |
| **Is not Blank**          | All types              | Field has a value                             |
| **Is Blank**              | All types              | Field has no value                            |

For date fields, additional operators are available:

* **Relative date** — Within the last or next X days
* **Date window** — Within a specific fiscal quarter or fiscal year

### Combining Conditions

Use **AND** and **OR** logic to combine multiple conditions:

* **AND** — All conditions must be true (e.g., Health = At Risk AND ARR > 50000)
* **OR** — Any condition can be true (e.g., Health = At Risk OR Renewal Date \< 30 days)

### Where Segments Are Used

<CardGroup cols={3}>
  <Card title="Campaigns" icon="bullhorn">
    Target email and survey campaigns to a specific segment of customers.
  </Card>

  <Card title="Views" icon="table">
    Use segments as preset filters in account and people views.
  </Card>

  <Card title="Notifications" icon="bell">
    Trigger notification rules based on segment membership changes.
  </Card>
</CardGroup>

### Managing Segments

From the Segments list page:

| Action        | Description                                      |
| ------------- | ------------------------------------------------ |
| **Edit**      | Modify the segment conditions                    |
| **Duplicate** | Copy a segment as a starting point for a new one |
| **Delete**    | Permanently remove the segment                   |
| **Preview**   | See which records currently match the segment    |

<Tip>
  Preview your segment after creating it to verify it matches the expected records. Adjust conditions as needed before using the segment in campaigns or notifications.
</Tip>

<Note>
  Segments are dynamic — the list of matching records updates automatically as data changes. There is no need to manually refresh a segment.
</Note>