Building a segment
There are three ways to define one:- Rules. Combine the built-in criteria: tags, a minimum contact score, and whether a wallet address is present.
- SQL. Save any query result as a segment. This is how you build on-chain cohorts, since the SQL editor can reach enrichment and messaging data the rule builder can’t. See Segments From Queries.
- Natural language. Describe the audience you want and get back draft rules to review.
Lists and segments share the same backing. A list is just a segment you import into, so a list can be reused anywhere a segment can.
Capture forms create lists too. A form that isn’t bound to a list gets one auto-created and named after the form (backed by a tag of the same name), so confirmed subscribers show up here under a matching list and tag without any manual wiring.
How the rules combine
A rule-based segment supports three criteria, and they’re combined with AND: a contact is in the segment only if it meets every criterion you set.
Leaving a criterion unset makes it a wildcard. A segment with only a tag criterion matches everyone with that tag, regardless of score or wallet.
When a campaign targets several segments plus some hand-picked contacts, those are combined with OR: a contact is included if it’s in any chosen segment or on the explicit list. So within one segment the criteria narrow the audience, and across segments they widen it.
For anything the three criteria can’t express, such as on-chain value, activity recency, or NFT holdings, build the segment in SQL instead. The rule builder is deliberately simple; the SQL editor reaches the enrichment and messaging tables.
Good segment types
- Reachable users on a specific channel (email or in-app)
- Recently active wallets
- High-value cohorts with declining engagement
- Holders of a specific contract or collection
- Query-built audiences ready for follow-up
A holder-based segment is only as complete as your contact list. Running wallet sync discovers the current holders of your configured contracts and adds the new ones as contacts, so a “holders of contract X” segment grows as sync brings in wallets you didn’t have yet, without spending per-wallet enrichment credits to find them.
Best practices
- Name segments by business meaning, not a one-off execution detail.
- Review segments that drive important automation paths; a segment whose criteria drift will quietly change who gets messaged.
- Keep ownership clear when several teams depend on the same segment.
- Preview the count before wiring a segment into a live send.