Tools

Know how your community is doing.

Growth, activity, and retention for your server, visible to owners and the staff you choose. No spreadsheet exports, no third-party dashboard, no guesswork: the numbers live where your community lives.

What server analytics is.

A built-in dashboard that answers three questions: is the server growing, is it alive, and are people staying?

Most owners run their communities on gut feeling. The server feels busy, so it must be fine. A few regulars went quiet, so something must be wrong. Gut feeling is a real signal, but it lies in both directions: a loud handful of members can make a shrinking server feel healthy, and a quiet week can make a growing one feel dead.

Server analytics replaces the guessing with a small set of honest numbers. Joins and leaves tell you whether you are growing. Messages and voice minutes per channel tell you where the life is. Retention tells you whether the people who arrive actually stay. Those three together describe the health of a community better than any follower count ever will.

The dashboard belongs to the server, not to us. It is visible to the owner and to the staff roles you choose through roles and permissions, and to nobody else. Members do not see it, other servers do not see it, and we do not build anything on top of it. It exists so you can run a better community, full stop.

Built in, not bolted on

There is no analytics script to paste, no pixel to install, and no third-party service quietly collecting your members on the side. Vronify.chat runs with zero trackers, ads, or data brokers, and the analytics dashboard follows the same rule. The numbers are computed from activity that already happens inside your server, on the same infrastructure that delivers your messages, and they never leave it.

That also means there is nothing to set up. The moment your server exists, the counting starts. Come back a week later and the picture is already forming.

What you can see.

Six views of the same community, each answering a different question.

Growth

Joins, leaves, and where new members come from, so you know which invite links and features actually work.

Activity

Messages and voice minutes per channel. See which parts of the server are alive and which need a rethink.

Retention

The number that matters most: how many people who joined last month are still talking this month.

Invite performance

Every one-link invite you share tells its own story. Learn which links bring people in, so you post more of what works and retire what does not.

Channel breakdown

Message counts per channel, side by side. Find the channels doing the heavy lifting, and the ones that have quietly become furniture.

Voice time

Minutes spent in voice channels, per channel. Voice-first communities look dead in message counts; this is where their heartbeat shows up.

How to read each number.

Analytics only helps if you know what the numbers mean, and where they can mislead you.

Growth: watch the leaves, not just the joins

Joins are the number everyone stares at, and the least informative one. A join costs a member nothing; anyone can click a link. What matters is the pair: joins next to leaves. A server gaining fifty members and losing forty-five is not growing, it is churning, and churn usually points at something inside the server rather than at your promotion.

The source breakdown makes joins actionable. When you know which invite links bring people in, whether from the Explore page, a link in a video description, or a friend passing an invite along, you can do more of what works instead of guessing. Post the same link in two places and you will find out, in plain numbers, which audience actually cared.

Activity: concentration is normal, silence is not

Every healthy server concentrates. One or two channels carry most of the conversation, and that is fine; a general channel is supposed to have gravity. The signal to look for is not spread, it is change. A channel that carried a third of your messages last month and nothing this month is telling you something: the topic died, a key member left, or the conversation moved somewhere else.

Count voice separately from text. A community that spends its evenings in voice channels will look inactive if you only read message counts, and it may be your most tightly bonded group. Voice minutes per channel exist exactly so that voice-first communities do not get misread as dying ones.

Retention: the number that keeps you honest

Retention asks the hard question: of the people who joined last month, how many are still talking this month? Raw growth flatters you. Retention does not. You can double your member count with a good promotion push and still be building nothing, because the same push that brought a hundred people in quietly watched ninety of them leave.

When retention is strong, everything else compounds. New members arrive into a room where the people who joined before them stuck around, and that alone makes them likelier to stick around too. When retention is weak, fix that before you spend another minute on promotion: pouring joins into a leaky server just makes the leak bigger.

Where the numbers can mislead you

