Analytics Guide

Discord Bot Analytics: KPIs, Metrics, and Growth Tracking

Rank.top Team
August 2025

Turning a good bot into a great product starts with measuring what matters. This guide covers the essential KPIs for Discord bots - acquisition, activation, engagement, retention, reliability, and monetization - and how to track them in practice. We also show where Rank.top helps with built-in analytics and growth tools.

The KPI Landscape

Active Users

DAU/WAU/MAU; unique users running any command or interacting with components.

Activation

Percent of new servers/users that trigger their first valuable action within 24–72h.

Engagement

Commands per active user, feature adoption, message → command ratios.

Retention

7‑day and 30‑day retained cohorts; server churn; vote return rates.

Reliability

Latency percentiles, error rates, rate‑limited events, uptime.

Conversion

Free → paid, vote participation, checkout success, campaign ROAS.

Acquisition & Activation

Track where new servers come from (directory listings, invites, referrals) and whether they hit the first "aha" moment. Useful metrics:

  • New servers per day/week, invite source distribution.
  • Daily active users (DAU) and weekly active users (WAU).

Engagement

Command Usage

Top commands by frequency and by server segments; long‑tail features to prune or improve.

Feature Adoption

What percent of active servers have enabled key features, slash commands, or web dashboard flows.

Retention & Churn

  • 7‑day and 30‑day retention by cohort; returning voters.
  • Server churn = (servers_removed / servers_previous_period).
  • Re‑activation rate after new releases or campaigns.

Reliability

Track these guardrails

  • P95/P99 command latency; error and timeout rates.
  • Rate‑limit events and Gateway send rate per shard.
  • Uptime and missed heartbeat ACKs. See our rate limits guide.

Monetization Funnel

Core metrics

  • Free → paid conversion by source (command, dashboard, campaign).
  • Checkout success rate; refund rate; LTV by server size.
  • Vote participation and revenue sharing. See monetization guide.

Attribution

Track conversion paths: command → paywall → checkout → success. Attribute by UTM or referrer when possible.

Instrumenting with Rank.top

What you can track

  • Votes and daily patterns via GET /api/bots/{botId}/votes (owner‑only)
  • Messages/commands, server count, ping, memory via GET /api/bots/{botId}/stats
  • Post real‑time stats via POST /api/bots/{botId}/post (every ~30m)

Quick Node.js example

// Submit bot statistics every 30 minutes
async function submitBotStats(botId, stats) {
const res = await fetch(`https://rank.top/api/bots/${botId}/post`, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': `Bearer ${process.env.RANK_TOP_API_KEY}`
},
body: JSON.stringify({
authorization: process.env.RANK_TOP_AUTH_TOKEN,
serverCount: stats.serverCount,
userCount: stats.userCount,
ping: stats.ping,
memory: stats.memory
})
});
return res.ok;
}

Where to view analytics

See your bot page → Stats tab for messages, commands, servers, and ping. Votes are available to owners via the votes endpoint.

Dashboards & Visualization

Cohort & Trends

Cohort retention, command trends, and feature adoption give stronger signals than raw totals.

Alerting

Alert on latency spikes, error rates, or sharp drops in activation so you can respond quickly.

Common Pitfalls

Measuring everything but not acting. Choose a few KPIs per goal and iterate.

Ignoring rate limits and reliability. Bad UX tanks engagement; fix guardrails first.

Run small growth experiments: onboarding prompts, clearer help, in‑bot CTAs, and track outcomes.

Grow with Analytics

List your bot for modern discovery, tap into vote analytics and passive revenue, and track performance in one place.