> 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** — write the audience you want in plain language and Reach proposes matching conditions for you to review and adjust. This is the default path when you have no segments yet.
* **Build it by hand** — 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.

## Conditions

Each condition combines an attribute, an operator, and a value. Conditions are joined with **AND** (all must match) or **OR** (any may match).

| Attribute group         | Examples                                                                                            |
| ----------------------- | --------------------------------------------------------------------------------------------------- |
| **Contact details**     | Email address, site's domain (when the contact synced from a connected site), note                  |
| **Subscription**        | Subscription status, opt-in method, date subscribed or unsubscribed                                 |
| **Origin**              | How the contact was added — manual, import, or sync                                                 |
| **Tags**                | 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. Text supports *equals*, *contains*, and their negatives; numbers and dates support *at least* and *at most*; dates also support rolling windows such as *within the last N days*, which keeps a segment current without editing it.

Engagement conditions look across your sending history by default, or you can narrow them to specific sent campaigns.

> **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.

## 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: August 26, 2026*