Community metrics fall into three groups: engagement and content (are people participating?), community health (is it growing and keeping members?), and business impact (is it moving support costs, retention, or pipeline?). Community managers who keep their budgets track a few from each group and report them monthly on one page that ties activity to outcomes.
This guide covers what to measure in each group, how to calculate the trickier ones, and a monthly community management report template you can copy. If you're still deciding what kind of community you're running, start with the types of online communities, because a support community and a membership community should not be judged on the same numbers.
These tell you whether members are participating and which content earns it. Track them weekly for operations and roll them up monthly.
A simple content score helps here. Rate standout posts from 1 to 5 on a few criteria that matter to your community, such as usefulness, originality, and how long it'll stay relevant, then look for patterns in what scores high.
Health metrics show whether the community is growing, holding on to people, and turning newcomers into regulars.
Track new members per month and where they came from (product, website, email, events), plus churn: members who stop showing up. Define churn for your context, such as no activity for 90 days, and stick to it so the trend means something.
Stickiness compares daily to monthly activity: average daily active members divided by monthly active members. A higher ratio means people come back more often. There's no universal target, because a B2B community people visit when they need an answer will naturally run lower than a social app, so judge it against your own trend.
N-day retention is the share of members who come back a set number of days after a starting event, such as joining, posting for the first time, or getting their first answer. Compare starting events to find the one that predicts members sticking around, then steer new members toward it.
Most members will only ever read. Jakob Nielsen's 90-9-1 rule describes the typical pattern: in most online communities about 90% of users lurk, 9% contribute a little, and 1% account for almost all the activity (Nielsen Norman Group). So track the share of new members who make a first contribution, and how many move through stages you define, for example from newcomer to contributor to trusted member to advocate.
For communities that collect feedback, track the balance of positive and negative sentiment over time, and the topics driving each. Sudden shifts are often the earliest sign of a product or support problem.
This is the group that keeps a community funded. Pick the ones that match why the company invested in the community in the first place.
Member accounts tend to be healthier to begin with, so present member versus non-member comparisons as directional rather than proof of cause. For the full playbook on proving value, see our guide to community KPIs and ROI.
A good community report fits on one page and answers one question for leadership: is this working, and what do you need? Here's a structure that does that.
Keep the same metrics and definitions month to month so the trend lines mean something. Glance at the operational numbers weekly, send this report monthly, and save the deeper retention and revenue analysis for a quarterly business review.
Community ROI is the value the community creates minus what it costs, divided by what it costs. On the value side, add up the support cost saved through deflection, the revenue retained from better renewal rates among member accounts, and pipeline the community sourced or influenced. On the cost side, count the platform, the people running the community, content, and events. Show the assumptions next to the number, and use a conservative range rather than a single figure. Leadership trusts an honest range more than a precise-looking guess.
Most teams pull from four places: the community platform's own analytics for engagement and health, web analytics such as Google Analytics for traffic and search landings, product analytics such as Amplitude for how members use the product, and the CRM, such as HubSpot or Salesforce, for the business impact numbers. The CRM is the one teams skip, and it's the one that makes the member versus non-member comparison possible.
Full disclosure, Bettermode is our product, so weigh this accordingly. Bettermode's built-in analytics cover engagement and health, it connects to Google Analytics and Amplitude, and native HubSpot and Salesforce integrations put community activity on the contact and company records, so the business impact section of your report comes from data you already trust. Starter is $149/month billed annually for up to 10,000 members, with a 14-day free trial. For the bigger picture on why this matters, see how community-led growth ties community to revenue.
Track a few metrics from each of three groups: engagement and content (active members, contributors, answer rate, time to first response), community health (growth, churn, stickiness, retention, new contributor rate), and business impact (tickets deflected, retention and revenue for member accounts, community-sourced leads). Pick the impact metrics that match why the company invested in the community.
A one-page monthly report works best: a one-sentence headline, a KPI table with this month, last month, target, and notes, two or three bullets on what moved and why, the business impact numbers with their method, member highlights, and next month's priorities and asks.
Count active members using a stable definition of meaningful actions, such as posting, replying, reacting, or voting. Then track contributors as a share of active members, answer rate, time to first response, and stickiness, which is average daily active members divided by monthly active members.
There's no universal benchmark. A B2B community that people visit when they need an answer will run lower than a social app people open every day. Track your own ratio over time and look for steady improvement rather than comparing against other kinds of communities.
Subtract the cost of running the community (platform, people, content, events) from the value it creates (support cost saved, revenue retained, pipeline sourced or influenced), then divide by the cost. Show your assumptions and give a conservative range rather than a single number.
Check operational metrics like new posts, answer rate, and response time weekly. Send a one-page report monthly. Review retention, revenue impact, and ROI quarterly, when the numbers are large enough to be meaningful.