Spigot, Velocity, or BungeeCord: which plugin should I install?#

Install the plugin on the place that sees players enter your network.

Use Velocity for Velocity proxy networks#

If players join through a Velocity proxy before reaching Hub, Survival, Prison, or other servers, install the Velocity plugin on the proxy.

Velocity is usually the best choice for networks because it can see the hostname players used when connecting. That hostname is what Joinometry uses to connect campaign traffic to players.

Example:

• Proxy: Velocity, public address play.example.com
• Backends: Hub, Survival, Prison
• Recommended setup: install Joinometry on Velocity first, then add backends if you want deeper session and playtime detail.

Use BungeeCord for BungeeCord or Waterfall networks#

If players join through a BungeeCord or Waterfall proxy, install the BungeeCord plugin on that proxy.

The BungeeCord plugin uses the same Joinometry credentials and sends the same proxy-style events as the Velocity plugin where the BungeeCord API exposes the same information.

Use Spigot for standalone servers#

If players connect directly to one Spigot server, install the Spigot plugin there and mark that server as an Entry point.

This is the simplest setup for a single-server community.

Use Custom only when you are building your own integration#

Custom servers are for custom tracking integrations. Most users should choose Spigot, Velocity, or BungeeCord.

Can I install both proxy and Spigot plugins?#

Yes, absolutely. Start with the entrypoint first, as that's where the valuable data comes from. For a proxy network, that usually means Velocity, BungeeCord, or Waterfall, and add backend servers after the entrypoint is working. The entrypoint tells us which hostname a player used to connect, and the backend servers send player-specific information like playtime.