# Segment group settings reference Find the settings you need to organize segments, check audience counts, sync contact data, and see what depends on a group. Available on the Grow, Scale, and Pro plans. Use the segment library to organize your audiences and see how many visitors belong to each one. **Segments** opens the **Segment Groups** library, where you'll find standalone groups. Choice questions and their answer segments live under **Questions**. A segment group holds related categories, such as Customer and Lead in a lifecycle group. A new standalone group allows one winning segment. It starts without segments, automatic rules, or a sync destination. To create one, follow [Create and manage segment groups](https://rightmessage.com/help/creating-and-managing-segment-groups). ## Segment library controls ![Segment group library containing customer lifecycle and affiliate groups](https://rightmessage.com/help/screens/segment-groups-index.light.webp) | Control | What you can do | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **New segment group** | Creates a group with a generated name beginning **New Segment Group** and opens **Setup** immediately. No template picker appears. | | **Grid** and **List** | Switch the library layout. List is the initial layout. The selected view is remembered in this browser for the signed-in user, and a view in the page URL takes precedence. | | **All** | Shows all standalone groups. The label includes the total count. This is the initial filter. | | **Favorites** | Shows favorited groups. The label includes their count. | | **Search segment groups** | Filters by group name without case sensitivity. It doesn't search individual rule values. | | Sort menu | Offers **Favorites first**, **Favorites last**, **Name A–Z**, **Name Z–A**, **Most segments applied**, and **Fewest segments applied**. **Favorites first** is the default. Equal values are ordered by name. | | Date-range button | Changes the reporting period, not the group's rules. | | **Clear filters** | Clears search and the Favorites filter. It doesn't reset sort order or the reporting period. The toolbar shows it for Favorites filtering. Filtered empty states also offer it. | | Favorite star | Adds or removes the group from Favorites without opening the group. New groups aren't favorited. | | Group name | Opens the group's detail page. | The List columns are **Segment group**, **Segments**, **Segments applied**, and **Favorite**. A group with no segments also displays **Needs setup**. Grid cards show the name, segment count, favorite star, and segment distribution. You'll see up to five distribution rows at first. **Show more** includes the number of remaining rows, and **Show less** collapses them again. **View results** opens the group. Cards can show **Multiple segments** and **Synced** badges. **Synced** means you've configured mappings. Check the contact record to confirm that your provider accepted an update. ## Reporting period and totals The date picker offers **Today**, **Last 7 Days**, **Last 14 Days**, **Last 30 Days**, **This Month**, **Last Month**, and **Last 90 Days**, plus calendar selection. Presets for the last number of days include today. Calendar ranges are limited to one year, and the picker doesn't allow future dates. The library and group reports share a reporting range. If the page URL contains a valid range, the page restores it when you open it. Without an inherited range, reporting starts seven days ago and ends at the current time. That initial range differs from the **Last 7 Days** preset. | Summary | Meaning | | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- | | **Segment groups** | Number of groups shown, with the total available groups alongside it. | | **Segments** | Number of configured segments across the shown groups. | | **Visitors segmented** | Unique visitors across the shown groups for the selected period. A visitor isn't counted again just because several groups match. | | **Segments applied** | Sum of segment memberships across the shown groups. This can exceed unique visitors. | These totals count segment memberships, not survey submissions. One visitor can match several groups, or several segments in a group that allows multiple winners. ## Empty and unavailable segment libraries | State | Meaning | | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **No segment groups yet** | The project has no standalone groups. The page prompts creation. | | **No segment groups match these filters** | Groups exist, but search or Favorites filtering excludes them. **Clear filters** removes that narrowing. | | **Needs setup** | The group has no segments. | | Statistics unavailable | You can still edit your groups. Unavailable totals display a dash rather than zero. The page suggests another date range or returning later. | ## Group header and tabs In the header, you can edit the group's internal name, see its segment count, and open **More actions**. Opening an existing group takes you to **Results**. Creating or duplicating a group takes you to **Setup**. If the page URL specifies a tab, that tab opens instead. | Tab | Contents | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | **Results** | Counts, membership shares, and engagement lift for the selected period. | | **Setup** | Segment names, order, identifiers, and automatic rules. | | **Sync with** the provider name | Outbound mappings and the matching contact-data rules those mappings create. Without a connection, the label is **Sync with ESP**. | | **Uses** | Linked resources and the deletion-impact summary. The tab includes a use count. | Your edits save to the project draft and reach your website after [publication](https://rightmessage.com/help/publishing-your-changes). Leaving the editor doesn't undo them. **Segment group not found** means the requested group isn't available, including after deletion. ## Segment results ![Customer Lifecycle segment group with its customer, lead and anonymous segments](https://rightmessage.com/help/screens/segment-groups-show.light.webp) **Segment results** shows the total segments applied and one row per reported segment. Each row shows the segment name, visitor count, and share to one decimal place. Rows follow visitor count, not the matching order in **Setup**. A segment's share is its count divided by the group's total memberships. If your group allows multiple winners, one visitor can count toward several segments. The page notes that shares count memberships, not unique visitors. **Lift** compares a segment's pages per visitor with the other segments in that group. Visitors outside the group aren't part of the comparison. The tooltip calls the comparison **Everyone else (baseline)**. It also shows **Segment pages / visitor**, **Lift**, and the selected dates. The calculation uses current segment membership. The tooltip notes when there are few visitors or when the calculation uses a sample. In a group with multiple winners, overlapping memberships can count on both sides. This isn't a randomized test or a measure of conversion lift. Engagement calculations cover at most 30 days and can sample up to 1,000 visitor IDs per segment. If you select a longer range, lift uses a shorter window ending on your range's end date. Membership counts still use your full range, and the lift tooltip still shows your selected dates. A dash means lift is unavailable, not zero. Other reporting states are **Loading results**, **Stats unavailable**, **No segments yet**, and **No visitors segmented yet**. ## Segment setup | Control or value | Behavior | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Segment name | Editable label for the membership. Renaming doesn't change the segment identifier. | | Drag handle | Reorders segments. Linked router branch order follows the new order. | | Displayed identifier | Read-only `seg_` identifier. It isn't a customer-editable setting. | | Segment trash button | Opens **Really Delete?** with **Delete** and **Cancel**. Removes the segment and its rules, including associated flow branches and segment-setting actions. | | Rule editor | Defines automatic membership for that segment. | | **Add segment** | Appends a segment named **New Segment**. | | Rule-count expand control | Opens or collapses rules in large groups. Large rule sets can also collapse individual condition groups. This changes the editor display, not matching behavior. | A group identifier begins with `dim_`. A segment identifier begins with `seg_`. A linked question has its own `raq_` identifier. Names and IDs aren't interchangeable in integrations or developer tools. New standalone groups allow one winner. RightMessage checks automatic rules in segment order, so the first matching segment wins. A remembered choice answer takes priority over ordinary automatic rules. Debugger overrides can change which segment wins while you're testing. A match can stay unresolved while contact data loads. If a higher-priority segment is unresolved, RightMessage can wait before selecting a lower-priority match. Multiple-answer choice questions can have several memberships. Existing groups that allow multiple winners keep that behavior, but standalone **Setup** doesn't have a multiple-winners toggle. A visitor who matches no segment stays unsegmented in that group. ### Automatic rule controls Each segment starts without automatic conditions. **Add group** creates a group of AND conditions. Alternative groups normally combine with OR. **Add AND condition** adds another requirement. A condition's remove control deletes that condition. The group's trash control deletes the group. The standard segment editor doesn't expose a top-level **Any group matches** or **All groups match** selector. Existing group logic is shown through its connectors. See the [condition reference](https://rightmessage.com/help/condition-builder-reference#groups-and-combinations) for grouping behavior and the distinction between empty groups and unrestricted targeting. **Generate Conditions** accepts a description when no user-defined conditions exist. **AI Generate** opens the generation dialog when rules already exist. Generated rules change the draft and still need review. **Auto synced** groups are read-only here because the Sync tab owns them. Choice questions use **Auto-Segment**, **Edit rules**, and a drawer with **Done** instead of the standalone group editor. Their rules are locked during a running A/B test. Answer visibility conditions are separate. They control which choices appear, not which answer is assigned automatically. The [automatic rules guide](https://rightmessage.com/help/automatically-segmenting-by-on-site-behavior-or-available-data) covers setup. The [condition reference](https://rightmessage.com/help/condition-builder-reference) covers operators, source availability, and unresolved data. ## Sync with your provider Connect your email platform to send segment data to your contacts. Without a connection, this tab explains that you need an integration. Your connected provider determines which sync methods and labels appear. | Control | Options and behavior | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Sync mode** | Custom-field mapping, or supported tag or list mapping. The selector appears when the provider offers alternatives. Provider-specific names can replace Custom Field, Tag, or List. | | **Destination** | The custom field that receives the selected segment's mapped value. Standalone group mappings use custom fields, not native contact fields. | | **Answer → value** | One mapped value per segment. Enum fields offer their allowed values. Other fields use text inputs. A multiple-winning group's selected values are comma-separated in field mode. | | **AI Generate** | Generates field-mapping values for non-enum fields. It isn't an option-value generator for enum fields. | | **Answer → tag** or the provider's list label | Maps each segment to an available tag or list. The picker supports search and clearing. | New groups default to field mode with no destination. A saved mode remains selected. For groups without a saved mode, the editor prefers supported tag or list mapping for multiple selections and otherwise prefers a custom field. Switching modes with existing mappings opens **Clear Existing Mappings?**. **Switch & Clear** discards the old mappings. **Cancel** keeps them. Clearing a populated field destination opens **Remove sync destination?**, with **Remove** and **Cancel**. Changing directly to another field preserves the mapped values. Mappings also create reverse conditions for identified contacts. You'll see these as **Auto synced** in **Setup**. Mappings don't identify anonymous visitors. To check a writeback, inspect the destination contact record. See [Map answers to contact fields and tags](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm). ## Where the segment group is used **Uses** lists linked resources with a **View** button. The categories are: - **Flows**. - **Forms**. - **Campaigns**. - **Widget targeting**. - **Email personalization**. - **Segment groups whose rules reference it**. - **Questions whose rules reference it**. - **Personalized phrases**. Flow labels describe uses such as **Routes on it**, **Condition**, and **Sets an answer**. The use count adds the listed resources across categories. A group can say **Not used in any flow yet** and still have dependencies elsewhere. If provider-field information is unavailable, you'll see **Some email personalization references are unavailable right now**. Other uses can remain visible. Check those email references before deleting the group. **Delete this segment group** describes removed and retained dependencies. Its **Delete segment group** button opens the deletion confirmation. ## More actions ### Duplicate **Duplicate** copies the group's configuration, including segments, rules, and sync settings. The copy's name ends in **(copy)**. It receives new group and segment IDs and opens in Setup. Existing flows, campaigns, and other resources continue referencing the original. Duplication doesn't update those references or copy reporting history into the new identifiers. Questions must be duplicated through their question editor so the question and its linked group stay together. ### Delete ![Delete segment group confirmation explaining that referencing flows and campaigns remain and historical data is kept](https://rightmessage.com/help/screens/verify-audience-delete-group.light.webp) **Delete** opens **Delete segment group?**. The dialog names the group, describes its dependency impact, and warns that the action cannot be undone. **Delete** confirms. **Cancel** leaves the group unchanged. Deleting a group can clear linked flow routing and split branches, remove segment-setting actions and linked form fields, and delete campaigns based directly on the group. It can also remove the group's personalized phrases and the referencing rules covered by the deletion process. The flows and forms themselves aren't deleted just because you remove their linked group. Other references can remain, including widget targeting, email personalization, and some conditions in other resources. The impact message separates references that will be removed from references that will stay. Review the remaining references and repair anything that still needs the group. Historical data stays in reports. Deleting a group doesn't delete responses. For linked questions, previous-answer conditions can block deletion until you remove those references. Deletion changes the draft. Publish to apply the affected configuration to your website. The [management guide](https://rightmessage.com/help/creating-and-managing-segment-groups) walks through reviewing dependencies first.