Optimize
Segments
A saved rule for a group of players, reused by experiments, remote configs and analytics.
A segment combines a player’s shipLua totals (sessions, playtime, purchases, Robux spent, first and last seen, country, platform, build, level) with events they did or did not send in the last 1 to 90 days. Conditions sit in “all of” or “any of” groups, nested up to three levels.
Membership is worked out on shipLua’s servers when a segment is used. Your game never sees segment rules or other players’ data. Only live events count; Studio test events do not.
Members
A segment’s page shows how many players are in it now and its rule in plain words. The count is kept for 15 minutes, then counted again, and shipLua recounts active segments in the background, so lists show a recent number without waiting. Editing the conditions clears the count. Snapshots keep the size at one moment for later comparison.
From a funnel drop-off
On a funnel’s Drop-off view, Make a segment from this drop-off drafts a segment of players who did one step but not the next, over the same number of days as the funnel range. Segments do not know a funnel’s order or window, so the count can differ slightly from the funnel. See Funnels.
Using a segment
Pick a segment as the audience of an A/B test or a remote config rule, or filter analytics to it. Archived segments leave the pickers but keep working where they are already used.