# Segments > Segments define reusable subscriber rules that stay current without manual maintenance — use them to target broadcasts, filter sequence emails, and build complex nested conditions from simple building blocks. - Human page: https://mailrith.com/docs/segments - Category: Subscriber Management - Reading time: 12 min read ## What this guide covers Build dynamic subscriber rules from status, tags, forms, sequences, and custom field values that update automatically over time. ## Sections - Segment Conditions - Previewing Results - Using Segments in Sends - When to Use Tags vs Segments ## Visual Reference ![Mailrith segments page listing saved segments with their condition rules.](https://mailrith.com/docs/screenshots/segments.png) 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 subscriber rule. Instead of manually maintaining a static list, you define conditions and Mailrith keeps the membership up to date. When a subscriber gains a tag, submits a form, changes status, enters a sequence, or updates a custom field, they can move into or out of matching segments automatically. Segment conditions can use several kinds of subscriber information: - **Subscriber status:** active, unconfirmed, unsubscribed, bounced, complained, or blocked. - **Tags:** subscribers who have one tag, all selected tags, any selected tag, or none of the selected tags. - **Forms:** people who submitted, or did not submit, a specific form. - **Sequence:** people who are active in, not active in, completed, not completed, ever been in, or never been in a selected sequence. - **Magic links:** people who clicked, or did not click, a selected magic link. - **Email activity:** people 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 to build layered targeting without rebuilding the same rule repeatedly. 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 any 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**, name the segment after the subscribers it represents, such as "Active Customers in Pro Plan". 4. Use **Description** to explain when teammates use the segment. 5. Add the first condition in the condition builder, usually subscriber status, tag membership, form submission, sequence membership, magic link activity, or a custom field value. 6. Choose whether the next condition narrows the subscriber group with **AND** or broadens it with **OR**. 7. Add exclusions for people you do not want to 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 sample subscribers match what you expect. Mailrith prevents a segment from referencing itself, directly or through a circular chain of other segments. This protects your subscriber rules from impossible loops. ## Previewing Results Always preview a segment before using it for a campaign, sequence, or automation. Preview runs the rule against the current workspace data and shows how many subscribers match right now. Preview is especially important when a segment uses more than one condition. A small change from AND to OR can turn a small subscriber group into a much larger one. A missing exclusion can include people you did not mean to contact. A custom field value spelled differently than expected can make a segment match fewer people than planned. If a preview count is wrong, check these common causes: 1. Click **Segments** in the left sidebar and open the segment you want to check. 2. Review **Live Preview** on the segment editor. 3. Compare the count with what you expected before using the segment in a [Broadcast](https://mailrith.com/docs/broadcasts.md) or [Sequence](https://mailrith.com/docs/sequences.md). 4. If the count is too high, look for OR groups, missing exclusions, or tags that are broader than intended. 5. If the count is too low, check AND groups, custom field values, subscriber status, and whether the active workspace is correct. 6. Open a few matching subscriber records and confirm their tags, fields, status, and activity history explain why they match. 7. Edit the conditions and watch **Live Preview** update until the subscriber group is clear. - The active workspace is not the workspace where the subscribers live. - A tag has a similar name to the tag you intended to use. - A custom field stores values in a different format than the condition expects. - The subscriber status filter is excluding people who otherwise match. - An OR group is too broad, or an AND group is too strict. ## Using Segments in Sends Segments are most useful when the same subscriber definition will be reused. Instead of rebuilding rules for every broadcast, create a segment once and select it when choosing campaign recipients. A segment is evaluated when it is used. If a broadcast is scheduled for tomorrow, the subscribers who match the segment tomorrow are the ones who receive it. This is helpful because people can join or leave the subscriber group naturally 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. - People in a sequence who qualify for a certain step based on their current data. ## When to Use Tags vs Segments Tags and segments solve different problems, and the cleanest 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 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 turns that fact into a precise send group. If a segment becomes hard to read, simplify it. Create smaller reusable segments, clean up inconsistent tags, or move repeated values into custom fields. Keep the segment understandable enough that another teammate can safely use it later. ## Related Guides - [Subscribers](https://mailrith.com/docs/subscribers.md): The Subscribers page is the operating hub for your subscriber list — search, status filtering, bulk actions, CSV imports and exports, and per-subscriber activity timelines all live here. - [Tags](https://mailrith.com/docs/tags.md): Tags are the fastest way to categorize subscribers — apply them through imports, forms, automations, and magic links, then use them as targeting filters across every send surface in Mailrith. - [Broadcasts](https://mailrith.com/docs/broadcasts.md): Broadcasts are for newsletters, product launches, announcements, and any message that goes out once to selected subscribers — compose, target, test, and send or schedule from a single workflow.