Integrations
Geyser and Floodgate
Track Bedrock players joining through Geyser or Floodgate so your platform split stays accurate.
If you use Geyser or Floodgate to let Bedrock players on your Minecraft server, Analyse supports them out of the box. You'll see every Bedrock player correctly tagged as Bedrock in Players, Sessions, Retention, and Revenue.
No extra plugin. No configuration hack. Just one setting to verify.
How Bedrock detection works
Geyser and Floodgate prefix Bedrock player usernames with a symbol (by default . for Geyser, or the Floodgate prefix you set). Analyse reads that prefix and tags those players as Platform = Bedrock.
Quick setup
- 1
Install Geyser or Floodgate the way you normally would
Instructions live on the Geyser docs site.
- 2
Note the prefix
Default is
.for Geyser. If you run Floodgate, your prefix is inplugins/floodgate/config.yml(often*or.). - 3
Open the Analyse plugin config
Usually
plugins/Analyse/config.ymlon your game server. - 4
Set the bedrock-prefix value
Match whatever Geyser or Floodgate is using. Example:
bedrock-prefix: "." - 5
Restart the server
From the first Bedrock join after restart, all Bedrock players are correctly tagged.
Confirming it works
Have a friend join on Bedrock (phone, console, Win10). In Analyse:
- Their Player row shows
Bedrockunder Platform - Their Session shows the Bedrock version string
- The Platform chart on the Overview shows the Bedrock count tick up
If they show up as Java, the prefix in your Analyse config doesn't match the prefix Geyser or Floodgate is using. Fix the config and restart.
Why this matters for your data
Bedrock and Java players behave very differently. On most servers:
- Bedrock players have shorter average session length
- Bedrock retention is usually lower on day 1 but stickier on day 7 (the ones who stay really stay)
- Bedrock purchase conversion is often lower, but they tend to buy cosmetics over power
- Tutorials designed for Java keyboard controls often lose Bedrock players in the first 2 minutes
Knowing the platform lets you split every chart by it and adapt your server for both audiences. See A/B testing ideas for a Bedrock-specific onboarding test that almost always wins.
Known quirks
- Xbox gamertags with spaces: Analyse handles them. They show up with the space replaced by an underscore the same way Geyser handles them internally.
- Bedrock-only accounts: if a player has no Java account, Analyse uses the Geyser-generated UUID. This is stable, so Player history works across sessions.
- Linked vs unlinked accounts: if a player uses Floodgate to link their Java and Bedrock account, they show as one Player in Analyse, not two.
Keep an eye on the Bedrock column
If your Bedrock percentage suddenly drops or spikes, it's usually a Geyser or Floodgate config change, not an audience shift. Check the plugin version and prefix first.
Related
- Players with Platform filter
- Retention split by platform
- Geyser docs for install help