Countries
Playerbase → Countries (/p/<projectId>/playerbase/countries)
Why this page exists
Countries helps you see where your players are when they connect: useful for language choices, support hours, regional pricing, partner deals, and marketing (geo-targeted ads or creators). It also shows where your traffic is not if you expected a different mix.
How to use it
Set a date range that matches the question (for example “last 30 days” for a steady view, or a launch week for a campaign).
Start with the map for a quick geographic picture, then use the table for exact sessions and unique players.
Sort by country name, total sessions, or unique players to find your top markets and long-tail regions.
Use pagination and items per page when you have many countries.
How to read the numbers
Higher unique players in a country means more distinct people from there, not just repeat logins.
Sessions can be higher than uniques when people play often; both matter depending on whether you care about reach or engagement.
When the map can mislead
Country data comes from IP-based location. It is not perfect:
VPNs, mobile networks, and hosting proxies can show the wrong country.
Minehut, TCPShield, and similar services must forward the real client IP correctly, or everyone may look like they are in the same region as the proxy.
If numbers look wrong, fix IP forwarding on your host first; then treat this page as directional (good for “mostly EU vs mostly US”), not legal proof of location.
Tips
Compare Countries with Join addresses or campaigns to connect traffic sources to regions.
If you run multi-region servers, remember each server’s audience may differ; use server-level views elsewhere when available.
Last updated