How to Set Up Discord Invite Tracking? Who Invited How Many Members

Manage Server permission, channel and module

• The bot must have the Manage Server permission. Discord only gives the invite list and invite usage counts to a bot with this permission. If the permission is missing, both the setup response and the dashboard will warn you; upon joins, a "could not detect invite" warning will drop into the notification channel at most once an hour. If you are unsure how to adjust the bot's permissions, check the Discord bot permission errors guide.
• The notification channel must be a text channel. The bot needs view channel, send messages, and embed links permissions there. The command will let you know if any of these permissions are missing as soon as you set the channel.
• The Invite Tracking module must be enabled. The module is managed via the toggle in the Overview section of the dashboard and is enabled by default. If you turn it off from there, tracking will also stop.
• History does not count. Tracking records joins that happen after the moment you select the channel. Members who joined while the bot was offline are not recorded either.

This topic in VeyroBot:Discord Invite Tracker →

How does the bot find out which invite was used?

Discord does not directly notify the bot about which invite a member used to join. VeyroBot keeps the server's invites and the usage count of each in memory; when someone joins, it re-reads the list and looks for the invite whose count has increased. All the errors and setting recommendations below stem from this method, so knowing them beforehand will make your job easier.

Setup from the dashboard

1. Open Dashboard → your server → Invite Tracking tab.
2. If you see a "Manage Server" warning at the top of the page, first give this permission to the bot's role.
3. Select the channel where the cards will go from the Notification Channel list.
4. Leave the Ignore Bot Joins toggle on; cards will not be sent for bots added to the server and nothing will be written to the leaderboard.
5. Click the Save Invite Tracking button.

If no channel is selected, tracking will not work; the moment you save, the bot reads the server's invite list so that even the first join matches correctly.

Setup via command

/setinvitelog channel:#invite-tracking

• You must have the Manage Server permission to use the command.
• When you provide a channel, the command also enables the module and reads the invite list immediately.
• To turn off tracking, run the command without providing a channel.

What do the four cards dropping into the channel mean?

Creating invites suitable for measurement

• Open separate invites instead of using every promo in one place. If you share a single link everywhere, you see who brought them, but you cannot see where they came from. We explained which channel you should promote in in the Discord server promotion guide.
• Do not set usage limits. Single-use invites or invites whose usage limit has been reached drop from Discord's list. The bot cannot see that the count has increased, and the join may appear as "Could not be detected".
• Use permanent invites for long-term promotions. Expired invites also drop from the list and lead to the same result.
• Pay attention to who created the invite. The count is credited to the account that created the invite on Discord. If you create promotional invites from an administrator account, they will all be added to that account's count.

Reading the numbers

Anyone can use the /invites [user] command. If no person is selected, the counts of the person typing the command are displayed.

• Joined — joins that definitively match this person's invite.
• Left — those among these who later left the server.
• Staying on server — joined minus left. The leaderboard is sorted according to this number.
• Invite link usage — the total usage counter of the person's invite links on Discord. Since it includes unmatched joins, it may be greater than the Joined count.

A person who joins with their own invite is not counted on the leaderboard. If a member leaves and returns with a different invite, they are not counted twice; their record passes to the latest inviter.

If the numbers look incomplete or misleading

• Editing the bot role later and removing the permission. Tracking does not stop silently; a warning drops into the notification channel, but joins during that interval are not counted.
• Being surprised by missing numbers during a raid. While the Anti-Raid lock is active, invite matching is intentionally skipped; joins during that time are not counted and no cards are sent. How the lock works is in the Discord anti-raid setup guide.
• Deleting the notification channel. Joins continue to be recorded for the leaderboard, but cards are not sent. Select a new channel from the dashboard and save.
• Using the Joined column as a metric in an invite contest. Accounts that join and immediately leave are also written to Joined. Give out the reward based on the "Staying on server" count and the situation a few days after the contest ends.

How exact are the invite counts?

Suitable for: servers wanting to promote in multiple places and see which one works, communities rewarding their members with an invite contest, managers wanting to measure how many people came from partnered servers.

Not suitable for: situations where every single join must match definitively. In large promotions where a large number of members join simultaneously, some of the matches remain as "Possible Invite". Numbers show a trend; they do not replace individual account verification.

Frequently asked questions

Are my invites from before the setup counted?

Existing invites are read when tracking starts, and their subsequent uses are monitored. Members who joined before the setup are not added to the leaderboard retroactively.

Do counts disappear if I delete an invite link?

No. Joins matched with that link remain in the inviter's count.

Can I reset the leaderboard?

Currently, there is no option to reset the leaderboard via the dashboard or a command. Run contests by noting down the numbers at the beginning and end of the period.

Are second accounts coming with another account's invite filtered out?

No. The bot only excludes the person who joined with their own invite; it does not distinguish whether an account belongs to a real person.

Which language are the cards written in?

In the bot language selected for the server.

The general overview of the feature is on the Discord invite tracking page, its short summary is in the documentation, and command cards are in the /setinvitelog and /invites links.

Last updated: September 17, 2026. The behaviors in this article have been verified with the invite tracking engine in the current version of VeyroBot, the /setinvitelog and /invites commands, and the Invite Tracking tab of the dashboard.