Merchants searching for email segmentation examples usually want a list of clever audience names, but the thing that actually determines whether segmentation pays off is whether the storefront and the underlying customer data can support it at all, which is a code and API question, not a naming question.
Most merchants who search for email segmentation examples want a list of clever segment names to copy, five or ten audience labels they can paste into their email tool and call it strategy. That is the wrong place to look first. The actual bottleneck is almost never naming the segment. It is whether the platform can define it, return it reliably through the API, and whether your storefront is fast enough that the behavior data feeding the segment is even trustworthy. Shopify’s own segments API returns segment objects as simple nodes with global ids, and that plumbing, not the label you give the segment, is what determines whether “high value repeat customers” is a real, queryable group or just a folder name.
Recent purchasers, repeat buyers, cart abandoners, high average order value customers, and lapsed customers form the backbone of nearly every profitable email program, because each one maps to a distinct message and a distinct moment in the buying cycle. None of these require custom app development on a typical Shopify store, because the customer segments API already models a segment as a queryable object. The API reference loaded on September 5, 2026 shows segments returned as a list of edges, each wrapping a node with an id, for example gid://shopify/Segment/210588551 and gid://shopify/Segment/250599805. That structure is what lets a segment be defined once in the admin and then referenced consistently by any tool that talks to the API, so the segmentation work is conceptual and rule-based, not code-based.
A common confusion is thinking that theme settings somehow gate or expose customer segments. They do not, and the theme code makes this plain. Take blocks/payment-icons.liquid from the Horizon theme, read from the Shopify/horizon repository at commit 8b42ace, which registers under the name t:names.payment_icons and carries exactly 6 settings. One is horizontal_alignment, a select with 4 options. The other five are range controls: gap, padding-block-start, padding-block-end, padding-inline-start, and padding-inline-end, each running 0 to 100 in 1px steps. That is the entire setting surface of this block. There is no field here for customer id, no field for order count, nothing that touches segmentation. This absence is the point: theme blocks control spacing and alignment of what a shopper sees, and segmentation logic sits entirely in Shopify’s backend and its API, disconnected from any individual theme’s file structure.
Segmentation only works on data you actually collect, and a store that loses visitors to slow pages is collecting less of it. The pass rates come from CrUX field data for July 2026, real visitors rather than a lab run, and the market median on mobile is 85.5% of stores passing all Core Web Vitals, with the best-measured theme in the market at 98.6% and the worst at 46.1%, across 247 themes with sufficient data. On desktop the median is 86.2%, with a top of 99.2% and a bottom of 30.3%, across 199 themes with sufficient data. A store running a theme near the bottom of either range is bleeding visitors before those visitors ever generate a second purchase, a cart abandonment event, or a lapse worth re-engaging, so the segment sizes you eventually mail against start smaller than they should.
| Metric | Value |
|---|---|
| Themes in ranked market | 329 |
| Median theme price | $300 |
| Theme price range | $100–$500 |
| Median market rating | 4.53 / 5 (308 themes) |
| Median review count | 23 |
| Mobile CWV pass rate, median | 85.5% (247 themes) |
| Mobile CWV pass rate, best/worst | 98.6% / 46.1% |
| Desktop CWV pass rate, median | 86.2% (199 themes) |
| Desktop CWV pass rate, best/worst | 99.2% / 30.3% |
It is tempting to treat a higher-priced theme as a safer bet for a data-driven email program, but the price sheet does not measure anything related to segmentation or even to speed. Across the 329 themes verified on themescout.co on 2026-09-07, the median price sits at $300 inside a $100 to $500 range, and the average rating across 308 rated themes is 4.53 out of 5 with a median of 23 reviews per theme. None of those figures come from a performance test or an API capability check. A theme can be expensive, well reviewed, and still sit near the 46.1% end of the mobile Core Web Vitals range, which is why the rating aggregate and the field data need to be checked separately rather than assumed to move together.
Build your five segments directly through Shopify’s customer segments API or the admin UI that sits on top of it, since the structure already exists and returns clean ids like the ones shown in the September 5, 2026 reference, and treat that as separate work from picking a theme. Then check your current theme’s own Core Web Vitals pass rate against the July 2026 market medians of 85.5% mobile and 86.2% desktop before you invest more in campaign copy, because a theme underperforming those medians is shrinking the very data your segments are built from.
The five that pay first are recent purchasers, repeat buyers, cart abandoners, high average order value customers, and lapsed customers, and none of these require custom development because Shopify exposes them through the customer segments API as plain segment objects with an id field, as shown in the API reference loaded September 5, 2026. You build the segment definition once in the admin and the API returns it as an edge with a node id like gid://shopify/Segment/250599805. There is no theme setting involved in defining who is in a segment, so switching themes does not break your segments.
Not the segment definitions themselves, but it affects the data quality that feeds them, because a theme with a low Core Web Vitals pass rate loses visitors before they generate the behavior signals segmentation relies on. The market range on mobile runs from 46.1% pass rate at the worst-measured theme to 98.6% at the best, out of 247 themes with sufficient CrUX data for July 2026. On desktop the range is 30.3% to 99.2% across 199 themes with sufficient data. A theme sitting near the bottom of either range is quietly thinning your top-of-funnel segments before you ever open your email tool.
It comes from Shopify's admin GraphQL API, specifically the segments query documented at shopify.dev, which as loaded September 5, 2026 returns segments as edges wrapped around node objects, each with a global id such as gid://shopify/Segment/210588551. This is entirely separate from theme code. A block like Horizon's payment-icons.liquid, read from the Shopify/horizon repository at commit 8b42ace, has 6 settings covering alignment and padding and nothing about customers or segments, which illustrates the general point that theme files control layout, not audience logic.
Price alone tells you nothing about this. The median theme price across 329 themes verified on themescout.co on 2026-09-07 is $300 with a range of $100 to $500, and the median store rating is 4.53 out of 5 across 308 themes with a median of 23 reviews, but none of those numbers measure whether a theme's pages load fast enough to preserve the behavioral data segmentation needs. Check the theme's own Core Web Vitals pass rate instead, since the market median is 85.5% on mobile and 86.2% on desktop for July 2026, and a theme well below that median is worth scrutinizing before you build campaigns on top of it.
No, not directly, because a block like blocks/payment-icons.liquid in the Horizon theme only exposes 6 settings, all display controls: horizontal_alignment as a select with 4 options, and four padding ranges plus a gap range, each running 0 to 100 in 1px steps. None of these settings are named as tracking or customer-data fields, so interaction with this specific block is not a segmentation input by design. Segments come from order history, purchase behavior, and customer properties surfaced through the segments API, not from which visual block a shopper happened to see.