Segments
Segments built on what users actually do
Combine event behavior, traits, and profile columns into a live audience, or describe it in plain words and let AI Studio draft the rule for review.
Behavioral, not just demographic
Segment on what people did, not just who they are.
Demographic attributes tell you who someone is. Behavioral data tells you what they're about to do.
Demographic segmentation
Plan, role, company size, signup date. Static attributes that describe who someone is on paper, and change slowly if at all.
Behavioral segmentation
Viewed pricing three times this week. Never invited a teammate. Hasn't logged in for 30 days. What someone actually did, which is a far better predictor of what they'll do next.
The rule builder
Nest conditions the way the logic actually works.
Real audiences aren't a single flat filter. The builder lets the rule be as specific as the audience needs.
Nested AND, OR, NOT
Group conditions inside conditions: did X AND (did Y OR did Z) AND NOT did W. The nesting mirrors how you'd actually describe the audience out loud.
Event behavior, exactly
Did, did not, count of times, within a time window. "Viewed pricing at least 3 times in the last 14 days" is one rule, not a spreadsheet formula.
Traits and profile columns
Mix event conditions with traits like plan or role, and profile columns like signup date, in the same rule. One audience, one definition.
Live recompute as data arrives
A segment isn't a one-time export. Membership updates as new events land, so anything targeting the segment always sees who qualifies right now.
Describe it in plain English
Say the audience, review the rule.
Type a sentence like:
“Trial users active last week who never invited a teammate”
AI Studio reads that against your real event and trait schema and drafts the nested rule: active in the last 7 days, trial plan, and no teammate_invited event. It sees your schema, not your customers.
The draft lands in the same rule builder a manually built segment uses. You review the conditions, adjust anything that's off, and save it yourself. The AI drafts, it never saves or activates a segment on its own, and the result passes the same validators as a segment built by hand.
One audience, everywhere
Segments feed automations directly.
A segment isn't a report you export and re-import somewhere else. The same audience definition that shows you a count on a dashboard is the audience an automation or a broadcast can target directly, with no CSV in between and no second copy of the logic to keep in sync.
See how segments fit into the rest of the platform on the features overview, or read about building audiences from real usage on the blog: behavioral segmentation for email.
Example segments
Three audiences, built in minutes.
Common segments teams build on day one, using events and traits they already have.
Power users
Logged in more than 10 times in the last 7 days AND completed onboarding. Your best candidates for a referral ask or an upsell.
At-risk trials
Trial started more than 7 days ago AND hasn't hit the activation event AND hasn't upgraded. Worth a nudge before the trial ends.
Dormant paid customers
Plan is paid AND no login event in the last 30 days. Paying, but not getting value, and quietly at risk of churning.
Build your first segment live.
Connect a source, wait for real events to land, and build a segment on what actually happened.
FAQ
Questions, answered.
How is a segment different from a static list?
A static list is a snapshot: it's accurate the moment you export it and stale immediately after. A GetFluxly segment is a rule, not a snapshot, so membership recomputes as events, traits, and profile columns change, and stays current on its own.
Can I combine event behavior with traits in one rule?
Yes. Event conditions like "viewed pricing 3+ times" and trait or profile conditions like "plan is Growth" live in the same nested rule, combined with AND, OR, or NOT.
Does AI Studio ever save or send a segment on its own?
No. Describe the audience in plain words and AI Studio drafts the nested rule for you to review. It never saves, activates, or sends anything without you approving it first. It sees your schema, not your customers.
What validation does an AI-drafted segment go through?
The same validators a manually built segment goes through. AI Studio drafts against your real event and trait schema, and the rule is checked before it can be saved, whether a person or the AI built it.
Can a segment trigger automations directly?
Yes. The same segment that powers a dashboard count can be the audience for an automation or a broadcast, with no export or re-import step in between.