Segments

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Defined by a rule rather than a list, so the group is correct tomorrow without anyone rebuilding it.

Sizes update as behaviour changes, which turns a segment into a metric as well as an audience.

A segment of zero is as informative as a large one, and it is visible rather than absent.

Rules read as sentences, so the definition is auditable by whoever acts on it.

How it works

1
A segment is defined by a rule over data other modules already hold.
2
The rule is stored rather than the membership, so the segment is correct tomorrow without rebuilding.
3
Size recomputes on read, which makes a segment a metric as well as an audience.
4
A segment of zero is shown rather than hidden, because that is often the finding.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Segmentrequired	text	What the group is called, phrased as the thing they have in common.
Rulerequired	text	The definition. Stored rather than the people, which is what keeps it current.
Sizerequired	number	How many match right now. Derived on read, never stored.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Rules are limited to what the source modules record. Anything they do not track cannot be segmented on.
No combination of segments — an intersection is a new rule.
Size is a count, with no breakdown unless you build a second segment.
Nothing acts on a segment by itself; it is an audience, not an automation.

Before it works

What you have to provide, if anything.

Needs at least one module with enough history for a rule to mean something.
Write the rule as a sentence first. If it cannot be said clearly it cannot be defined clearly.

In practice

A shop with a mailing list and no idea who was on it.

“Who has bought twice, and who never has?”

What was said to the agent

What the agent built

Four segments defined by rule: repeat buyers, dormant, high value and never activated.

What changed

Two hundred and six people had signed up and never bought — larger than every other segment combined, and a completely different problem from the one being worked on.

Better with

These do a different job on the same data. An agent can have all of them.

UserbaseLive

People sign up and use the product over time, and retention matters more than the relationship with any one of them.

CouponsLive

Discounts are offered through codes and someone needs to see which ones worked and which are still live.

FeedbackLive

Comments arrive continuously through several channels and currently vanish into inboxes and messages.

Who uses this page

Recruiting team

Answers candidates properly, screens the basics, and keeps every pipeline visible.

Questions

What data does the Segments page use?

It reads segment records the agent has collected. Saved filters over people. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.