Skip to main content
A segment is a saved set of rules over your email contacts — what they bought, how much they spent, when they last bought, opened or clicked, their tags, country and how they subscribed. Segments are evaluated live: a count, a member list or a send always uses the rules at that moment, so “bought in the last 30 days” means the 30 days before the email goes out.
Segments are on the Growth plan and above. On other plans every segment endpoint answers 403 with code: FEATURE_LOCKED and details.requiredPlan: "tier2" — API keys and MCP included.

Endpoints

Definition

Rules sit in groups. Rules inside a group combine with the group’s match; groups combine with the top-level match — all is AND, any is OR. Up to 10 groups of 20 rules.
This is “(bought the course and spent more than $50) or tagged vip”. Purchase totals are rebuilt from your sales every night (and a new purchase moves “last purchase” right away). Contacts added before segments shipped have no source.

Count a segment before saving it

Smart tags

Give a segment a smartTag and every member carries that tag. It is refreshed every night: new members get it, people who left the segment lose it — only where the segment added it, so a tag you typed by hand is never removed. One smart tag per segment, each tag used by one segment (409 otherwise). The dashboard offers three to start: customer, vip (spent over $200) and lapsed (no purchase in 90 days).

Send a post to a segment

Set segmentId on POST /newsletters/posts (or update a post with it), then send or schedule it as usual. The segment’s rules are evaluated when the post goes out. A deleted segment, or a plan that no longer includes segments, leaves the post with no audience: it fails instead of sending to someone else. Automations can use segments too: limit a trigger to a segment, or branch on Is in segment in a condition.

MCP

AI agents get list_segments, create_segment, get_segment, get_segment_count and preview_segment. See MCP server.