# Player segmentation for small studios

> Which player segments a small studio should track first, how to build them from lifecycle, behavior, source and build, and what to do with each segment.

By Yos Riady. Updated 2026-11-18. Published 2026-11-18. Canonical URL: https://manalens.dev/blog/player-segmentation-small-studios

Start with four player segments: new, returning, at risk and lapsed. Then split them by acquisition source, build and storefront. On PC, most new players leave fast: the median game in the GameAnalytics Benchmarks Hub kept 6.54% of new players on day 1 in October 2026. Segments show which players stay, and why.

## Key points

- Start with the lifecycle stages New, Returning, At Risk, Churned and Resurrected, because they cover every player and need no extra events.
- Wait for a few hundred players before you trust a segment's rate, since with 50 new players one extra return moves D1 by 2 points.
- A small team should track three to five segments: the lifecycle stages, one behavior segment and one source segment.

## What is player segmentation?

Segmentation splits players into groups that behave differently, so you can compare the groups. An average hides the story. A D7 of 3% could be 8% for players from one creator and 1% for players from an ad.

A segment is a rule, not a list of names. "Players who finished the tutorial on build 571" is a segment. The rule picks new players as they arrive, so the segment stays current.

Sources: Manalens filters and segments documentation; GameAnalytics Benchmarks Hub (October 2026).

## Which segments should a small studio start with?

Start with lifecycle stages, because they cover every player and need no extra events. Add one behavior segment and one source segment next. The lifecycle rules below are the ones that Manalens uses on its Users page.

Each active player has exactly one stage, and the stages are checked in the order of the table, from Churned down to Returning. Activity means page views and custom events from the game.

| Segment | Rule | Question it answers |
| --- | --- | --- |
| New | First active in the last 30 days | Does the first session work? |
| Returning | Active, and not in another stage | Who is the core audience? |
| At Risk | No activity for 14 or more days after earlier activity | Who is drifting away? |
| Churned | No activity for more than 30 days | How many players have left? |
| Resurrected | Active again after a gap of 30 or more days | Did an update or sale bring players back? |
| Tutorial finishers | Did tutorial_complete at least once | Does the tutorial predict retention? |
| Payers | Revenue greater than 0 | Who buys DLC or items? |

Sources: Manalens metrics documentation.

## How do I segment players by behavior?

Use a behavior rule: players who did an event a number of times in a window. The window can be the last 7, 30 or 90 days, or a number of hours or days after the player was first seen. "Completed level 3 within 1 day of first launch" is a strong early signal for many games.

On the Users page, the People filters hold these rules, next to lifecycle, revenue and data source. Through the API, the same rule is a JSON condition.

``` Query parameter
behavior_filters=[{"event":"level_complete","event_type":"track","op":"gte","times":3,"relative_to":"first_seen","window":{"value":1,"unit":"day"}}]
```

Sources: Manalens filters and segments documentation.

## How do I segment by source, build and platform?

Use event filters. They work on every report, on funnels and on retention charts. The App group filters game events by platform, storefront, app version, build and engine. The Acquisition group filters by channel, UTM fields and referrer.

Save a set of filters as a segment so the whole team can reuse it. Note one limit: lifecycle, behavior and revenue rules are People filters, and they apply on the Users page and its audience cards. Other reports show a notice instead of applying them. For funnels and retention, build segments from event filters.

Sources: Manalens filters, segments and app events documentation.

## How many players does a segment need?

A few hundred before you trust a rate. With 50 new players, one extra return moves D1 by 2 points, which is our own arithmetic. A segment of 30 players can look great one week and terrible the next by chance alone.

Fewer, larger segments beat many tiny ones. If two segments differ, check whether the gap is larger than chance with the same test you would use for an A/B test.

Time helps too. A segment that is too small in one week can be large enough over four weeks. Read small segments monthly and large ones weekly, and always note the number of players next to the rate, so nobody reads 50% of 4 players as a trend.

