Getting started with Joinometry#

Joinometry helps you understand where Minecraft players come from, which campaigns bring valuable players, and how that traffic turns into revenue.

The fastest path is to follow the guided setup on the Overview page. You do not need to configure everything at once, but each step makes the dashboard more useful.

1. Create your first server#

Open Servers and create the server players connect to first.

• If players join through a Velocity, BungeeCord, or Waterfall proxy, create the proxy as an Entrypoint.
• If you run one standalone Paper server, create that Paper server as an Entrypoint.
• If you have backend servers behind a proxy, add them later as Backends.

2. Install the plugin#

Download the matching plugin from your server page. Put it in the server's plugins folder, restart the server, and paste the credentials Joinometry shows you.

Credentials are shown once for safety. If you leave the page before saving them, rotate the credentials and use the new values.

3. Confirm the heartbeat#

After the server restarts, the server page should show a recent heartbeat. That tells you the plugin can reach Joinometry.

If the heartbeat does not appear, see Troubleshoot missing events or heartbeat.

4. Create a campaign#

Open Campaigns and create a campaign for one traffic source: a creator, server list, ad, Discord post, vote link, or promotion.

Give it a clear name, choose the source, and add start/end dates if you know them. You can add spend now or later.

5. Map a hostname#

Assign the hostname players use for that campaign, such as play.example.com, creator.example.com, or vote.example.com.

For most networks, map hostnames to the proxy entrypoint, not to backend servers.

6. Connect revenue#

If you use Tebex, set up automatic revenue tracking from the server page. If you already have older sales, use the Imports page to bring in historical revenue.

7. Check your first results#

After a few joins and purchases, open Overview, Acquisition, Campaigns, Revenue, Players, and Cohorts. The first useful signal is usually:

• a heartbeat on the server,
• recent join events,
• a campaign receiving traffic,
• a purchase connected to a player,
• revenue attributed to a campaign.