Campaigns

Use /referraltrack campaign inspect <id> for current referral counts and durable event counts. All campaign administration commands require referraltrack.admin.

After the configured end date, /referraltrack campaign archive <id> saves an immutable snapshot of the counters and the entire validated inviter leaderboard. /referraltrack campaign archived <id> shows that snapshot (up to 100 leaderboard entries), even after the definition is removed from config. Repeating archive preserves the original snapshot. Use a new campaign ID for each season. Pending referrals may validate later; the archive is explicitly a snapshot at its recorded UTC time. Wait for outstanding validations before archiving if you want them included in the final results.

Event collection begins when this version is installed; earlier events cannot be reconstructed. Current referral counts and event counts therefore need not match. Overwriting an attribution does not invent a second successful claim. Deleting a referral does not erase its historical events.

• Impressions: successful displays of /referral top <campaign-id>, once per player per UTC day.
• Claims: successful initial campaign claims, recorded in the same transaction as the referral.
• Validations: claims accepted immediately or later passing their validation gate, once per claim.
• Rejections: campaign claim outcomes rejected as inactive, ineligible, invalid or already claimed; once per player, campaign, outcome and UTC day. Unknown campaign codes and command-level cooldown or claim-window refusals are not campaign rejection events.
• Rewards queued: the referral reward marker, once per claim. This measures reward admission, not confirmed delivery by Vault or external commands. Milestone rewards are not included.

Observation keys contain player UUIDs and UTC day numbers, never IP addresses or Discord credentials. Archives and historical events are retained. No automatic archival or deletion is performed.