Discord Invite Tracking records new joins observed after tracking is enabled and identifies the inviter when the available invite-use counts support a clear match. It is available with Community & Discord or Everything.
Enable Invite Tracking
- Open Discord > Onboarding in the connected workspace. A workspace Owner or Admin can configure this feature.
- Expand Invite Tracking and turn on Enable Invite Tracking.
- Select a Notification channel. Use a text or announcement channel where the bot can send messages.
- Optionally enable Mention joining member. Mentions are off by default.
- Click Save changes inside Invite Tracking. These settings save separately from Save onboarding.
The bot needs Manage Server to read Discord invites. In the notification channel, allow View Channel, Send Messages and Embed Links. Manage Channels allows invite-create/delete events in the relevant channels.
Tracking starts with a snapshot of current invite usage. Existing server members and earlier referrals are not reconstructed. Disabling tracking stops new tracking and retains stored logs.
Review join logs and statistics
Open Discord > Role History and find Invite Tracking Logs below the role timeline. Workspace Owners, Admins, Leads and Managers can review this area.
- Join Logs shows observed members, inviters, invite codes, join times and attribution status. Open a row for account and join details, the attribution reason and notification delivery status.
- Click Filters to search by member, inviter or invite code, choose a join-date range or attribution status, or enter an inviter Discord ID. Collapsing Filters keeps the selected filters active.
- The summary cards and Export filtered CSV follow the log filters. CSV includes all matching stored rows, not just the current page.
- Inviter Statistics shows the top 25 inviters across confirmed tracked joins in the server; log filters do not narrow this view.
Retained-member counts are checked live for inviters with at most 100 confirmed join records. Larger histories or failed Discord checks show Unavailable. A rejoined member counts as retained only when the current join matches the confirmed record. Observed invite links describe links seen by the tracker; they are not credited referrals.
Use Discord commands
Run these commands inside the connected Discord server. Every command response is private.
| Command | Purpose | Who can use it |
|---|---|---|
| /invites me | View your confirmed tracked invitations. | Any server member; no linked CollabOS account required. |
| /invites leaderboard [limit] | View top inviters; limit is 1–25, default 10. | Any server member; no linked CollabOS account required. |
| /invites user user:@member | View a member's invite statistics. | Discord Administrator or linked workspace Owner/Admin. |
| /invites setup channel:#invite-logs [mention_member] | Enable tracking and choose the notification channel; mentions default to off. | Discord Administrator or linked workspace Owner/Admin. |
| /invites disable | Stop new tracking and retain logs. | Discord Administrator or linked workspace Owner/Admin. |
| /invites status | View tracking status, synchronization and permission health. | Discord Administrator or linked workspace Owner/Admin. |
Understand attribution
Invite Tracking compares invite-use counts around observed joins. Discord does not supply a direct member-to-invite mapping, so attribution is best effort.
- Identified means the tracker found a clear supported match. Only confirmed attributed joins count toward inviter statistics and the leaderboard.
- Unknown means there was insufficient reliable invite data to identify an inviter.
- Ambiguous means overlapping joins or competing invite-use changes prevented a unique match.
Gateway interruptions, unavailable invite data, deleted or reset links, vanity-link changes and overlapping joins can prevent attribution. Tracking resumes conservatively after reconnecting; it does not invent missing referrals.
Troubleshooting
If tracking cannot read invites, check Manage Server and the bot's connection. If notifications fail, check the selected channel and its View Channel, Send Messages and Embed Links permissions. Use /invites status for more detail.
A notification failure does not remove its stored join log. Uncertain notification deliveries are not automatically resent. Welcome messages, autoroles and verification remain separate onboarding features.