Track Discord Invites Without Guessing What the Bot Can Know
Invite Tracker estimates who invited a member by comparing Discord invite usage counters with observed joins. It cannot prove which invite a person used or recover historical joins. Use this guide to enable tracking, read saved counts and understand when an inviter must remain unknown.
Start freeStart free. Pro is $9.99/month.
Before you start
- A running bot with Invite Tracker enabled for the server you want to measure.
- Manage Server permission for the bot and the Server Members Intent enabled for its Discord application.
- A server manager to configure tracking; optionally, a designated manager role for /invites status.
Enable tracking for your server
Create an account through the sign-up link, connect your bot to Discord and find Invite Tracker in its Modules area. Open Settings, select your server and switch on invite tracking. Set a manager role if someone without Manage Server should inspect tracking health, then save. Confirm that the bot itself can manage the server and receive member events.
In Discord, use /invites status from an account with Manage Server or the configured manager role. A fresh start needs an invite-counter baseline before it can estimate later joins. The status response distinguishes warming up, available counters, unavailable permissions and storage trouble. Do not interpret an empty leaderboard as proof that nobody shared an invite.
Know how a join gets an estimated inviter
The bot compares invite usage counters before and after a batch of observed joins. It attributes the batch only when one identifiable inviter accounts for the entire matching increase. If multiple invite codes belong to that same inviter, their increases can still support an estimate. The bot does not receive a definitive invite-to-member link from this comparison.
Simultaneous joins become ambiguous when counters rise for different inviters: the bot cannot pair each person with a link. Deleted invites, unexpected new used links, changed counters and missing permissions can also prevent attribution. Such joins may be saved with an unknown inviter instead of assigning credit to a guess.
Read member stats and the leaderboard
Use /invites stats to inspect your own saved invite estimates, or choose the member option to inspect another inviter. The reply shows present members and total tracked members attributed to that person. Use /invites leaderboard for the top ten estimated inviters, ordered by present count and then tracked count. Unknown inviters are excluded from that ranking.
Counts describe saved members, not a lifetime total of invite clicks or every join event. Each member has one latest observed join record. A later observed rejoin replaces that record; an observed departure marks the member absent. Members can request stats and the leaderboard while tracking is enabled; the health/status command is reserved for managers.
Account for history and offline gaps
Enabling the module today does not reconstruct who invited your existing members. Saved member records survive a restart, but the bot resets its in-memory counter baseline after a disconnect. It does not compare counters across that unobserved gap or backfill joins and departures that happened while offline.
A missed departure can therefore leave a present count stale. Check /invites status for unknown joins and tracking health before using the leaderboard to discuss community growth. If tracking is unavailable, restore the bot’s Manage Server permission; if saving fails, resolve the storage issue before treating new counts as reliable observations.
Frequently asked questions
Can this recover the inviter for members who joined last month?
No. There is no historical backfill. An old join only contributes if the bot observed and saved it while tracking was active.
Why is a join unknown even though someone used an invite?
An invite counter alone does not identify the joining member. Conflicting counter changes or gaps in observation leave insufficient evidence for an inviter estimate.
Is the leaderboard an all-time referral ranking?
No. It ranks attributed saved member records, with present and tracked totals. Repeat joins do not accumulate as separate lifetime referrals.
Do counts stay exact when the bot is offline?
No. Stored records remain, but missed member events are not reconciled. Present totals can include members whose departure the bot never saw.