Run one command on the proxy where DomainStats is installed. The sources in your DomainStats config become campaigns you review before anything is created. Importing player history is coming next.
Every tracking source in your DomainStats config becomes a campaign, with its domains as tracked hostnames. You confirm the list first.
Next up: players with their first join, source, country and edition, read from your DomainStats database on your own server.
Next up: ad slots with their dates and cost as campaign spend, so return on investment carries over.
The Analyse plugin reads DomainStats' config on your server. Your DomainStats login is never needed.
Your DomainStats config has a TikTok source covering two hostnames you give out in videos.
It becomes a TikTok campaign tracking both hostnames, so every player joining through them is credited to it from now on.
You also ran Plan, which kept the address each session joined through.
Create the campaigns first, then import Plan: past sessions are credited to the campaign their address belongs to.
Connect the Analyse plugin to your game where DomainStats runs.
Run /analyse import domainstats. It reads your DomainStats config and sends the sources it found.
In game settings under Import, untick or rename sources, then create the campaigns.
Your tracking sources can be imported today, as campaigns with tracked domains. Player history and ad spend are coming.
The plan is to skip it when Tebex, PayNow or CraftingStore is connected, since those bring exact orders and taking both would count money twice.
They're left out, because campaigns match exact hostnames. Add the hostnames you hand out to the campaign instead.
No. The import reads your own config on your own server. It doesn't use your DomainStats dashboard account.
Free to start, 14 days of Pro, and about four minutes of setup.
