> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Segments

A segment is a named, rule-based group of the stores that use your app, for example "on the Pro plan" or "spent more than \$500". Segments let you target automations and analysis at a slice of your base instead of all of it.

The segments list is searchable by **name** or **handle**. [Global search](/global-search) finds the same fields across apps.

## Building one

Start from a **template** in the gallery, describe the audience [in English](#describing-one-in-english), or build the conditions by hand. Whichever way you start, you end up in the same rule builder with a **live preview** beside it, showing how many stores currently match, so a rule that matches everything or nothing is obvious before you save.

Conditions are built over store attributes:

* **Subscription status**: **Active**, **Frozen** or **Churned**. These are the labels for the store's install state as Shopify reports it (installed, frozen, uninstalled). Frozen means Shopify paused the store's subscription, usually after a failed payment.
* **On trial**: yes or no. A store is on trial while its active subscription's trial end date is still in the future. It is separate from status because a trialist is also an installed store, so "Active and not on trial" is your paying base.
* **Plan name**: the store's current subscription plan. An installed store with no running subscription reads **Free** after a known cancellation of its last subscription. Without a known cancellation it keeps the last subscription's name. Frozen and uninstalled stores also keep the last plan they subscribed to, so "Plan name is Pro and status is Churned" finds the Pro stores you lost. A store that never subscribed is **Free**, even when it pays usage or one-time charges: those never count as a plan.
* **Total revenue** and **total charges**: lifetime money from that store.
* **Install date**: installed within (or not within) the last N days, re-evaluated against today rather than pinned to when you saved the segment.
* **Revenue rank**: inside or outside the top N earners across all your stores. Ties share a rank, so "top 10" can return more than ten stores.
* **[Custom fields](/custom-fields)**: your own attributes on a store (text, number, boolean, select, or date), with the operators that field's type allows.

Each field offers only the operators that make sense for it: `is` / `is not` for status, `contains` for a plan name, numeric comparisons for revenue and charges, "in the last N days" for install date, and top-N for revenue rank. Conditions combine with **And** / **Or**.

Membership is computed **on read**: a store moves in or out of a segment as its data changes, so a segment is always current and never a stale snapshot. That's also why a segment can't be exported as a fixed list, because it isn't one.

A condition on a custom field that gets deleted is marked as a deleted field rather than silently ignored.

## Describing one in English

Instead of building the rules by hand, describe the audience ("stores that installed in the last 30 days and have spent over \$200") and Meridian turns it into conditions you can review, adjust and save. It tells you when the generated rules don't fully capture what you asked for, so you check before saving rather than trusting it blindly. Available while creating a segment.

## Using segments

Segments are available for **public apps**. Once defined, a segment can:

* **branch an [automation](/condition-segment)**: only email the stores in an "at-risk" segment,
* **scope [Analytics](/introduction-11)**: every metric on the page restricted to that audience, where a segment matching nothing gives an empty report rather than an error,
* **feed the [Report Builder](/report-builder)**, as a dataset and as a filter.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.