Understand your player audience
Read player activity, retention, join quality, and geography for one server.
Audience summarizes the player sessions that the agent observed on one server. Use it to answer questions such as how many players return, where they connect from, and whether join problems drive players away.
Before you begin
You need access to a Bukkit-family, Velocity, or BungeeCord server whose agent reports player analytics. Members need a grant that includes audience analytics. The data starts when the agent first observed players. Time before installation, and time while the agent was stopped, is missing and not zero.
Audience data describes players. Share it according to your privacy policy and the laws that apply to your community.
Choose a time window
Select a preset range or a custom range, then set the chart interval. Compare like with like: a week against the previous week, or a weekend against a weekend. A window that includes an outage or an event will not match an ordinary one.
Read the views
| View | Answers |
|---|---|
| Overview | How many distinct players, new players, and sessions the window had, and how long sessions lasted |
| Players | Which known players were active, with first seen, last seen, and an activity score |
| Quality | How often joins failed and how many sessions ended almost at once (bounce rate) |
| Sources | Which server address players used to connect, and how that mix changed |
| Geography | Which countries and continents players connect from |
| Versions | Which protocol versions players connect with |
| Cohorts | How many players who first joined in a week or month came back later |
| Incidents | How many players were online during recorded incidents and lag spikes |
Use the filters to narrow a view, for example to one country or one connection address.
Interpret the numbers carefully
- A bounce is a very short session. A spike can mean a join problem, a full server, or a login plugin that rejects players.
- A join failure is an attempt that did not become a session. Compare a spike with Console and with the alerts history for the same time.
- Network labels such as hosting, proxy, or mobile are estimates from the player's address. Geographic data is best effort and can be missing. Do not treat either as proof about one player.
- Cohort retention needs time. A cohort from last week cannot show a four-week return yet.
- A proxy and a backend server see different sessions. Read audience data on the record that matches your question.
Act on a finding
- Note the window, the view, and the reading that concerns you.
- Look for a cause in metrics and the console for the same window.
- Change one thing, then compare the same view over an equal window afterward.
To investigate one player, open Players.
If Audience is missing or empty
Check that the server is a game runtime and that the agent reports player analytics. Check your server access. An empty view on a new installation is expected until players join.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on