> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/segments/percentage-split-segments.md).

# Percentage Split Segments

Domains can now divide an audience into up to four fixed-percentage segments directly in the segment editor, and target each one independently from the notification builder. This ships the full self-serve UI and surfaces split segments wherever an audience can be chosen for a notification send.

### What's New

#### Percentage Split section in the segment editor

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2F1WGfWoFhXFQ6c9olDl5c%2FScreenshot%202026-11-10%20at%204.26.16%E2%80%AFPM.png?alt=media&amp;token=be29b4c7-3a51-4e8f-8262-92c0c7497a3d" alt=""><figcaption></figcaption></figure>

A **Percentage Split** section now appears at the bottom of the domain-level segment editor for new and duplicated segments. It is empty by default; clicking **Create A/B/n split segments** activates it. Once active:

* Up to four split segments can be defined. Each row shows its letter, auto-generated name, share percentage, and a remove button. A bar visualizes the current shares.
* Names are generated automatically in the format *{Segment Name} A (50%)*, *{Segment Name} B (50%)*, and so on.
* All split segments share the same conditions, channel selection, and icon as the parent segment.
* Shares must be whole percentages. Two or more segments must total exactly 100%; a single segment can hold any share from 1 to 99 (the remaining audience is unaddressed). The save button is disabled with a plain-language error until shares are valid.
* The save button reads **Create N Segments** for two to four splits, **Create Segment** for one, and **Save** when split is off.

#### Editing, duplicating, and archiving

* Opening any split segment opens the whole split for editing. Conditions, channels, name, and shares are shared across all segments in the split.
* Split segments cannot be added or removed after saving. The editor surfaces this clearly and directs the user to duplicate.
* Duplicating a split creates a new split with a new random division of subscribers. The originals are unchanged.
* Archiving any split segment archives the entire split. The confirmation dialog lists every segment that will be archived.

#### Segment list and notification builder

Split segments carry a purple **Split** tag in the segment list. Hovering shows the tooltip "Changes to this segment apply to every segment in its split."

The notification builder's audience dropdown now surfaces split segments, also tagged **Split**. Split segments cannot be used alongside A/B test variants; the builder blocks this combination with a clear error.

#### Segments with no conditions

As part of this release, any segment (not just splits) can now be saved with no conditions. This makes it straightforward to divide the entire subscriber base into two or more splits. The editor shows "With no conditions, this segment targets all subscribers" and displays a live reach estimate.

### How to Access

**Segments > Create Segment (or open an existing segment) > Percentage Split section > Create A/B/n split segments**

The feature is available on domain-level segments only. It does not appear in organization-level segments or multi-domain segment editors.

### Benefits

* Customers can now create controlled, persistent audience splits without engineering involvement.
* Because subscriber assignment is stable, the same subscriber always receives the same treatment across sends -- making longitudinal comparisons valid.
* Splits made manually before this release continue to work for delivery. The editor surfaces a read-only notice for pre-existing hand-built splits.
* Reach estimates are displayed per split segment (scaled by share), so customers have visibility into effective audience sizes before sending.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://documentation.pushly.com/platform/segments/percentage-split-segments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
