Funnels and retention for Minecraft plugins
See where players give up between joining and finishing your game, where servers stop between installing and setting up, and who keeps your plugin.
The problem
A server count goes up and you feel good. But are servers finishing setup? Do players who join ever start a game? Do servers still run your plugin a month later? A count can hide a leaky bucket.
How it works
- Track the steps that matter with one line each, or use the commands and events already recorded automatically.
- The first time each player or server does each step is recorded once, with players as an anonymous hash that differs on every server.
- Build a funnel from 2 to 8 steps in the dashboard; the biggest drop is highlighted.
analytics.track("game_started", player, "mode", "solo");
analytics.track("game_finished", player);What you see
- Player funnels: joined → started a game → finished it
- Server funnels: installed → created an arena → enabled it
- Conversion and average time between each step
- Install retention: how many servers still run your plugin each week after installing it
Questions
Do I need to track every step myself?
No. Player joins, installs and every command are recorded automatically. Add track() calls only for the steps that are specific to your plugin.
Are players identifiable?
No. A player is a salted hash that differs on every server and never leaves it in clear.
Which plan includes funnels?
Pro and Premium. Free covers servers, events, errors and listing analytics.
Try it on your plugin
Free for your first plugin. One line in onEnable.