Import from Plan and DomainStats

Switching from another analytics plugin doesn't mean starting your charts from zero. The Analyse plugin reads the other plugin on your own server and sends its history to your game. No database passwords leave your server.

Both imports need the Analyse plugin connected to the game (see Install) and the analyse.admin permission. Follow them in the dashboard under the game's Settings, Import.

Plan: Player Analytics#

Run this in the console of the server or proxy where Plan is installed:

/analyse import plan

What comes over

• Every Plan session, as a join and a leave at its original time, so sessions, playtime and retention cover your past.
• Each player's first join, so long-time players aren't counted as new.
• The address each session joined through, so hostname campaigns and traffic sources include history.
• Countries, from Plan's geolocation data.
• Bedrock players, marked as Bedrock.

How it runs

• It reads Plan through Plan's own Query API (Plan 4.9 or newer), so it works on SQLite and MySQL alike.
• It works in pages of 500 sessions, off the main thread. Run the command again while it runs to see progress.
• Only sessions that ended before your game's first live join are imported, so nothing is counted twice.
• If the server restarts, run the command again: it continues where it stopped. Importing the same history twice isn't possible.
• /analyse import cancel stops after the current page. Pause in the dashboard does the same.
• On a network where Plan runs on the proxy and the backend servers, sessions from the proxy are skipped so each visit counts once.

Plan's players online samples, kills and world times aren't imported.

DomainStats#

Run this on the proxy or server where DomainStats is installed:

/analyse import domainstats

It reads the tracking sources from DomainStats' config.yml. Each source becomes a proposed campaign, with its domains as tracked hostnames. Nothing is created until you review the list under Settings, Import, where you can untick sources and rename them.

• Domains another campaign already tracks stay with that campaign.
• Wildcard domains are left out, because hostname campaigns match exact hostnames.
• Run the import before /analyse import plan if you use both: imported Plan sessions are then credited to the campaigns their join address belongs to.

Importing DomainStats' player history and ad spend is coming.

See what can be imported#

/analyse import

Lists whether Plan is installed and whether a DomainStats config was found on this server.