Every dashboard has edge cases, and we would rather you know ours than discover them the hard way.

  • Small servers are noisy. With twenty members, one person going on vacation moves your activity graph. Read trends over weeks, not days, until the community is large enough for single members to stop dominating the math.
  • Lurkers do not show up in message counts. Someone who reads every day and never posts is a real member, but retention measured by talking will not see them. Low retention in a server people clearly keep returning to often means a posting barrier, not a leaving problem.
  • Events distort everything around them. A game night or an announcement spike pulls activity forward and makes the following week look like a decline. Compare like with like: event weeks against event weeks, quiet weeks against quiet weeks.
  • A first month is not a baseline. New servers get a wave of curious joiners and a wave of early leavers. Both are normal. Judge your trends from the second month onward, once the curiosity traffic has washed through.

Patterns, and what to do about them.

The dashboard shows you the pattern. This table is the field guide.

Joins up, retention down
Often means:Your promotion works but your onboarding does not. People arrive, find no obvious first step, and drift away before anyone notices them.
What to try:Give newcomers a landing spot. A clear rules channel, a visible place to say hello, and a staff habit of greeting new names. The owner handbook covers the first-week experience in depth.
One channel has everything
Often means:Usually nothing bad. General channels are supposed to dominate. It becomes a problem only when your topic channels exist but never get used.
What to try:Prune, do not add. Merge dead channels into living ones and group the rest into tidy categories. Ten quiet channels feel emptier than three busy ones, even with identical activity.
Voice high, messages low
Often means:You have a voice-first community. This is a shape, not a sickness: some of the tightest communities barely type at all.
What to try:Serve the shape you have. Keep voice channels front and center, and use text for the things voice loses: pinned messages, polls, and plans that people need to find again later.
Leaves spike suddenly
Often means:Something happened. An argument, a heavy-handed moderation call, or a rule change that landed badly. Members rarely leave in groups for no reason.
What to try:Reconstruct the day. Check the audit log for staff actions around the spike, ask your moderators what they saw, and read the moderation guide before deciding whether policy or delivery was the problem.
Growth flatlined
Often means:Your existing invite links have reached everyone they are going to reach. The community may be perfectly healthy; the pipeline is just empty.
What to try:Open a new door. Make the server discoverable on the Explore page, refresh your server tags so the right people find you, and share fresh invite links where your audience actually is.
Everything slowly declining
Often means:The hardest one: no incident, no villain, just fading energy. Usually the conversation rituals that made the server feel alive have quietly stopped.
What to try:Restart the rituals. Bring back the weekly thread, the regular event, the question of the day. Communities run on rhythm, and rhythm is something an owner can simply decide to restore.

None of these are rules, they are starting points. You know your community; the dashboard just makes sure you are reacting to what is actually happening rather than to the loudest voice in the room.

A weekly review that takes ten minutes.

Analytics is not a place to live. It is a place to visit, briefly, on a schedule.

1

Pick a day and keep it

Once a week, same day, open the dashboard. Checking daily teaches you to panic over noise; checking monthly lets problems grow roots. Weekly is the rhythm where trends are visible and still cheap to fix.

2

Read growth first, in pairs

Joins next to leaves, this week next to last week. One question: is the balance moving the right way? Then glance at the sources, and note which invite links did the work.

3

Scan the channel breakdown

You are not reading every number, you are looking for movement: a channel that surged, a channel that went quiet, voice minutes drifting up or down. Write down at most one thing worth acting on.

4

Check retention last

It moves slowly, and that is the point. If the people who joined last month are still talking this month, your foundations are sound whatever the weekly noise says. If they are not, that is your project for the week.

5

Do one thing, then close the tab

Merge the dead channel, greet the newcomers, restart the weekly thread. One deliberate action per week beats ten reactive ones, and it keeps the dashboard what it should be: a tool, not a mood.

Numbers you can trust, on a platform built for them.

Your dashboard is only as good as the infrastructure underneath it. Ours is hand-built, from zero to over 125.000 lines of code, on hardware we own and tune ourselves.

