Segments

Segments define reusable audience rules that stay current without manual maintenance — use them to target broadcasts, filter sequence emails, and build complex nested conditions from simple building blocks.

5 min read

Mailrith segments page listing saved segments with their condition rules.
Saved segments are built from live conditions and update automatically. Use Preview before saving to confirm the subscriber count and spot unexpected logic interactions.

Segment conditions

A segment is a saved set of rules that defines a group of subscribers. Unlike a static list that you update manually, a segment's membership updates automatically as subscribers gain or lose the attributes the segment's conditions describe.

Mailrith segments are built from the following condition types:

  • Subscriber status: filter by active, unsubscribed, bounced, or complained.
  • Tags: include or exclude subscribers based on whether they have a specific tag.
  • Forms: target subscribers who submitted (or did not submit) a specific form.
  • Sequences: include subscribers who are (or are not) currently enrolled in a sequence.
  • Custom fields: match subscribers whose field values meet a condition — equals, does not equal, contains, is greater than, is before a date, and so on.
  • Saved segments: reference another segment as a condition to build nested or composite targeting logic.

Combine conditions using AND (every condition must match) or OR (any condition can match) to build precise audience definitions. You can mix AND and OR within a single segment.

Mailrith segments page showing saved segments with condition-based targeting rules
The Segments page lists all saved segments with a preview of the conditions used. Open any segment to edit its rules or see the current subscriber count.

Previewing results

Before saving a segment, click Preview to see how many subscribers currently match the conditions and review a sample of the matching contacts. Mailrith runs the preview against the live database — not a browser-side estimate — so the count reflects actual data at that moment.

Previewing is especially valuable when combining multiple conditions, because the interaction between AND and OR logic can produce unexpected results. Always preview a new segment before using it as the audience for a broadcast or automation trigger — a segment that matches zero subscribers means your email will not be delivered to anyone.

Using segments in sends

When creating a broadcast or configuring a sequence audience filter, you can select a saved segment instead of rebuilding conditions from scratch every time. This keeps targeting consistent and means you only need to update the segment's rules in one place when your audience definition changes.

Segments are evaluated at send time. The subscribers who match the conditions at the moment the email goes out are the ones who receive it. If a subscriber joins a segment's conditions after you define a broadcast audience but before the scheduled send time, they will be included in the delivery.

When to use tags vs segments

Tags and segments are complementary tools that work best together:

  • Use a tag to label a subscriber with a fact about what they did or where they came from: attended a webinar, made a purchase, signed up through a specific form.
  • Use a segment to define a rule: active subscribers who have the "webinar-attendee" tag but do not yet have the "purchased" tag.

A segment can use tags as inputs, which means good tag hygiene directly improves the quality of your segments. Keep your tag naming consistent, and your segment definitions will be easier to build and maintain. A cluttered tag directory makes it harder to express precise audience rules.

Need help?

Reach the Mailrith team if you need help planning a workflow or troubleshooting a setup.

Contact Mailrith

Related guides

On this page

Jump to the section you need.