Referral system
Reward History
Open Journal -> Referral system and select a project. The history contains changes to achievement and invitation rewards, referral accruals and clan rewards. The newest entries appear first.
A single grant can have several entries, such as awaiting items, review and completion. These are stages of one operation, not three received rewards.
Filters
| Field | How to use it |
|---|---|
| Project | Select the project whose history you need. |
| Server | Limit the history to one server or include all project servers. |
| Reward type | Select achievement rewards, invitation rewards, accruals or clan rewards. |
| Period | Choose a preset, the current or previous year, or custom dates. |
| Start and end dates | Both dates are inclusive. The period uses UTC; there is no limit on the number of years. |
| Status | Include only changes with the selected status. |
| Player | Enter the master account ID or full email. Matches include the inviter, invited player or recipient. |
| Reward ID | Enter the reward definition ID, not the ID of an individual grant operation. |
| Rows per page | Choose 25, 50 or 100 entries. |
Apply filters with Refresh. Reset filters restores the initial period and other values. A player not found in this project produces a message; the search does not silently switch to all players.
Year and Custom Dates
This year selects January 1 through December 31. Metrics include only changes already recorded. Future dates do not add operations to the history.
For several years, change the start and end dates. Period switches to Custom dates. The page size does not limit totals for the whole range.
Metrics
Metrics cover all matching entries in the selected period, not just the currently displayed page.
| Metric | Meaning |
|---|---|
| Recorded changes | Number of history entries. |
| Distinct operations | Individual grants or accruals, regardless of how many changes they have. |
| Recipients | Distinct players identified as recipients. |
| Completions in period | Operations with a completion recorded in the period. |
| Review requests in period | Operations with a review requirement recorded in the period. |
| Reversals in period | Accruals with a reversal recorded in the period. |
An operation can appear in several metrics: for example, it may require review and later complete. These values are not independent groups and should not be added together. Reviews in the period do not mean that all those operations still await a decision.
Statuses and Details
| Status | Meaning at the time of the entry |
|---|---|
| Pending | The grant or accrual has not completed yet. |
| Completed | The operation completed. |
| Needs review | The operation needs investigation before it can proceed. |
| Reversed | A previously applied accrual was reversed. |
| Skipped | This operation did not issue a clan reward. |
Open Details in a row to see the operation and reward IDs, associated character or clan, and the item contents where recorded. Quantity and enchantment level are shown separately.
For achievement and invitation rewards, Current delivery and reward composition also loads the current delivery state and the contents saved when the grant was created. These may differ from an earlier history entry. Editing a reward definition does not rewrite an existing grant.
Refresh and Navigation
Use Next and Previous to navigate the list. Moving forward keeps the calculation time and totals. If new information arrives for earlier dates, the page asks you to refresh the list instead of mixing pages with different totals. Changing filters, refreshing manually or returning to the first page starts a new calculation. Use Refresh after a long pause as well.
The first page refreshes automatically about every 30 seconds while you are not editing filters or inspecting an expanded entry. Other pages do not refresh automatically. New changes may appear after a short delay; use Refresh to load them again.
Empty Periods and Errors
An empty list means that no entries match the filters. For example, the previous year may be empty even when rewards have already been issued this year.
When data is temporarily unavailable, a retry message replaces the list instead of showing zero metrics.