A segment builder with a real operator catalogue — opens, clicks, tags, verification status, typed custom fields and signup date. Build the audience once. Use it for campaigns and automations.
A segment is a set of conditions against a list. Pick a field, pick an operator, give it a value. Stack as many as you need. The segment is saved, named and reusable — it is not a one-off filter you rebuild every time you send.
Because segments are per-list, the fields on offer are the fields that list actually has. No phantom attributes, no cross-list drift.
No vague "smart" targeting. Here is precisely what you can ask of a subscriber record.
equalnot equalcontains / not containsstarts with / not starts withends with / not ends withgreaterlessblanknot blanklast opened less than N days agolast opened greater than N days agolast clicked less than N days agolast clicked greater than N days agotag containstag not containsequalsnot equalsgreater / lessin the last X daysEngagement operators read the subscriber's real open and click history. Verification status is written by the verification job. Tags are whatever you put on the record.
Last opened greater than 60 days ago, last clicked greater than 90 days ago, verification status equals deliverable. That is your win-back audience — and only the addresses worth mailing.
Verification status not equals risky. Attach it to every broadcast. The addresses that would bounce never enter the send in the first place.
Created date in the last X days, tag not contains welcomed. Point an automation at it and the welcome sequence looks after itself.
Plan equals pro. Company not blank. Country contains UK. Your fields are typed and sortable, so comparison operators behave the way you'd expect.
Open the record and you get the timeline: how they arrived, what they opened, what they clicked, what tags they carry, what the verifier said about the address. This is the same data the segment operators query — so what you read on the record is what the segment will match.
Tags can be added and removed individually or in bulk. Subscribers can be copied or moved between lists, deleted in bulk, or blacklisted outright.
Building the audience is the easy part. The point is what happens next — and in CleverlyBox a segment is a first-class input to the two things that send email.
Pick it as the recipients of a campaign. Or point an automation at it and let the flow decide who enters. Same definition, one place to change it.
Segments and verification share one subscriber record. Clean the list, and the segment tightens automatically.
No. Segments are per-list by design — the fields, tags and engagement history belong to a list, so the segment does too. If you need the same audience logic across two lists, build it in both, or copy/move the subscribers into a single list first.
Yes. Engagement operators query real open and click history: last opened less than or greater than N days ago, and the same pair for clicks. That is how you build re-engagement and win-back audiences without exporting anything.
The verification job writes a status onto each subscriber record. Segmentation exposes that status as an operator — equals or not equals. So you can exclude risky addresses from a broadcast in the same tool that cleaned them.
Custom fields are typed and sortable, so greater/less behave sensibly, and blank / not blank let you catch incomplete records. Contains, starts with and ends with are all available for text.
Subscriber management supports bulk tag add and remove, bulk delete, blacklisting, and copying or moving subscribers between lists — so a segment can be the starting point for cleanup as easily as for a send.
Segments, verification, campaigns and automation on one subscriber record.