Vote tracking and vote ROI

#How it works

A server list site sends a vote to Votifier or NuVotifier on your server. The MCAnalytics connector listens for that vote and sends the site name, the player name, the player's UUID when the server knows it, and the time.

The Votes page shows votes per day and per site, how often players vote, the top voters, and votes no player matched. Vote ROI compares each site's voters with players who did not vote.

The page is on the Network plan and up. Votes are recorded on every plan that is active, so an upgrade shows the votes you already had.

#Set it up

You need connector 1.0.15 or newer. There is nothing to switch on in MCAnalytics and nothing to add to the connector config.

• Install NuVotifier where your votes arrive: on the Velocity proxy, or on each Paper server if you run without a proxy. The classic Votifier plugin works on Paper too.
• Give each voting site the host, the port (8192 by default) and the public key or token from the NuVotifier config, the way the site asks for them.
• Restart, then check the connector line in the console. It says when it attached to Votifier and that votes will be reported.
• Send a test vote. On Paper run /testvote YourName serviceName=Test, on Velocity run /ptestvote with the same arguments, or use the test button many sites have. It shows on the Votes page within a minute.

#How a vote finds its player

A voting site only knows the name the player typed. The connector looks that name up on the server it runs on: a player who is online, or on Paper a player the server has seen before. On Velocity it knows players who joined the proxy since it last started. When the name resolves, the vote carries that player's UUID, and Bedrock players carry their XUID.

MCAnalytics then matches the vote to a player by premium UUID, Bedrock XUID or cracked UUID. A vote is never matched by name alone, so a typo or a name someone else took never lands on the wrong player.

A vote that matches nobody is kept as unmatched. It still counts for its site, and the Votes page lists the names that came in. If it carried a UUID, it is matched once that player has joined and votes again.

#How vote ROI is counted

Back by Day 7 is the share of a site's voters who had a session that counts as a return between Day 1 and Day 7 after their first vote on that site in the window. Day 1 starts 24 hours after the vote, so a session the same day does not count.

Players who played in the window and did not vote are the baseline. Each one is counted from their first session in the window, on the same rule. The table shows each site against them in points.

Revenue: every completed store purchase goes to the site of the buyer's most recent vote in the window, if that vote came no more than 30 days before it. One purchase goes to one site, so the sites add up. Amounts stay in the currency the store charged.

This shows what voters did next, not that the vote made them do it. Players who vote are often your most loyal players already.

#Limits

• Up to 300 votes a minute per network. More than that waits on the server's disk and is sent after.
• A vote is kept on the server's disk for up to 7 days while MCAnalytics is out of reach, then sent.
• Site names longer than 64 characters, and names with characters a Minecraft name cannot have, are not recorded.
• Days on the Votes page are UTC days.
• The IP address a voting site sends is never sent to MCAnalytics.