# Saved player segments

Choose Player segment on supported analytics pages to reuse a named group of players. Members, admins and owners can create and edit up to 100 segments per game. Viewers and recipients of shared games can read them. Rules match platform, build, a level prefix, up to five exact event-property values, and up to five behaviour rules.

**Behaviour rules** select players by what they have done, read from their retained history up to the end of the query window: total spend in minor units of one named currency (never converted), total playtime in seconds, number of sessions, or whole days since last seen, each as at least or at most a whole number. Ad revenue rules are listed but refused until ad revenue data is available. For remote config and experiments, membership is worked out once an hour for each behavioural segment a config rule or a running experiment uses, so the config fetch never waits on the event store. A segment with more than 100,000 matching players is not used at fetch time and says so; split it with another rule. A game can use up to 20 behavioural segments in remote config and experiments; more are listed as over the limit and match nobody at fetch time.

**Device IDs are not secret.** A config fetch trusts the device ID the game sends, so anyone with the build's key and another player's device ID can read that player's values, and from them which segments the player matched. Do not target a sensitive behavioural segment, such as high spenders, with a value whose presence reveals the targeting.

All rules must match the same event during the query window. Analytics then reads the matching players, retaining their full history for session lengths, first-seen retention cohorts and purchase deduplication. Activity uses its own trailing 30-day window. Synthetic-player settings still apply. Property comparisons use stored text and are case-sensitive.

Segments apply to Overview, metrics, Players, levels, retention and activity, Monetization, Economy, Health, Builds, Why it moved, Progression, Distribution, funnels, property breakdowns, Explore and engagement. Long-range rollups, activity-history charts, session timelines, studio portfolio queries, realtime and SQL do not apply saved segments. Player Insights labels its whole-game history separately.

Website analytics requests accept `segment`. Supported MCP and REST analytics reads accept `segment_id`; MCP `list_segments` lists definitions at the usual programmatic rate. Explicit platform, build, level-prefix and property values replace the corresponding saved rule while preserving other rules. A segment from another game is refused. The hosted analyst does not advertise segment selection.

Saved views keep the segment ID, so editing its rules changes future results. Remove references from saved views before deleting a segment. Deleting a game removes its segments. Segment definitions contain no keys or player credentials.

Source: https://ravensight.io/docs/saved-segments/
Last updated: 2026-11-15
