Back to Guides Hub

Discord activity tracker

Track Discord activity trends with Activity Health Score.

A privacy-first 0-100 community health score. AHS explains what moved the needle, to help staff review participation patterns and quiet weeks. It reflects observed activity, not a complete member census or message quality.

Invite CLNR Try it now (5m)
Score Previews
CLNR Bot
CLNR ✓ APP 10:54
Activity Health Score

⭐ 74 (Fair) - - 0

📌 74 is Fair. There is useful activity, with room to improve consistency or reach.

🌱 Fresh channels: 41% active in the last 72h

♻️ Recoveries: 8/8 channels became active again

📡 Coverage OK: CLNR can observe most text and voice channels (≥70%).

Data window

2026-10-01 to 2026-10-07

Last calculated: 2026-10-08 10:00 UTC

Pillars (0-100)

  • Breadth: 84%
  • Intensity: 100%
  • Momentum: 5%
  • Mix: 92%
  • Continuity: 100%
  • Decay hygiene: 68%

Activity snapshot

Active members: 23/44 managed members

Scored events (7d): 1152

Privacy & storage

Counts & timestamps only. No content stored.

Shareable web page

Open the live score

Share the signal

Your Activity Health Score makes community activity easier to understand. A vote helps more admins find a privacy-first way to manage activity.

🔒 CLNR ethics statement: Ethics #09 - I apply rules through visible server settings. If staff configure exemptions or slower decay for some roles, those exceptions should be explicit - never hidden.

Example score from 2026-10-08, not live data.

Related Commands

Use the latest aggregate score, optional publishing, and member-tracking coverage together before making decisions.

View Latest Score
/score

Displays current 0-100 score, pillar breakdown, and active data window in staff view.

Publish Signal
/score_publish

Authorized admins can publish the latest card to a selected, configured, or current channel, once per UTC day. Public web sharing is optional.

Assess Tracking
/coverage

Shows tracked members versus the estimated server total. AHS channel coverage is a separate indicator on the score card.

Discord servers rarely “die” overnight

They drift: conversations concentrate into a few channels, regulars stop showing up on weekdays, and one quiet week turns into a month of churn , often before staff can clearly see what’s happening.

Activity Health Score (AHS) is CLNR’s privacy-first way to make that drift visible early. AHS gives your team a Discord activity tracker, a single 0-100 community health score, and a clear explanation of what changed.

What AHS is

AHS is a server-wide community health KPI computed from the last 7 days of observable activity signals. The result is a 0–100 score that is updated once per day (scheduled around 00:15 UTC).

Use the score for week-over-week comparison within your own server. Community Pulse turns the aggregate context into a visual scene; member transparency explains individual status separately.

What AHS is not

  • Not a moderation trigger: AHS does not kick, warn, or change roles by itself.
  • Not content analysis: we don’t judge sentiment, topics, or message content.
  • Not a vanity metric: it is built to resist spam and low-effort inflation.
  • Not surveillance analytics: we do not store message text or read private DMs.

Decay Score vs Activity Health Score

CLNR uses two distinct metric systems for two clear management roles:

  • Decay Score is member-level. It measures individual inactivity to manage warnings, inactive roles, and manual review thresholds.
  • Activity Health Score is server-level. It aggregates observed activity signals across the last 7 days to give staff community-wide trend context.

AHS does not warn, kick, or change roles by itself. If you want to configure member-level inactivity enforcement, read our guide on how to clean inactive Discord members fairly.

Discord Decay Score Guide Fair Member Cleanup Guide

The six pillars behind the score

AHS is a weighted blend of six pillars. Each pillar answers a question staff actually needs to answer , without chasing raw message volume.

1) Breadth

“How many people show up?”
Measures how many tracked members were active in the last 7 days, normalized by server-size cohort. Helps detect if a small core is carrying the server.

2) Intensity

“How much energy per active member?”
Reflects how strongly active members participate, using robust statistics (e.g., median AU per active member) to reduce the influence of outliers.

3) Momentum

“Are we trending up or down?”
Compares the current 7-day window to the previous week. It’s your early-warning system and context for reviewing what changed; it cannot prove what caused the change.

4) Mix

“Is engagement diverse or fragile?”
Measures spread activity across categories (e.g., text, reactions, voice, threads, RSVPs). A healthier mix usually means a more resilient community.

5) Continuity

“Do we show up consistently?”
Tracks how many of the last 7 days had any qualifying activity. Makes “spike-and-silence” patterns visible and nudges towards stability.

6) Decay hygiene

“Are channels fresh?”
Incorporates freshness and dormancy patterns. Connects “community health” to maintainability: active communities feel maintained.

How AHS helps

Use the score to choose a practical next step and review it over time.

Catch dips early. Most inactivity drama starts with a gradual decline. Momentum and continuity reveal drift while you can still fix it with small actions.
Measure interventions safely. Use AHS to compare patterns after events, onboarding changes, or channel cleanup. A change in score alone does not establish cause and effect.
Turn “vibes” into a repeatable ritual. Instead of debating impressions, AHS gives your staff a shared language: band, trend, and the one pillar that moved.
Connect AHS to Premium Staff Reviews. Free score cards can show a short review teaser. Premium Staff Reviews retain aggregate review history so admins can compare engagement, coverage, and channel-health context over longer windows.

