Sessions

A session is one visit: from the moment a player joins until they leave. Analyse captures every session on your Server and exposes it in two places that each answer a different question.

• "What did this player do?" → the Player detail page shows that player's full session list, with hostname, join time, length, and playtime totals.
• "What do new players do in their first minutes? Where do they drop off?" → Session Insights shows the aggregate: the most common events right after join and right before leave, grouped by hostname or by Campaign.

What a session captures

Every session automatically captures:

• When the player joined and when they left
• How long they played
• The hostname they joined through (used for Campaign attribution)
• The Minecraft version the player was on
• Any custom events fired during the session

Per-player session list (Player detail page)

Open any player from the Players page and you'll see their own history:

• Number of sessions on your Server
• Average session length
• Total playtime across all sessions
• Last active
• Individual sessions with join time, hostname, and length

This is the page to open when you want to understand a specific player: "Where did this whale come from? How long have they been playing?"

Session Insights (aggregate view)

The Session Insights page answers the question every server owner asks but can't easily measure: "What's actually happening in the first minutes of a session?"

It surfaces:

• Post-join event distribution. Out of all sessions in the window, what are the top events that happen in the first few minutes? (Commands typed, blocks placed, shops opened, whatever your plugins track.)
• Pre-leave event distribution. Out of all sessions, what are the most common events right before the player logged off.
• Comparisons. Switch the view mode to group by hostname or by Campaign so you can compare audiences side by side. There's also an advanced filter panel to narrow by a specific event name or event property / value.

The time window (how long "post-join" lasts) and how far back to look are both configurable.

What you learn from it

This is pattern-spotting, not "what did this one player do":

• If 60% of new sessions end with "tried to open /shop" in the pre-leave breakdown, your onboarding flow needs work.
• If the post-join events for your YouTube Campaign differ a lot from your TikTok Campaign, the audiences are literally playing your server differently.
• If the most common pre-leave event is a specific broken command, you just found your top retention bug.

Tips

• Sessions under 60 seconds are usually a spawn or lag issue. Check the Player's first hostname to see where they came from, then look at Session Insights for that Campaign to see what the broader pattern is.
• Compare post-join events between your best-retaining Campaign and your worst. The delta shows you what "good" engagement actually looks like on your server.
• Don't over-filter in Session Insights. Start with "all sessions", spot a pattern, then narrow down.

What about proxy-only setups?

In proxy-only setups (BungeeCord or Velocity on the proxy, no backend plugin), sessions still capture joins, leaves, server switches, and proxy-level commands, but not block-level or death-level events, and not per-gamemode first/last action. See proxy-only setup for the full trade-offs.

Related

• Players for the per-player view that lists sessions
• Retention for long-term comeback patterns
• Custom events to feed richer data into Session Insights