Browse Docs

Jump between feature areas and guides without leaving the article.

On This Page

Jump to the section you need.

Segments

Segments define reusable subscriber rules that stay current without manual maintenance. Use segments to target broadcasts, filter sequence emails, and build complex nested conditions from simple building blocks.

12 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 rule for subscriber membership. Instead of manually updating a static list, define the conditions once, and Mailrith keeps the subscriber group current. When a subscriber gets a tag, submits a form, changes status, enters a sequence, or updates a custom field, Mailrith can automatically add that subscriber to matching segments or remove them from segments they no longer match.

Segment conditions can use these types of subscriber information:

  • Subscriber status: active, unconfirmed, unsubscribed, bounced, complained, or blocked.
  • Country or region: subscribers from selected countries or regions when that information is available. For one country, choose the country name from the dropdown.
  • Tags: subscribers who have one tag, all selected tags, any selected tag, or none of the selected tags.
  • Forms: subscribers who submitted, or did not submit, a specific form.
  • Sequence: subscribers who are active in, not active in, completed, not completed, ever been in, or never been in a selected sequence.
  • Magic links: subscribers who clicked, or did not click, a selected magic link.
  • Email activity: subscribers who opened or unsubscribed from emails, depending on the available event data.
  • Custom fields: values such as text, numbers, dates, single-choice fields, multi-choice fields, and checkboxes.
  • Other segments: reuse an existing segment inside a new segment when you need layered targeting and do not want to rebuild the same rule.

Conditions can be joined with AND or OR. Use AND when every condition must be true, such as active subscribers who have the "customer" tag and are in the United States. Use OR when at least one condition can be true, such as subscribers interested in "webinars" or "workshops".

  1. Click Segments in the left sidebar.
  2. Click Create Segment in the page header.
  3. In Segment Name, enter a name that describes the subscribers in the segment, such as "Active Customers in Pro Plan".
  4. Use Description to explain when teammates should use the segment.
  5. Add the first condition in the condition builder, such as subscriber status, tag membership, form submission, sequence membership, magic link activity, or a custom field value.
  6. Choose AND if the next condition should narrow the subscriber group, or choose OR if the next condition should broaden it.
  7. Add exclusions for subscribers who should not receive the message, such as current customers, recent purchasers, or subscribers with a suppression tag.
  8. Review Live Preview, including Active Subscribers, Total Subscribers, and the matching subscriber table.
  9. Click Save Segment only after the preview count and the sample subscribers match the group you intend to target.

Mailrith prevents a segment from referencing itself directly or through a circular chain of other segments. This prevents subscriber rules from creating impossible loops.

Mailrith segments page showing saved segments with condition-based targeting rules
The Segments page lists saved subscriber rules and lets you preview how many subscribers match before you use the segment in a send.

Previewing Results

Always preview a segment before you use it for a campaign, sequence, or automation. The preview checks the segment rule against the current workspace data and shows how many subscribers match at that moment.

Preview is especially important when a segment has more than one condition. Changing AND to OR can make a small subscriber group much larger. A missing exclusion can include subscribers you did not mean to contact. A custom field value with unexpected spelling can make a segment match fewer subscribers than planned.

If the preview count does not match the subscriber group you expected, use these steps to find the cause:

  1. Click Segments in the left sidebar and open the segment you want to check.
  2. Review Live Preview in the segment editor to see the current count and matching subscriber table.
  3. Compare the preview count with the count you expected before you use the segment in a Broadcast or Sequence.
  4. If the count is too high, look for OR groups, missing exclusions, or tags that include more subscribers than intended.
  5. If the count is too low, check AND groups, custom field values, subscriber status, and whether you are in the correct workspace.
  6. Open a few matching subscriber records and confirm that each subscriber's tags, fields, status, and activity history explain why the subscriber matches.
  7. Edit the conditions and watch Live Preview update until the matching subscriber group is the group you expect.
  • The active workspace is not the workspace where the subscribers are stored.
  • A tag has a name similar to the tag you meant to use.
  • A custom field stores values in a different format than the condition expects.
  • The subscriber status filter excludes subscribers who otherwise match.
  • An OR group includes too many subscribers, or an AND group excludes too many subscribers.

Using Segments in Sends

Segments are most useful when you need to reuse the same saved rules. Instead of rebuilding rules for each broadcast, create a segment once and select it when you choose campaign recipients.

Mailrith evaluates a segment when the segment is used. If a broadcast is scheduled for tomorrow, the subscribers who match the segment tomorrow receive the broadcast. This keeps the send current because subscribers can join or leave the group before the send time.

Common send uses include:

  • Active newsletter subscribers who have not purchased yet.
  • Trial users whose trial ends within the next week.
  • Customers who clicked a product interest link but did not register for the event.
  • Subscribers from a specific form who also chose a particular topic preference.
  • Subscribers in a sequence who qualify for a certain step based on their current subscriber data.

When to Use Tags vs Segments

Tags and segments solve different problems. A clean subscriber setup usually uses both.

  • Use a tag when you want to mark something about a subscriber directly, such as "attended-webinar" or "interested-in-enterprise".
  • Use a custom field when you need to store a specific value, such as "Plan is Pro" or "Renewal Date is June 1".
  • Use a segment when you want a live rule that combines status, tags, forms, fields, sequences, events, or other segments.

For example, you might apply a "webinar-attendee" tag when someone attends an event. Then you might create a segment for active subscribers who have "webinar-attendee", do not have "customer", and selected "Enterprise" in a custom field. The tag stores a simple fact. The segment uses that fact to create a precise send group.

If a segment becomes hard to read, simplify the rule before teammates use it. Create smaller reusable segments, clean up inconsistent tags, or move repeated values into custom fields. Keep each segment clear enough that another teammate can safely use it later.

Need Help?

Reach out to the Mailrith team if you need help with anything.

Contact Us →