Discord Bot Analytics: KPIs, Metrics, and Growth Tracking

Choose metrics that answer a question

A key performance indicator (KPI) should help you make a decision. If you want to improve onboarding, measure how many new servers finish setup. If commands feel slow, measure response times. Use the categories below to choose a small starting set.

From an install to a useful first action

Acquisition measures how people find and add your bot. Activation measures whether they get it working. Count those separately: an install does not tell you that setup succeeded.

1. 1

   Record the install

   Track when the bot joins a server. Record the referral or campaign source when you can reliably identify it.
2. 2

   Define the first useful action

   For a moderation bot, this might be enabling the first rule. For an events bot, it could be creating an event.
3. 3

   Choose a time window

   For example, count servers that complete that action within 72 hours of installing. Give each server the full window before including it in the result.

Look beyond command totals

A rise in commands can come from a growing audience, one busy server, or repeated failed attempts. Count unique users and servers alongside command volume to see what changed.

• Define active: choose a meaningful action, such as a successful command, and use that definition consistently.
• Choose your unit: count people when studying personal use and servers when studying community adoption.
• Compare similar groups: small servers and large communities may use the same bot very differently.

See whether people come back

A cohort is a group that started in the same period. Follow each group over time instead of comparing this week's total users with last week's: new arrivals can hide a drop in returning users.

Pick one retention definition and label it clearly. The example above counts servers that were active during each week after their first use. A day-7 retention metric would answer a different question.

Put reliability beside usage

If engagement falls, check failures and response times before changing features. A command that times out gives people little reason to try again.

Follow the path to a paid plan

If your bot offers paid features, track the steps between seeing an offer and completing a purchase. A single conversion percentage will not show you where people stop.

• Conversion: divide completed purchases by the relevant starting group, such as users who saw the offer.
• Checkout completion: compare successful payments with checkout starts.
• Refunds and cancellations: track what happens after purchase, alongside revenue.
• Attribution: use campaign tags or known referrers where available; keep unknown sources labeled as unknown.

Keep votes and revenue-sharing earnings separate from paid-plan conversion. They measure different ways people support your bot. The monetization guide covers the broader options.

Track listing activity with Rank.top

Rank.top provides vote data and statistics reported by your bot. For activation, retention, and per-user command usage, collect events in your own application as well.

Send a statistics snapshot

Call this function from your bot process with its current statistics. Supply your account API key and the bot authorization token through environment variables.

async function submitBotStats(botId, stats) {
  const apiKey = process.env.RANK_TOP_API_KEY;
  const token = process.env.RANK_TOP_AUTH_TOKEN;
  if (!apiKey || !token) {
    throw new Error("Missing Rank.top credentials");
  }

  const res = await fetch(
    "https://rank.top/api/bots/" + botId + "/post",
    {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        Authorization: "Bearer " + apiKey,
      },
      body: JSON.stringify({
        authorization: token,
        serverCount: stats.serverCount,
        userCount: stats.userCount,
        ping: stats.ping,
        memory: stats.memory,
      }),
    }
  );

  if (!res.ok) {
    throw new Error("Stats submission failed: " + res.status);
  }
}

Build a dashboard you will use

Put each metric next to a question and a possible action. Include the reporting period, comparison period, and release dates so changes have context.

Common mistakes to avoid