Invite Logger
Invite Tracker helps staff understand how members find the server. Strom tracks invite usage, reports inviter statistics from stored activity, and helps detect suspicious or low-quality invite activity.
Features
- Track which invite code a member used.
- Show tracked invite counts for members.
- Track joins and leaves from Strom’s stored invite activity.
- Review stats by invite code.
- Rank top inviters with a tracked leaderboard.
- Reset tracked invite stats for one inviter or the whole guild.
- Use invite data for campaigns, partnerships, and staff review.
Requirements
Strom needs:
- Manage Server or access to invite data where Discord requires it.
- View Channels and Send Messages for command responses.
- Embed Links for rich stat cards.
Invite tracking works best when Strom is present before the invite is used. If the bot joins later, it may not know older invite state.
Commands
| Command | Description | Access |
|---|---|---|
/invite stats [month] [year] | Show your own tracked invite totals for the selected period. | Everyone |
/invite code <code> [month] [year] | Show tracked stats for a specific invite code. | Staff |
/invites stats [user] | View tracked invite statistics for yourself or another member. | Staff |
/invites inviter <user> | See who invited a member when attribution is available. | Staff |
/invites leaderboard [limit] | Show the top tracked inviters in the server. | Staff |
/invites reset <target> [user] | Reset tracked invite stats for the guild or one inviter. | Guild Owner |
/invite stats is self-service for everyone. Staff access for the other invite commands uses Discord permissions. reset is runtime-restricted to the guild owner.
How invite tracking works
Discord does not directly tell bots which invite was used for every join. Strom compares invite usage counts before and after a member joins. This works well when the bot has current invite data, but there are edge cases:
- Vanity URLs may not expose the same detail as normal invite codes.
- Multiple joins at the same time can make attribution harder.
- Deleted invite codes may limit historical context.
- Members leaving and rejoining can affect quality metrics.
Tracked member totals come from Strom’s stored invite activity, not from Discord lifetime invite-code uses. If a code existed before Strom started tracking, older uses are not counted as tracked member invites.
Best practices
- Invite Strom before launching invite campaigns.
- Avoid deleting active campaign invite links.
- Use separate invite codes for different campaigns or partners.
- Review invite stats together with moderation and member activity.
- Do not use invite counts as the only measure of community quality.
Troubleshooting
An invite was not attributed
Strom may not have had a fresh invite snapshot, multiple joins may have happened at once, or the join used a vanity URL.
Invite stats look delayed
Wait a short time and run the command again. If the issue persists, check whether Strom still has access to view invite data.
Invite totals look lower than Discord invite uses
That is expected when an invite code existed before Strom started tracking or when stats were reset. Member totals show only tracked database activity, not Discord lifetime invite-code uses.