# Create and manage segment groups

You'll group visitors using what you already know about them, then use those segments to show more relevant questions and offers.

Available on the Grow, Scale, and Pro plans.

A segment group lets you use what you already know about visitors to decide what to show them. For example, [WorkForge](https://workforge.rightmessage.com) could group people who've read its pricing page, then show them a relevant offer in a flow.

If you'd rather ask visitors to choose an answer, create a **Multiple choice** or **Yes / No** question. Those questions create their own answer segments. Input questions, such as **Number** or **Short text**, don't. See [Segments, questions, and responses](https://rightmessage.com/help/how-we-segment-your-visitors).

## Create your group

Open a project you can edit. These changes stay in its draft until you publish, so visitors keep seeing the published setup while you work.

1. Open **Segments** in the sidebar.
2. Choose **New segment group**.
3. Replace the generated name with a name you'll recognize, such as `WorkForge pricing interest`.
4. In **Setup**, choose **Add segment**.
5. Rename **New Segment** to `Pricing readers`.
6. Add the rules that qualify someone for it. Follow [Create automatic segmentation rules](https://rightmessage.com/help/automatically-segmenting-by-on-site-behavior-or-available-data).
7. Add any other segments the group needs.

**New segment group** opens **Setup** directly, without a template picker. Your new group starts with no segments, rules, or sync destination.

![Segment group library listing Affiliates and Customer Lifecycle with New segment group highlighted](https://rightmessage.com/help/screens/segmentation-group-library.light.webp)

*The **Segment Groups** library holds standalone groups. **New segment group** opens **Setup**.*

Use the real pricing page on your site. WorkForge's is `https://workforge.rightmessage.com/pricing.html`. If the segment needs to apply on other pages too, use a recorded visit rather than a current-page rule. Choose the occurrence and time window to fit. See [Pages and visits conditions](https://rightmessage.com/help/conditions-pageviews).

Page-visit and other anonymous rules don't need an email platform. [Contact conditions](https://rightmessage.com/help/conditions-partner) need a connected provider and an [identified contact](https://rightmessage.com/help/how-do-we-identify-returning-subscribers-or-contacts) with matching data.

## Put specific segments first

A new group allows one winning segment. If several automatic rules match, the first segment in the group wins.

1. Open **Setup**.
2. Drag segments by the handle beside their names.
3. Put specific segments above broader segments that include the same visitors.

For example, put "Pricing readers in the last week" before "Returning visitors" if pricing readers can match both.

Renaming a segment doesn't change its identifier. The displayed `seg_` identifiers aren't editable settings.

## Use the group in your site

Creating segments doesn't change what visitors see until you use them.

1. Add the group to a flow router or a targeting condition where it should change what happens.
2. To save segment data to contacts, open **Sync with** your provider and configure the [field or tag mappings](https://rightmessage.com/help/synchronizing-contact-data-with-your-email-platform-or-crm).
3. Open **Uses** to see which parts of the project depend on the group.

If the flow should use an existing answer instead of asking again, follow [Route using an answer you already know](https://rightmessage.com/help/route-by-existing-answers).

## Check it, then publish

You'll need your project's snippet installed to test website behavior. Make the visits or other actions your rules need before checking the match.

1. Choose **Preview on your site** to open the draft with the debugger.
2. Check a visitor who should match and a visitor who shouldn't. [Testing your changes](https://rightmessage.com/help/best-practices-for-testing) explains how to try both.
3. Review the project's unpublished changes.
4. Choose **Publish** when the full draft is ready.

Closing the group doesn't undo your edits, and saving doesn't publish them. [Publishing](https://rightmessage.com/help/publishing-your-changes) applies the project's changes, not only the group you have open.

When matching visitors get the intended question or offer and unmatched visitors take the fallback, the group is working. Next, use the [segment group settings reference](https://rightmessage.com/help/segment-library-reference) to understand the audience counts and settings.

## Duplicate a group

To use an existing group as a starting point:

1. Open the group and choose **More actions** in the header.
2. Choose **Duplicate**.
3. Rename the copy in **Setup**.
4. Review its rules and sync mappings before using it.

The copy's name ends in **(copy)**, and it has new group and segment identifiers. Existing flows and targeting rules still use the original. Replace those references only where you want to use the copy.

## Remove a segment or group

Before deleting, open **Uses** and read the dependency information. Some references will be removed. Others will stay and need your attention. Deleting a group keeps its historical reporting data.

To remove one segment:

1. Open **Setup** and choose the segment's trash button.
2. Review **Really Delete?**.
3. Choose **Delete** to confirm or **Cancel** to keep it.

To delete the whole group:

1. Open **More actions** and choose **Delete**.
2. Read the dependency impact in **Delete segment group?**.
3. Choose **Delete** only if you accept those changes.
4. Review the affected flows and targeting before publishing.

![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)

*Choosing **Delete** in the menu opens this confirmation. It doesn't delete the group yet.*

You can't undo deletion through that dialog. The settings reference linked above lists exactly which dependencies are removed and which can remain.