Skool analytics explained

If you own a Skool community, you have numbers. The question is what they mean and what you are supposed to do with them on a Tuesday morning when the room feels quiet.

This is a plain walkthrough. No screenshots, because Skool ships changes to its admin surfaces regularly and any screenshot in an article is out of date the week after it is published. Go open your own admin area alongside this and check what is actually there for you today. What follows is the shape of the thing and, more usefully, how to read it.

What numbers can I see as a Skool community owner?

The numbers a Skool community owner can see fall into four families: the roster, activity, the leaderboard, and revenue if the community is paid. Almost everything you will look at belongs to one of those four groups.

1. The roster

Your list of members. Names, join dates, community level, and whether their subscription is live. This is the foundation, and it is the most under-used surface in the whole product, because owners glance at the total and move on.

The total is nearly meaningless on its own. A community of 500 where 30 people talk is a different business than a community of 500 where 200 do. The roster becomes useful the moment you start slicing it — by when someone joined, by whether they have ever posted, by whether they showed up this month.

2. Activity

Posts, comments, who has been around lately. This is the pulse. It tells you whether the room is warm or cold right now.

The trap here is that activity is dominated by a small number of people in almost every community, so the aggregate number can look healthy while ninety percent of your members have never typed a word. If 40 of your 500 members commented this month, that is 8 percent participating, and the other 92 percent are invisible inside a chart that says "activity is up."

There is a second trap hiding inside the word engagement, and it is worth pinning down before you read another number. Participation rate counts true interactions with posts — comments, comment replies and poll votes. A member only counts if they actually did something. A visit-based engagement rate counts anyone who loaded the page in the window, including the member who read nothing, said nothing and left. As of July 2026, Skool's own dashboard reports engagement on a visit basis; check yours directly, because Skool ships changes often. Both are legitimate definitions serving different purposes, but the visit-based number is always the bigger and more flattering one. A community can display a perfectly respectable engagement percentage while almost nobody is talking. Participation rate is the smaller, harsher figure, and it is the one that moves when you do something right.

3. The leaderboard

Skool's gamified contribution ranking, visible to members over rolling windows. It is unusual among community numbers in that members can see it, and anecdotally they visibly respond to it — owners routinely report members watching their own position and climbing.

As an analytics surface it tells you who your top contributors are, which matters. What it does not tell you is who used to be near the top and has quietly slid off it — and that person is usually the one worth a message.

4. Revenue

If you charge, you get the money numbers: what came in, what recurs, what cancelled. Straightforward, and the most honest scoreboard you have.

The blind spot is anything sold outside the Skool checkout. Coaching booked by DM, an upsell paid on another platform, a live event — none of that shows up. If a meaningful share of your income lands elsewhere, treat the in-platform revenue figure as one line item rather than the whole picture.

What are Skool's analytics actually good at?

Skool's analytics are good at reporting — telling you the state of the community — and genuinely fine at it.

• Is the community growing? Joins over time answers that.
• Is the money working? Revenue and cancellations answer that.
• Is the room warm this week? Recent posts and comments answer that.
• Who is carrying the conversation? The leaderboard answers that.

Skool's design philosophy is deliberately minimal — it strips out the dashboard sprawl that makes other platforms exhausting to administer. That is a defensible choice and a lot of owners prefer it. You are not fighting a bad product when you hit the limits described below. You are hitting the edge of what a reporting surface is built to do.

Why don't these numbers tell me what to actually do?

Reading numbers stops working at the boundary between reporting and deciding, because reporting tells you the state of things and not what to do about it.

A member count is a fact. "Message Jordan today, because he commented every week for two months and then stopped fourteen days ago" is a decision. Getting from the first to the second is the work.

Making that jump requires joining several things together: how long someone has been a member, what they did recently, how that compares to their own previous behaviour, and often what they do outside your community entirely. No summary chart contains those joins. So owners do it by hand — scrolling the members list, opening profiles one at a time, holding a mental shortlist that decays by Thursday.

That manual reconstruction is where the hours go. It is also the first thing to break as you grow. It works at 80 members. It is unpleasant at 300. It is impossible at 1,500.

What can't I learn from inside my own community?

The one thing you cannot learn from inside your own community is what your members do everywhere else on Skool, because no single-community view can produce it however good it is.

Skool is a network. Your members are almost certainly in other rooms — free, paid, in your niche and nowhere near it. A member who looks dead to you may be posting daily somewhere else. Your own admin area cannot know that, because it only knows about your community.

Two consequences, both practical:

• You misread silence. Someone quiet with you but prolific elsewhere is not a disengaged person. They are an engaged person who has not built the habit in your room. Completely different problem, completely different fix. More on this in what your members are doing on Skool.
• You cannot see where attention goes. If a chunk of your members all spend time in the same handful of external rooms, that is a map of what your audience actually cares about — and a shortlist of places where showing up would reach real people. See where else your members are active.

How do I get more out of the numbers I already have?

You get more out of the numbers you already have by changing the questions you ask of them, before adding any tool at all.

Every one of those turns a headline number into something you can act on. The second column is harder to compute by hand, which is exactly why it gets skipped — but it is where the decisions live. Which Skool metrics actually matter goes deeper on choosing the short list.

Where does Skoolgrades fit into this?

Skoolgrades fits in the gap between reporting and deciding, and it reads your community through a Chrome extension running on your own logged-in Skool session. No Skool API, no scraping infrastructure — to Skool it looks like you browsing your own community, because that is what it is. It collects eleven streams: the roster, posts, comments, notifications, your DM channel list, leaderboards, member profile detail, and the piece you cannot get from inside a single room, where your members are active elsewhere on Skool.

It then turns that into two things. Reports, which cover the state questions — participation rate on the comments-plus-polls definition above, retention lanes, joins, timing, top posts, and a peer benchmark computed on posts that have had 72 hours to mature so it does not swing with fresh content. And Next Moves, a ranked stack of cards where each card is one concrete action with the reasoning attached and the artifact already written: message this member, here is the draft; post this idea, here is the post.

Those drafts are sendable. You build a target list — pick a recommended group, describe who you want in plain language, or paste a post URL to pull everyone who engaged — and Skoolgrades writes a message for each person, verbatim to everyone or personalised per member. You approve every draft, then send from the extension panel one click at a time. It never auto-sends, which is deliberate: human-approved sending is what protects your account and keeps your members' inboxes worth opening.

Two limits worth stating. Skoolgrades does not capture per-post likes, so participation is comments plus poll votes. And on communities above roughly 3,000 active members it works from a fixed sample rather than a full census, so those figures are estimates and we say so.

Skoolgrades is not affiliated with, endorsed by, or partnered with Skool. Check your own admin area for what Skool ships today.