50k+
Members supported in a single server
<40ms
Median message delivery in Europe
99.9%
Uptime across the last 12 months
0
Trackers, ads, or data brokers, anywhere

Analytics for you. Not about you.

A dashboard is not a data business.

These numbers exist so owners can run better communities, full stop. They are visible to you and the staff roles you choose, and they are never sold, shared, or used to target anyone with anything. That is the same privacy stance as everywhere else on the platform: we never sell data, never show ads, and never read private conversations.

The clearest line is the one around direct messages. DMs on Vronify.chat are private, which means we don't read them, and a thing we don't read never appears in a dashboard. Server analytics describes servers. Your members' private conversations stay out of it.

What the dashboard is

  • A view for the owner and the staff roles you choose, and nobody else
  • Built from activity that already happens inside your server
  • Computed on our own infrastructure, with no third-party analytics service involved
  • A decision-making tool: which channels to keep, which rituals to restart, where to invest your energy

What it never is

  • A product we sell, share, or trade with anyone, in any form
  • An advertising engine: there are no ads on the platform to target
  • A window into DMs, which stay private and which we don't read
  • A surveillance tool pointed at individual members; for reviewing staff actions, use the audit log

Questions about server analytics.

Who can see my server's analytics?

The server owner, plus whichever staff roles the owner grants access through roles and permissions. Regular members do not see the dashboard, other servers cannot see it, and there is no public stats page unless you choose to share numbers yourself. Access follows your role setup, so promoting or demoting a moderator updates who can look at the numbers the same way it updates everything else.

Do direct messages count toward any analytics?

No, and they cannot. DMs on Vronify.chat are private, which means we don't read them, so there is nothing to count. Server analytics is built only from activity inside your server's channels. Community channels are visible to their community and its moderators, precisely so moderators can keep public spaces safe, and that is the boundary the dashboard respects too.

Is this data ever sold, shared, or used for ads?

Never. Vronify.chat has zero trackers, zero ads, and zero data brokers, and the analytics dashboard is no exception. We never sell data and never use it to target anyone with anything. The numbers exist for one audience, your staff team, and one purpose, running your community well. Our privacy page explains the full stance.

What does "still talking" mean for retention?

Retention compares the people who joined last month with the people among them who are active this month. It measures participation, which means quiet readers will not register even when they visit daily. That is a real limitation worth keeping in mind: a low retention number in a server that clearly has an audience usually means people are hesitant to post, not that they left. Lowering the barrier to a first message, with a hello channel or a running casual thread, often moves the number more than any promotion does.

My server is small. Are the numbers even useful yet?

Useful, but read them gently. In a small server every individual is a visible fraction of every graph, so one busy member on vacation looks like a downturn. Focus on direction over weeks rather than day-to-day movement, and treat retention as your primary number: it is meaningful at any size, because it asks about people rather than volume. The platform itself scales from a friend group to 50k+ members in a single server, and the dashboard grows with you.

Does analytics cost extra?

No. Server analytics ships as part of the platform, the same way channels, roles, and the audit log do. Core features on Vronify.chat are free forever, with optional extras for power users planned later and no surprise paywalls. Understanding your own community is not something we think an owner should have to pay for.

Will the bot engine tie into analytics?

The bot engine is coming soon, and it approaches engagement from the other side: where analytics helps you observe participation, features like leveling and XP, welcome cards, and auto-reactions help you encourage it. They are designed as complements. Watch the changelog for the bot engine release; this page will keep describing the observation half.

Where do I go from the numbers to the fixes?

Start with the pattern table on this page, then go deeper: the owner handbook covers structure, onboarding, and community rhythm, and the moderation guide covers the situations where a leaves spike has a human cause. If you are still setting up, create a server takes you from zero to a live community in minutes, and the counting starts on day one.

Your community. Your rules. Your data.

Create a server, invite your people, and see what chat feels like when your account actually belongs to you.

Free to start. Live in under a minute. No install required.