Saved segments
Define an audience once, use it everywhere. Saved segments are reusable rule sets applied to a guide's targeting the moment it's served — so editing a segment updates every guide that uses it.
Define once, reuse anywhere
Build a segment like “Power users” and apply it to many guides.
Always up to date
Segment rules are applied when a guide is served, so edits take effect everywhere at once.
The same powerful rules
Segments use the same AND/OR trait conditions.
Live in three steps.
Create a segment
Name it and add your rules.
Apply it
Point any guide at the segment.
Edit anytime
Changes flow to every guide using it.
One segment, four guides, zero drift.
The moment two guides target "the same" audience with separately-written rules, the definitions start diverging. Segments exist to kill that class of bug.
Define it once
In Segments, create "Power admins": role equals "admin" AND events_last_30d greater than 100 AND plan in ["pro", "business"]. Name it what a colleague would search for.
Apply it everywhere
The beta invite, the advanced-features tour, the NPS pulse, and the webinar slideout all pick "Power admins" from the dropdown — no rules rebuilt, no copies.
Edit centrally
Marketing decides 100 events is too low. Change it to 250 in one place; all four guides follow at their next serve. That is the whole point.
Audit at a glance
The segment page shows its rules in plain terms, so "who exactly gets the beta?" is a look-up, not an archaeology dig through per-guide settings.
What to expect: Targeting becomes vocabulary: "Power admins", "Trial week 2", "Churn risks" — names the whole team reuses. Four guides, one definition, and an edit that propagates instead of forking.
When not to use saved segments.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
Single-use targeting
A one-off guide for one launch does not need a durable named audience. Inline rules keep your segment list meaningful — a library of twenty "misc" segments helps nobody.
Audiences defined by a moment
"People who just exported a report" is a trigger (the event), not a segment (a property of the user). Segments describe who someone is; triggers describe what just happened.
Reaching anonymous visitors
Segments are built on traits, and anonymous visitors have none — a trait-based segment can only match identified users. For visitors, use the audience setting and URL scoping.
When a segment changes, what happens to live guides?
Segments are evaluated when a guide is served, so edits apply to every guide using the segment from the next serve — no republishing. Powerful, and worth a moment's care: check what uses a segment before you loosen it.
Segments or inline attribute rules?
Same rule engine, different lifetime. Inline rules die with their guide; segments are shared, named, and centrally editable. The rule of thumb: the second time you type the same conditions, you owed yourself a segment.
Can users be in several segments?
Of course — segments are filters, not folders. A user matches every segment whose rules they satisfy, and each guide simply checks the one it targets.
Do segments update as users change?
Yes — membership is computed live from current traits. When seats_used crosses the threshold you set, the user is in the segment that moment, and out again if the trait falls back.
How many segments should a team have?
Fewer than you think: a healthy project runs five to ten named audiences that everyone recognizes — trial admins, power users, at-risk accounts. Past twenty, duplicates creep in and nobody trusts the names. Prune quarterly; merging two segments is a rename, not a migration.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.