- [A/B testing in games: when is a result real?](https://manalens.dev/blog/ab-testing-games-statistical-significance)

Sources: Manalens A/B test significance calculator.

## What should I do with each segment?

Give each segment one question and one action. Manalens does not send messages to players, so the actions happen in your game, on Steam or in your community channels.

Keep the list of actions short. A segment that never leads to a change in the game or in your marketing is a chart nobody needs, so remove it after a month without a decision.

- New players who did not finish the tutorial: read the first session funnel and fix the largest drop.
- At Risk players: plan your next update post; Steam can show a Major Update in the library of players who own the game.
- Resurrected players: compare their count after each update or sale to see what brings people back.
- Payers: check which levels and builds they reach before buying DLC or items.
- A weak source: compare its D7 with your best source before you spend more on it.

Sources: Manalens documentation; Steamworks Events and Announcements Visibility documentation.

## How do I compare segments on a funnel?

Break the funnel down, or limit it to a saved segment. A funnel can break down by channel, referrer, UTM source, medium and campaign, device, OS, browser or country. In the chart editor you can also enter any event property key, such as difficulty or variant.

Choose whether the breakdown uses the player's first touch or last touch value. First touch tells you where players came from at the start. Last touch tells you what they saw most recently. For acquisition questions, first touch is usually the right choice.

Open Conversion insights under the funnel to see what goes with conversion for the same people, steps and filters. It is a quick way to find a segment worth a closer look.

- [First session funnel and FTUE analysis](https://manalens.dev/blog/first-session-funnel-ftue)

Sources: Manalens funnels documentation.

## How do I review segments each week?

Use the same short routine every week, so changes stand out. Keep notes of each decision and the segment that drove it.

1. Read the count of each lifecycle stage on the Users page and compare it with last week.
2. Read D1 and D7 for your two largest acquisition sources.
3. Read the first session funnel for the newest build against the build before it.
4. Pick the segment with the largest change and write one question about it.
5. Choose one action, and the metric that will show if it worked.

Sources: Manalens filters, segments and retention documentation.

## How do I build these segments?

Manalens is the analytics and growth engine built for games. Install the SDK, add filters for source, build and behavior, and save them as segments for funnels and retention charts.

- [Retention analytics](https://manalens.dev/features/retention)

Sources: Manalens product documentation.

## Frequently asked questions

### What is the difference between a segment and a cohort?

A cohort groups players by when they started, such as the week of their first launch. A segment groups players by a rule, such as source, build or behavior. You often combine them: the retention of each weekly cohort, filtered to players from one creator campaign.

### Can I segment players without accounts?

Yes. Each install has an anonymous ID, and events carry the build, platform and storefront. You can segment by those and by behavior without a login. Call identify only if players sign in, so one person on two devices counts once.

### Can I share segments with my team?

Yes. Segments belong to the project, so every teammate can apply them from the filter menu. When a segment is active, its conditions are added to any other filters on the page. A behavior window such as the last 30 days stays a rolling window, so the segment updates itself.

### How many segments should a small team track?

Three to five. Start with the lifecycle stages, one behavior segment such as tutorial finishers, and one source segment. Add a segment only when it answers a decision you face. Many small segments spread your players too thin to read with confidence.

## Sources

- [GameAnalytics Benchmarks Hub: PC and mobile benchmarks (October 2026 data, read 18 November 2026)](https://www.gameanalytics.com/benchmarks-hub)
- [Steamworks documentation: Events and Announcements Visibility (Valve, read 18 November 2026)](https://partner.steamgames.com/doc/marketing/event_tools/visibility)

## Related guides

- [Game marketing measurement guide](https://manalens.dev/blog/game-marketing-measurement-guide)
- [Cohort analysis for games](https://manalens.dev/blog/cohort-analysis-for-games)
- [Why players quit your game](https://manalens.dev/blog/why-players-quit-game-churn)
- [Lapsed player reactivation after updates and sales](https://manalens.dev/blog/reactivate-lapsed-players-steam)
- [D1, D7, D30 retention calculator](https://manalens.dev/tools/retention-calculator)
- [Player analytics guides](https://manalens.dev/blog/topic/player-analytics)
- [A weekly metrics review for your game after launch](https://manalens.dev/blog/weekly-game-metrics-review)
- [Measure the impact of updates and live ops on players](https://manalens.dev/blog/measure-game-update-impact)
- [What events to track first in your game](https://manalens.dev/blog/game-tracking-plan-first-events)
- [Game metrics every indie developer should track](https://manalens.dev/blog/game-metrics-indie-developers)
