> For the complete documentation index, see [llms.txt](https://docs.hostinger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hostinger.com/reach/segments.md).

# Segments

Build reusable audiences in Hostinger Reach from contact attributes, tags, and campaign engagement, using AI suggestions or manual conditions.

A segment is a saved set of conditions that selects part of your audience — recently subscribed contacts, people who opened a campaign but didn't click, customers in one country. Campaigns and [automations](/reach/automations.md) send to segments rather than to raw contact lists.

Find them under **Audience** → **Segments**.

Segments are evaluated when you use them, not frozen at creation. A contact that starts matching the conditions is included in the next send automatically.

## Ways to create one

* **Describe it** — choose **New segment**, write the audience you want in plain language (or pick a suggested prompt), and Reach proposes matching conditions for you to review and adjust. This is what you see first when you have no segments yet. Each description uses one of your plan's AI messages — see the [Reach product page](https://www.hostinger.com/reach) for plans.
* **Build it by hand** — choose **New segment** → **Create manually** and add conditions yourself.
* **From a tag** — filter [contacts](/reach/contacts.md) by tag and turn that filter into a segment, or create one directly from the **Tags** page.
* **After a CSV import** — optionally group everything you just imported into a new segment.
* **From an automation** — when a flow needs a segment that doesn't exist yet.
* **From an AI campaign draft** — when Reach drafts a campaign for you, it may create a segment that matches the audience you described.

## Conditions

Each condition combines an attribute, an operator, and a value. A segment can have up to five conditions. Choose **Match all** to include contacts that meet every condition, or **Match any** to include contacts that meet at least one — the choice applies to all conditions in the segment.

| Attribute group         | Attributes                                                                                                                      |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Contact details**     | **Email address**, **Site's Domain** (when the contact synced from a connected site), **Note**                                  |
| **Subscription**        | **Subscription status**, **Opt-in method**, **Subscribed at**, **Unsubscribed at**, **Created at** (when the contact was added) |
| **Origin**              | **Source type** — Manual, Imported, or Synced                                                                                   |
| **Tags**                | **Tag** — has, or doesn't have, a given tag                                                                                     |
| **Campaign engagement** | **Opened**, **Clicked**, **Delivered**, **Processed**, **Bounced**, **Soft bounced**, or **Dropped** — and the negative of each |
| **Custom fields**       | Any [custom field](/reach/contacts.md#custom-fields) you've defined                                                             |

Operators vary by attribute. Email and text fields support **Equals**, **Not equals**, **Contains**, and **Not contains**; **Site's Domain** and **Note** support only **Equals** and **Not equals**. Numbers support **Greater than or equal** and **Less than or equal**. Dates support **On or after** and **On or before**, plus rolling windows — **Within last days**, **Not within last days**, and **Older than days** — which keep a segment current without editing it.

Engagement conditions look across your sending history by default. To narrow them to one campaign, use **Sent campaigns**, which lists your 20 most recent sent campaigns and also covers whether a contact unsubscribed from it.

> **Note:** Contacts still waiting to confirm a double opt-in are matched through **opt-in method**, not subscription status.

## Using a segment

Pick one or more segments as a campaign's recipients, or as the entry condition for an automation. A campaign can also go to your whole audience without a segment — choose **Exclude some segments** to leave specific segments out of that send.

Choose **View** on a segment to see who currently matches it. From there you can search those contacts and export, tag, or delete them. Each segment's menu in the list also has **Edit segment**, **Rename**, and **Delete**.

## Related pages

* [Contacts](/reach/contacts.md) — the data segments filter on
* [Campaigns](/reach/campaigns.md) — choosing recipients for a send
* [Automations](/reach/automations.md) — segment-entry triggers

***

*Last updated: September 25, 2026*