Audience
A segment is a saved query over the contact record, not a frozen list. Filter on custom fields, engagement history, and — uniquely in ONE — Pixel and conversion events. Contacts flow in and out automatically as their data changes.
What you can filter on
The same engine as Mumara Campaigns — but in ONE the conditions can read Pixel and conversion data, so you can segment on what people actually did, not just who they are.
Any profile field with type-aware operators — greater-than on numbers, before/after on dates, contains on text.
Opens and clicks over a window — "engaged in 30 days", "never opened", "clicked the last campaign".
Uniquely in ONE — "viewed pricing", "purchased", "converted in the last 30 days", from your pixel.
On-site behaviour — page views, add-to-cart, custom events fired from your site.
On or off a given list, or inside another segment — compose audiences out of audiences.
Where and how contacts engage — country, region, and the client they open on.
Conditions combine with AND/OR logic and nest into groups for precise, layered audiences.
Why dynamic wins
The difference isn't cosmetic — it's whether the audience you send to is who matches today, or who matched the day you built the list.
Static list
A list captured by an export is accurate the moment you build it and stale by the next day. New matches don't join, lapsed contacts don't leave, and keeping it current means re-pulling it by hand before every send — which nobody does.
Dynamic segment
A segment is a saved query that re-runs whenever it's used. Define "engaged in the last 30 days" once: someone who opens today joins automatically, someone who goes quiet drops out. The audience is correct as of the moment you send.
Built from layers
A single condition is a list. The value is in the overlap — a field, an engagement window, and a conversion event in one query express an audience you could never pull by hand. Each becomes a precise, self-maintaining target.
Because ONE can read conversion and pixel data, "what they did" is a first-class condition — not just "who they are".
Win-back
Bought before · no open in 60 days
Hot prospects
Viewed pricing · not yet purchased
VIP
MRR > $500 · engaged in 14 days
Re-permission
On list · zero engagement in 90 days
Define once, use everywhere
The same saved query drives every send path. Build the audience once and point whatever you like at it; it recalculates each time it's used.
The audience
Point a one-time broadcast at a segment and it reaches exactly who matches at send time — not a stale exported list.
The entry + branch
You are hereA segment is a drip's entry condition and a trigger's match event — "entered the VIP segment" starts a journey; "left engaged" fires a win-back.
The slice
Use a segment as a cut in reporting to see how one audience performs against another — the same definition that targets your sends.
What teams build with segments
“Once we could segment on conversions, not just opens, everything got sharper. “Viewed pricing but didn't buy” became our best-performing campaign — and we'd literally never been able to build that audience before. It just recalculates and sends itself now.”
Verified review
Mumara ONE customer
Common questions
Live. A segment is a saved query that recalculates whenever it's used — at send time for a broadcast, at evaluation for a trigger. Contacts join and leave automatically as their data changes; you never rebuild it.
Custom field values (with type-aware operators), engagement history (opens/clicks over a window), list membership, geography and device, and — uniquely in ONE — Pixel events and conversion attribution. Conditions combine with AND/OR logic and nest into groups.
Because pixels feed purchase and on-site events back to the contact, you can filter on behaviour: "viewed pricing", "added to cart", "purchased in the last 30 days". Most ESPs can only segment on stored fields and email engagement — segmenting on what someone actually did on your site is the ONE difference.
Yes. A segment can reference another segment as one of its conditions, so you compose precise audiences from broader ones without duplicating logic — narrow "all customers" down to "customers in the EU who bought twice" by layering.
Each segment is a set of conditions joined by AND or OR, and you can nest groups — for example, (engaged AND Pro) OR (MRR > $500). That lets you express real audiences rather than the single-condition lists most tools limit you to.
Everywhere a send happens: as a broadcast audience, a drip's entry condition, a trigger's match event (fired when a contact is added to the segment), and a slice in reporting. One definition, reused across the platform.
Yes. A segment defines who matches your conditions; suppression and per-list opt-outs are still applied at send time, so a matching contact who unsubscribed or hard-bounced is never actually mailed.
Related
The typed data segments filter on. Richer fields mean more precise audiences.
Read moreThe ONE-only event source that lets you segment on what contacts did on your site.
Read morePoint a broadcast at a segment and it reaches the right people as of send time.
Read moreStart a drip from a segment, and branch mid-sequence on segment membership.
Read moreA contact being added to a segment is a trigger event — automate the moment someone qualifies as "engaged".
Read moreMumara ONE · Segmentation
Dynamic queries over fields, engagement, and conversion events — recalculated at send time and reused across every broadcast, drip, trigger, and report.
