Invite Tracking

Discord never tells a bot which invite somebody used. Arclo works it out by holding every code's use count and re-reading them on each join to find the one that went up — which is why attribution is a system rather than a field.

The number

One formula, used by the invite card, the leaderboard image, the web table, the /invites command and the reward checks:

total = regular − left − fake + bonus

• Regular counts every credited join, including the ones later marked fake — which is what makes a fake net to exactly zero rather than to minus one.
• Left is arrivals who have since left, and is subtracted only if you ask for it.
• Fake is an arrival that failed your rules — an account younger than your threshold, or a rejoin you chose not to count.
• Bonus is what you add by hand.
• Pending sits outside the sum: an arrival waiting to be validated.

Setting it up

1. 1

   Switch it on

   Essentials → Invite Tracking. Arclo needs Manage Server to read your invite list.

2. 2

   Decide what counts

   Minimum account age for a real invite, whether rejoins count, and whether leavers are subtracted.

3. 3

   Pick a join channel

   Optional — an announcement each time somebody arrives, saying who brought them.

4. 4

   Add rewards

   A role at N invites. Roles reconcile, so somebody whose total drops loses the role again.

#welcome

ArcloBOTToday at 14:32

Welcome @newcomer — invited by @mira, who now has 34 invites.

Per-code roles and labels

Give a specific invite link a label and a role: anybody arriving through it gets that role automatically. This is how partner links, event links and campaign links are separated without asking anybody to pick a role afterwards.

The label and the code are available in your welcome message as {invite_label} and {invite_code}.

In the welcome message

{inviter}, {inviter_name} and {inviter_invites} are resolved before the greeting is sent, so “Welcome @newcomer, invited by @someone” arrives complete rather than being edited a second later. See Welcome & Goodbye.

Cards, boards and the web page

• The invite card and the leaderboard image are designed in the same studio as the level cards.
• The leaderboard has a public web page, and can live as a pinned message Arclo keeps up to date.
• Server Analytics reads the same join records for its growth, retention and join-source views.

Commands

Limitations

• Vanity URLs cannot be attributed to a person — Discord reports the use but not an inviter.
• An invite whose uses ran out between two joins is ambiguous; Arclo handles the common case but perfect attribution is not possible from Discord's API.
• Arclo cannot see invites created before it joined until it has read the list once, which it does on startup.