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

# Segments and saved filters

> Filtered contact sets for campaigns and reporting.

A segment is a saved filter, not a separate list you maintain by hand. Build a filter once on the contacts list, save it, and it re-runs live every time you open it — it's a query, not a snapshot.

## What you can filter on

<CardGroup cols={2}>
  <Card title="Standard fields" icon="id-card">
    Name, email, phone, identifier, country, city, created date, last activity, company, blocked status.
  </Card>

  <Card title="Labels" icon="tag">
    Whatever tags you've applied to contacts — the one filter type that isn't a plain field on the contact itself.
  </Card>
</CardGroup>

## Managing a segment

A saved segment is a name and a query — nothing else is frozen at save time. Editing one changes what it returns going forward; you're not creating a new version alongside the old one. Deleting it just removes the saved shortcut — it was never the only way to reach those contacts, since the same filter can always be rebuilt from scratch on the contacts list.

## Segments are one of three filter types

The same saved-filter mechanism backs three different things: filters on contacts, filters on conversations, and filters used for reporting. "Segment" is specifically the contacts one — the dashboard's name for a contact filter you've chosen to save. A saved conversation filter is the same underlying idea, covered under [custom views](/automation/custom-views) instead.

<Note>
  A segment is scoped to the person who created it. It isn't shared with the rest of your team by default the way a label is — if a segment needs to be a team-wide reference point, coordinate on the filter criteria directly rather than assuming everyone sees your saved list.
</Note>

## Segments and campaigns

A one-off campaign needs an audience, and the mechanism it actually uses is **labels**, not a saved segment directly — a campaign selects everyone carrying a chosen label, computed at send time. If you've built a segment filtered on a label, that segment and a campaign aimed at the same label describe the same group of people, but saving a segment doesn't, by itself, hand that audience to a campaign. Build the grouping around a label if the plan is to eventually message it. See [Campaigns](/campaigns).

## Next

<CardGroup cols={2}>
  <Card title="Attributes and custom fields" icon="list" href="/contacts/attributes">
    What a segment can filter on, in more depth.
  </Card>

  <Card title="Importing contacts" icon="upload" href="/contacts/import">
    Getting the underlying data into shape before you filter it.
  </Card>

  <Card title="Campaigns" icon="megaphone" href="/campaigns">
    Where label-based audiences actually get used.
  </Card>

  <Card title="Labels" icon="tag" href="/inbox/labels">
    The tagging mechanism campaigns target directly.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.