Invite Tracking records how members join, who invited them, and how invite counts change when members leave or rejoin. Members can view invite statistics with /invites. Staff can resolve uncertain attribution and reset tracking data.
Invite Tracking belongs to the Settings module. It also supplies inviter variables to welcome and leave messages.
Features
- Track standard Discord invites and vanity URL joins.
- Show real, left, fake, and total invite counts.
- Record the latest known invite source for each member.
- Mark uncertain joins as ambiguous instead of guessing silently.
- Let staff resolve an ambiguity from
/invites user:. - Reset selected inviters or the whole server while keeping settings and the current baseline.
Before You Begin
You need Manage Server to configure or reset tracking. Discortics needs Manage Server to read the server's invite metadata. It also needs Send Messages and Embed Links for the settings and statistics panels.
Invite attribution depends on changes in Discord invite usage. Some joins cannot be identified with certainty, such as several invites changing at nearly the same time. Discortics records those cases as ambiguous or unknown.
Invite tracking, statistics, ambiguity review, and reset controls are available on all tiers.
Enable Invite Tracking
- Give Discortics Manage Server.
- Run
/settings invites. - Select the status button to enable tracking.
- Discortics reads current invite usage and saves it as the baseline.
- Run
/invitesafter members join to review your own statistics.
Enabling can fail when Discord invite data is unavailable, the bot lacks Manage Server, another baseline update is in progress, or the baseline cannot be saved. Correct the reported problem and try again.
Disable Invite Tracking
Run /settings invites and select the status button while tracking is enabled.
Disabling removes the current invite snapshot, so a fresh baseline is created the next time tracking is enabled. Existing member statistics remain until you reset them.
View Invite Statistics
Run:
/invitesto view your own counts./invites user:@memberto view another member.
The response shows:
| Field | Meaning |
|---|---|
| Real | Credited invited members who currently count as legitimate joins |
| Left | Credited invited members who later left |
| Fake | Joins classified as fake by invite rules |
| Total | Historical legitimate invite credits |
| Source | Latest detected invite, vanity URL, unknown, or ambiguous source |
| Inviter | Member credited for the target's latest standard invite source |
Counts are historical. A legitimate rejoin after enough time can create another credit without removing the old inviter's history.
How Fake and Rejoin Counts Work
Discortics classifies an invite as fake when the joining account is younger than seven days.
Rejoins also affect counters:
- Rejoining within 24 hours through the same inviter restores that member from left to real.
- Rejoining within 24 hours through a different inviter counts as fake for the newly detected inviter.
- Rejoining after 24 hours with an old-enough account can create a new legitimate credit for the detected inviter.
Fake counts are separate from total legitimate credits.
Resolve an Ambiguous Join
When Discortics detects several possible invite changes, /invites user:@member shows Pending ambiguity.
Staff with Manage Server see a menu of candidate invite codes:
- Run
/invites user:@memberfor the joined member. - Review each candidate's invite code, inviter ID, and usage change.
- Select the invite that was actually used.
- Discortics recalculates the attribution and refreshes the statistics panel.
Regular members can see that attribution is pending but cannot resolve it.
Reset Invite Data
Open /settings invites, then select Reset. This reset keeps invite tracking settings and the current baseline.
Reset Selected Users
Choose Selected Users, then select 1 to 25 inviters. Discortics clears their counters and affected invitee attribution.
Reset the Entire Guild
Choose Entire Guild, then confirm. Discortics clears invite counters, invitee attribution, and ambiguity records across the server.
Warning: Invite resets cannot be undone. Record any statistics you need before confirming.
The broader /settings reset type:Invites command is a separate statistical reset. Prefer the Invite Tracking panel when you need selected-user controls or explicitly want to retain the current invite baseline.
Welcome and Leave Variables
When tracking identifies a source, welcome and leave embeds can display invite code, source, inviter identity, and inviter counts. Unknown or unavailable values render as empty text.
Configure these in the Welcome, Leave, and Autorole guide. Enable tracking before relying on invite variables in live messages.
Command Reference
| Command | Purpose | Required user permission |
|---|---|---|
/settings invites | Enable, disable, or reset invite tracking | Manage Server |
/invites | View your own invite statistics | None |
/invites user: | View another member and resolve ambiguity when permitted | None to view; Manage Server to resolve |
Frequently Asked Questions
Why is the source Unknown?
Discord did not provide enough invite-usage change data to identify one source. Vanity joins and unavailable invite metadata can also prevent standard inviter attribution.
Why is a join Ambiguous?
More than one invite looked possible during the same join window. A staff member can choose the correct candidate from /invites user:@member.
Does disabling tracking delete statistics?
No. It removes the current invite snapshot and stops new tracking. Use Reset to clear stored counts and attribution.
Why did a rejoin change counts differently from a new join?
Rejoins within 24 hours use special same-inviter and different-inviter rules. Older rejoins can create a new legitimate credit.
Can invite counts be perfectly accurate during a raid?
No invite tracker can always identify concurrent joins perfectly from Discord's invite counters. Discortics records uncertain cases for staff review instead of silently choosing one invite.