StockSweep StockSweep | Help Center

Customer Segments Builder

How segment rules combine, the caps that apply per plan, and the current status of attaching a segment to a clearance page.

Last updated: September 22, 2026

Contents
Show all sections (16) ▼

Customer segments let you define an audience — VIPs, lapsed buyers, a region — and reuse it rather than rebuilding the same filter every time. This article covers how a segment is built, the limits that apply, and one important limitation about what you can currently do with a finished segment.

Estimated time: 4 minutes

What you'll accomplish

  • Know how to build a segment and how its rules combine
  • Know the size and complexity caps that apply to you
  • Understand the three ways a segment can be sourced
  • Know the current status of segment-gated offers

Requirements

  • Plan: Pro or Enterprise.
  • Found at Settings → Customer Segments.

Before you start: what a segment can do today

Stated upfront, because it changes whether this is worth your time right now.

You can create, edit and resolve segments today: build the rule, see how many customers match, keep it current. What is not currently available is attaching a segment to an offer so that only its members can see or use it. The attachment gate is switched off, and a surface that cannot honour a segment rejects it rather than storing it and quietly ignoring it.

That refusal is the deliberate choice: we do not accept targeting input we cannot enforce, because a form that silently accepted it would let you believe an offer was gated when it was open to everyone. When the gate opens, the segments you build now will already be there.

How segment rules combine

A segment is a rule tree — conditions grouped with AND/OR, nested as needed. Two limits bound it:

  • Maximum nesting depth: 5
  • Maximum predicates: 20

Those are generous for real audiences and exist to keep resolution predictable. If you are pressing against 20 predicates, the segment is usually two segments.

Where segment members come from

Three sources, with different refresh behaviour:

Source What it is Refresh
Native Rules evaluated by StockSweep against your own data Daily
Platform A segment mirrored from your commerce platform Hourly
Email provider A list or segment mirrored from your ESP Hourly

You can trigger an on-demand resync at any time rather than waiting for the cadence.

Size caps

Caps apply per segment and depend on your plan:

  • Pro: up to 500,000 customers per segment, and up to 100 segments.
  • Enterprise: up to 2,000,000 customers per segment, and unlimited segments.

There is one additional cap that is not about your plan: when your commerce platform cannot express the rule natively and StockSweep has to resolve it itself, the segment caps at 100,000 customers regardless of plan. If you hit that, narrowing the rule is the fix.

Breaching a cap marks the segment degraded rather than deleting anything: existing attachments keep working against the last valid audience and new attachments are blocked until the segment is back within its cap.

Verify it is working

  • Open Settings → Customer Segments. Each segment shows its source, its current member count and when it last resolved.
  • Create a deliberately narrow test segment and confirm the resolved count matches what you expect from your own data.
  • A count of zero on a rule you believe should match is usually a source problem — check that the platform or ESP mirror has synced.

Troubleshooting

My segment shows as degraded

It has breached its audience cap. Narrow the rule; the segment recovers on its next resolution.

The member count is lower than my platform reports

Check the source. A native segment evaluates StockSweep's own copy of your customer data; a platform-sourced segment mirrors the platform's own definition. They will not always agree, and the source is shown on the segment.

I cannot attach the segment to a clearance page

That is the attachment gate described above, not a fault with your segment.

FAQ

Does a segment sync customer personal data into StockSweep?

Segments resolve to the membership needed to evaluate and enforce the rule. Sensitive fields are not copied for display.

What happens to my segments if I downgrade?

Stored segments and their definitions are preserved. Enforcement and caps follow your current plan.

Can I use a segment to exclude customers rather than include them?

Yes — build the exclusion into the rule tree with the usual AND/OR/NOT structure.