Server Statistics
The Statistics tab is rebuilt from scratch and served by your own bot. Over forty views of what happens on your server, stored in your bot's own database. It counts what happens, and never stores what anyone wrote.
/serverstats
Server statistics for the last 7 days
Collected and stored by this server's own bot.
Messages
18,402
Voice time
312 h
Joins
241
Leaves
96
Busiest channel: #general
Illustration only - actual interface and behavior may differ
What you get
The Statistics tab was rebuilt from scratch. It covers activity, channels, people and the modules you run. Module cards appear once the module is switched on for your bot.
Activity
- Messages sent over time
- Voice time across your server
- Joins and leaves
- A heatmap of when your server is busiest
- Busiest days of the week and hours of the day
Channels
- Which channels are busy
- Which channels have gone quiet
- Leaderboards by channel and by category
People
- Activity by role
- Your most active members
- Rising stars, and regulars who are going quiet
Growth and retention
- Member flow: joins, leaves and net growth
- Retention cohorts and lurker rate
- New versus returning posters
- How long new members take to write their first message
Commands
- Your most used commands
- Command failure rate
- Command usage per module
Modules
- Moderation
- Tickets
- Giveaways
- Levels
- Invite tracking
- Suggestions and applications
- Activity streaks and economy
- Custom commands
What it records, and what it never touches
Everything analytics stores is a number or a date. Until you switch it on, none of it exists: the database tables are never created, your bot attaches no listeners, and it does not ask Discord for the events involved.
What gets recorded
- Server totals per day and per hour: messages, slash commands, reactions, voice seconds, threads, joins and leaves, first-time posters, and a daily member snapshot
- How often each kind of automatic moderation fired, by trigger type. Who triggered it is not stored
- Message counts per channel and per role, per day
- Per member: messages, reactions and voice seconds per day, a lifetime message total, and the dates of the first message and the last activity
- A capped list of recent events, each holding an event type, a member ID, a channel ID and a timestamp
What is never recorded
- The text of a message
- Attachments, images, files or links, neither their contents nor how many there were
- Message edits or deletions
- Direct messages. Only activity inside the server counts
- Channels your bot cannot see
- Other bots. Their messages and commands are ignored
Analytics stores no message text, and asks for no permission to read one
Counting a message needs no text. Discord tells your bot that a message happened without including what it said, and analytics never requests the permission that would add it. Some other modules do need that permission and ask for it when you switch them on. Even then nothing in analytics reads message text, and there is no field in the analytics data that could hold one.
It runs on your bot
Your bot collects the data and writes it to its own database, on the Bot-Host you picked. SCNX does not pool it with other servers, and the dashboard keeps no copy: it asks your bot for the figures each time you open the tab.
Activity in your server
Messages, voice, joins, module events
Your own bot
Collects and writes the numbers itself
Your bot's own database
Never pooled with other servers
SCNX dashboard
Asks your bot on each visit. Stores no copy.
Your bot runs on the Bot-Host you picked. Hosts sit in different regions, so that choice decides which country the data is physically in. If your bot is stopped, the dashboard has nothing to ask, and the tab tells you so.
Privacy and control
You decide what happens to the data. Export it, delete it, or let members take themselves out of it.
Download a copy
Under Privacy on the Statistics tab, for the server owner. The file is built in your browser from your bot's answers, and nothing is stored at ScootKit along the way. It covers your whole history whatever range is on screen, includes cards you have hidden, and always lists anything that could not be exported.
Delete all of it
You tick a confirmation first, and it cannot be undone. The deletion runs as one database transaction, so it either completes in full or changes nothing, and you get a report table by table with a row count for each.
Member opt-out
Off by default. Switch the Let members opt out of analytics setting on and a member can run /analytics-privacy. Their per-day records are anonymised, their totals and dates cleared, and their recent activity deleted. Server totals stay intact, only the link to the person disappears.
How long it is kept
Daily and hourly totals, and the figures per channel, per role and per member, are kept until you delete them. The list of recent individual events has a fixed size cap and the oldest fall off: a few days back on a busy server, a few months on a quiet one.
Two things a delete leaves behind
Your members' opt-out choices, so deleting the data does not quietly re-enrol anyone who opted out. And disaster-recovery backups, where a copy can persist for up to 90 days.
The data is your responsibility
As the server operator you are responsible for your members' activity data, not SCNX. Check what applies to your server and decide whether you want to offer members the opt-out. What is recorded and how long it is kept is documented in full.
For your members
Your members do not need dashboard access to see how the server is doing. Two slash commands cover it, and you can switch either one off.
/mystats
Your activity on this server
Only you can see your own figures.
Messages
1,284
Voice time
26 h
Most used channel
#off-topic
Level
14
Opt out any time with /analytics-privacy
Illustration only - actual interface and behavior may differ
Read it the way you need
Pick a timeframe, set your timezone and look back at the year.
Three timeframes
Last 24 hours, last week or last 30 days. Every card follows your choice, and the figures are fetched fresh from your bot each time you open the tab.
Your own timezone
Days and hours follow the timezone the server owner sets, UTC by default. A change applies to activity recorded afterwards.
Server Wrapped
Around the end of each year a shareable summary of your server's year appears. Past years stay available.
Share access with your team
Owners and co-owners can open the tab, and trusted admins can be given the View and use analytics permission. Only the owner changes privacy settings or downloads and deletes data.
Arrange the tab your way
Every server watches different numbers. Set the Statistics tab up the way you use it.
Drag cards into order
Put the cards you check every day at the top and the rest below.
Hide what you do not need
Hidden cards disappear from the tab and are never calculated.
Frequently Asked Questions
In your own bot's database, on the Bot-Host you picked. Bot-Hosts sit in different regions, so that choice decides which country the data is physically in. It is never pooled with other servers, and the SCNX dashboard keeps no copy: it asks your bot for the figures each time you open the tab.
No. Analytics records counts and timestamps only, and it never asks Discord for the permission that would let it read message text. Some other modules do need that permission and request it when you switch them on. Even then nothing in analytics reads message text, and there is no field in the analytics data that could hold one.
Daily and hourly totals, and the figures per channel, per role and per member, are kept until you delete them. The list of recent individual events has a fixed size cap and the oldest entries fall off, which reaches back a few days on a busy server and a few months on a quiet one.
If your server already had statistics, the history was carried across automatically and the old copy was removed. The old system never recorded joins, leaves or first-time posters, so for dates before the transfer those figures show as not recorded, and the handover point is marked. Analytics is now collected by your own bot only.
Yes, once you switch the member opt-out on, which is off by default. A member then runs /analytics-privacy: their per-day records are anonymised, their lifetime total and their first-message and last-active dates are cleared, and their recent activity records are deleted. Their future activity still counts in the server totals with no link back to them. It applies immediately and they can opt back in later, but removed data stays gone.
Once. After you switch statistics on under the Statistics tab, restart your bot with the button shown there. Nothing is recorded before that restart, and new activity shows up within about a minute after it.
Your server needs its own bot on SCNX, on a recent version. The server owner or a co-owner switches analytics on in the dashboard, then you restart the bot. The Server Members Intent must be enabled for the bot in the Discord Developer Portal. Nothing is recorded before the restart.
You are, as the server operator. In data-protection terms you are the controller and ScootKit is the processor, under the Data Processing Agreement that comes with your SCNX contract. Whether analytics runs, what the figures are used for and when they are deleted are your decisions. What is recorded and how long it is kept is documented in full at docs.scnx.xyz.
Statistics that stay on your bot
Switch the Statistics tab on, restart your bot once, and it starts collecting into its own database.
Get started