Behavioral segments

An audience filter can already match on contact fields — plan, city, signup date. Behavioral segments add a second axis: what a contact has actually done.

Behavioral conditions

Alongside a normal field condition, the audience filter builder offers a Behavior and a Commerce group with seven metrics: opened, clicked, submitted, purchased, RSVP'd, overall engagement score, and total revenue. Each one supports an optional "within the last N days" window, so you can build rules like:

• Opened, but never clicked — a classic re-engagement segment.
• Purchased more than once in the last 90 days — your repeat-buyer list.
• Hasn't opened anything in 90 days — a churn-risk list.
• Engagement score above a threshold — a rough "who's actually paying attention" ranking, decayed over time so an old burst of activity doesn't keep someone looking engaged forever.

These combine with ordinary field conditions and with each other using the same AND/OR groups you already use for a block's visibility rules in the studio.

Saving a segment

Building the same behavioral filter by hand every time you send isn't great, so the Segment picker above the audience filter lets you save one under a name and reuse it. A saved segment is a snapshot of the rule, not a live reference — the same "copy, not a link" approach as saving a project as a template — so editing the rule later doesn't retroactively change a send that already used it. Its displayed member count refreshes on demand and is display-only; the real match always happens fresh at send time.

Where segments show up

Anywhere an audience filter already exists: a manual send, a recurring schedule, and a journey's segment-entered trigger and branch step. A segment scoped to behavior costs one extra read per contact at evaluation time — negligible for a manual send, and only paid by a schedule or journey sweep when its filter actually uses a behavioral condition.

Your plan caps how many saved segments you can have — see pricing.