Fairness: Anti-gaming by design

A metric that can be gamed becomes meaningless. AHS is designed to reward healthy patterns (more unique people participating, consistency, diversity) instead of raw spam.

Deduping & Debouncing Debounces repeated events to reduce the contribution of rapid bursts without reading message content.
Per-member daily caps Limits how much one member's activity contributes; it does not make the score impossible to influence.
Voice session validation Requires qualifying session lengths and caps counted minutes to reduce voice-farming effects; it does not assess conversation quality.
Robust median statistics Intensity uses median activity per active member to reduce the influence of outliers.

These guards reduce the effect of repetition and outliers. Staff should still interpret changes alongside coverage and real community context.

Coverage Assessment

AHS reflects only activity in channels CLNR can observe.

  • If CLNR lacks View Channel, activity in that space is excluded.
  • For voice channels, AHS channel coverage checks Connect permissions as well as View Channel.
  • The AHS card labels channel coverage OK, Partial, Low, or Error. Run /coverage for the separate managed-member estimate; Bulk Upload can seed known current members.

Fail-Closed Guardrails

Check score availability and publication separately:

  • Too little data: fewer than 15 active managed members or 200 scored events in the last seven days.
  • Publishing is blocked when observed channel coverage is below 10%.
  • Publishing also requires valid setup, current admin access, and the necessary channel permissions.

Review the displayed reason before drawing conclusions from a missing score.

Example ways to interpret the pillars

🎮

Gaming / MMO Guilds

“We’re not dead, we’re concentrated.”

Symptom: Chat is busy, but raid signups drop.

AHS: Intensity is high, but Breadth declines.

Fix: Add a lightweight LFG ritual to draw in quiet members.

🎭

Roleplay Communities

“The RP is fine; structure is decaying.”

Symptom: Great main thread, confusing channel clutter.

AHS: Mix narrows, Decay hygiene scores drop.

Fix: Archive completed RP channels to clean up entry paths.

🎥

Creators & Streams

“Spikes hide weekday silence.”

Symptom: High activity post-stream, dead on weekdays.

AHS: Continuity drops despite high Intensity spikes.

Fix: Schedule a midweek prompt or poll to build daily cadence.

🎓

Education & Cohorts

“Top students are carrying the class.”

Symptom: Energetic discussions, but low participation rate.

AHS: Low Breadth score relative to total enrolled members.

Fix: Run weekly check-in threads and study groups.

💼

SaaS & Product Hubs

“Support is fine; community shrinking.”

Symptom: Support tickets resolved, general chat dead.

AHS: Mix score collapses to single-mode usage.

Fix: Consolidate unused channels and initiate product discussions.

🛡️

Privacy-Sensitive Groups

“Measure health without exposing anyone.”

Symptom: High privacy expectations, no telemetry allowed.

AHS: Operates strictly on aggregate counts & timestamps.

Fix: Keep AHS private to staff channels without public web export.

Explore matching community workflows in Use Cases

Try it now (5 minutes)

  1. Run /score to inspect your current AHS and key pillar drivers.
  2. If score is missing, review the guardrail indicator (data depth, coverage, setup).
  3. Use /score_settings to pick your target publish channel and sharing rules.
  4. Publish an initial baseline card using /score_publish.
  5. To view or share the web version, grab the destination link with /score_link.
  6. Establish transparent server guidelines with the Inactivity Policy Template.
  7. Inspect a live published page example: AHS Live Example.

Weekly staff habit loop (10 minutes)

  1. Check the overall health band (Poor / Fair / Good / Excellent).
  2. Examine Momentum (week-over-week trend direction).
  3. Identify one lowest-scoring pillar to focus on.
  4. Execute one small targeted action aligned to that pillar.
  5. Re-check progress next week.

💡 Pro-tip: Prioritize improving Breadth (participation reach) before chasing high Intensity.

Frequently Asked Questions

“Our server has lurkers, so will AHS always be low?”

Lurkers are normal. AHS is not trying to force everyone to talk. It helps you track whether participation is widening and whether the server stays alive across the week. Breadth and continuity are often more useful than raw message volume.

“Is Activity Health Score an activity rank bot?”

No. AHS is a staff-first Discord activity tracker, not a member ranking system. It helps staff compare server health week over week with safeguards that reduce the effect of repeated events and outliers.

“Do we have to publish a public scoreboard?”

No. AHS is staff-first. Publishing is optional, and public sharing can be enabled or disabled. Once a public page exists, daily score updates refresh it without reposting the Discord message or resetting the manual publish cooldown.

“When is there no score displayed?”

A score is withheld when the last seven days have fewer than 15 active managed members or 200 scored events. Publication is separately blocked below 10% channel coverage or when setup and permission checks fail. Review the reason shown before acting.

AHS is about a calm routine: check the trend, pick one lever, re-check next week.

Invite CLNR Join Support Community