Loading
A segment is a saved set of conditions — for example “retail companies with 100–500 staff and no activity in 30 days” — that is evaluated every time it is used, so its members always reflect your records as they are now. A list is a dated snapshot of a segment’s members, for when membership must stay fixed. In Treepie Flow segments are shared by Desk queues, Growth campaigns, sequences and reports.
Because the alternative is a CSV. It is exported on Monday, edited on Tuesday, sent to three people on Wednesday, and by Friday four of its accounts have churned and two have doubled.
A segment is a saved query over contacts or companies. It is evaluated when it is read, so its membership reflects the records as they are now rather than as they were when it was built.
You build a segment from any field on the record, including enriched values, deal state and support standing. It has a name and an owner, and anything that can act on a list can point at it.
"Renewals in the next 90 days with an open escalation" is a segment, not a spreadsheet. It was 14 accounts in January and 6 in March without anybody rebuilding it, and Desk changed both numbers.
It is not a static audience. If you need the exact membership as it stood on a date — for a mailing record or an audit — take a snapshot, which is a deliberate and separate act.
Growth targets campaigns at them, sequences enrol from them, routing rules can reference them, and reporting can group by segment membership over time.
| Exported spreadsheets | Static CRM lists | Treepie Flow | |
|---|---|---|---|
| Membership | Correct on the day it was made | Correct until someone forgets to update it | Worked out every time it’s read |
| New customers & unsubscribes | Still on the list | Still on the list | Drop out automatically |
| Data it can use | Whatever was exported | Contact and company fields | Companies, contacts, deals and activity |
| Shared with other teams | Emailed around | Within the CRM only | Desk, Growth, sequences and reports |
| Proof of who was sent to | A file somewhere | Rarely kept | A dated snapshot of every send |
Yes. Support standing from Desk and payment state from Books are on the same record, so they are queryable.
They are evaluated against indexed fields. Very large segments used constantly can be materialised on a schedule.
Only if you share it with edit rights. Shared read is the common case.
Any field on companies, contacts and deals — including custom fields — plus activity such as last email, last call, open tickets and deal stage.
Yes. Group conditions and choose all or any within each group.
No fixed limit. Segments are saved queries, so they cost nothing to keep.
Yes. Segments can be private, shared with a team or shared with everyone, and each reader sees only the members they have access to.
Yes. A sequence or automation can start when a record enters a segment — for example, a check-in task when an account goes quiet.
No. They are evaluated by the same engine as reports, and large segments are counted in seconds.
Yes, as a CSV or through the API. Each export is kept as a dated snapshot.
Accounts with no activity in 30 days. It usually surfaces customers who need attention before anyone has noticed.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.