Analyse
FeaturesRetention

Features

Retention

Track how many players come back on day 1, 7 and 30. Compare retention between campaigns and gamemodes.

Retention is the single most important number for a server. If new players don't come back, nothing else matters. The Retention page turns retention into charts you can actually read and compare.

What retention means on Analyse

Retention is the percentage of new players from a given week that came back on day 1, day 7, and day 30.

  • D1 = of the players who first joined this week, how many joined again the next day
  • D7 = ...how many joined again within 7 days
  • D30 = ...within 30 days

Good servers typically hit 20-30% D1 and 5-10% D7. Great servers go higher. If you're under 10% D1, your onboarding is losing people.

The main chart

The retention line chart shows retention curves over time. Use the view mode to pick how the lines are split:

  • Platform - one line for Java, one for Bedrock
  • Domains - a line per root domain
  • Campaigns - a line per tracked Campaign

Under the chart, a cohort table shows each week's cohort across columns W0 through W8 (weeks 0 to 8 after join). The cells are color-graded so you can scan for cohorts that fell off a cliff.

Summary stats

Above the chart you get the three headline numbers for the selected window:

  • D1 retention
  • D7 retention
  • D30 retention

Plus total new players.

Time range

Pick a time range at the top:

  • 1 week
  • 1 month
  • 3 months

Every chart and cohort row reacts to this.

Comparing cohorts

The cohort table is where retention becomes actionable. A row that dips hard on W1 when every other row holds up means something specific went wrong that week: a lag spike, a bad update, a creator that sent bots, etc. Click through to Players or Campaigns to investigate.

Splitting by Campaign vs Platform

Switching to Campaigns view in particular is where you learn the most:

  • "The Discord campaign has 2x the D7 retention of the TikTok campaign" is an actionable number.
  • Global retention is a vanity number. Always split before making decisions.

Tips

  • Set a baseline, then move it. Write down your current D1 and D7. Any change you make (a new spawn, a new tutorial, a new kit) should move one of these. If it doesn't, it didn't matter.
  • Weekly review. Glance at the cohort table every Monday. Vertical stripes of "this cohort did bad" always have a story.

Network-level retention

If you want retention across every Server in a Network, open the Retention page from the Network in the sidebar instead of from a single Server. It's a separate page that rolls up the numbers.

  • Sessions for a closer look at what's happening during a visit
  • Funnels for finding the exact step where new players leave
  • Retention playbook for a checklist of changes that actually move retention