Theme
Analytics and Rewards
Summaries inherit the meaning of their source records
Analytics groups eligible saved results. Rewards apply configured participation or score rules to eligible records. Neither view repairs missing or incorrectly scoped source data by itself.
analyticsSearch tasks, concepts, states, and troubleshooting
I need to...
Add or update a playerLink a game profileRecord event resultsImport a screenshotCorrect imported rowsReview analyticsConfigure reward rulesApply for a Castle PositionReview applicantsBuild and publish a scheduleRead a scoped articleCreate and publish an articleCreate a Reading Verification sessionUse a saved Lab profileOptimize Hero GearConfigure a Bear Trap rallyUnderstand premium accessRestore deleted information
10 highest-relevance guides shown
Analytics and RewardsAnalytics and Rewards Analytics groups eligible saved results. Rewards apply configured participation or score rules to eligible records. Neither view repairs missing or incorrectly scoped source data by itself.Matched in: IntroductionAnalytics Aggregation and Reward DecisionsAnalytics Aggregation and Reward Decisions Decision precedence must remain visible when several reward rules apply. Missing data is not equivalent to a measured zero. Analytics reads current, non-deleted player results whose events are alsoMatched in: IntroductionReward Workspace and Personal RewardsReward Workspace and Personal Rewards The reward workspace is the manager-facing place for reward records and decisions. My Rewards is the player-facing view of outcomes visible to the signed-in identity. Analytics can inform a reward decisMatched in: IntroductionWar Room Analytics OverviewWar Room Analytics Overview War Room Analytics turns saved player, event, participation, and score records into kingdom, alliance, player, and custom views. It does not create missing results or correct an import automatically. The selectedMatched in: IntroductionKingdom AnalyticsKingdom Analytics The Kingdom tab compares eligible alliances and players across the active kingdom. It is intended for kingdom-level review, not for changing an alliance roster or result.Matched in: IntroductionAlliance AnalyticsAlliance Analytics The Alliance tab explains how one alliance is performing across saved event instances and which member records need closer review.Matched in: IntroductionPlayer Cross-Event AnalyticsPlayer Cross-Event Analytics The Player tab collects one warrior's eligible event history across multiple event instances. It is a premium feature and appears as Player (Premium) when locked.Matched in: IntroductionCustom AnalyticsCustom Analytics The Custom tab builds a chart and table from the records already visible in the active scope. It is labeled Custom (Premium) and shows a locked state until Custom Analytics is active.Matched in: IntroductionAnalytics Sharing, Scope, and TroubleshootingAnalytics Sharing, Scope, and Troubleshooting Analytics visibility combines account assignments, the active kingdom or alliance, optional kingdom sharing, and subscription features. These mechanisms can grant a view without granting managemMatched in: IntroductionReward Eligibility and StatusesReward Eligibility and Statuses Reward views evaluate saved event data against the current scoped reward rules. My Rewards shows the linked player's result when available; authorized managers can review broader eligibility lists and configuMatched in: Introduction
Input to decision to output
Analytics and reward flow. Eligibility and filters precede grouping; reward decisions consume qualified records and expose a reason.
Accessible summary: Saved records are checked for eligibility, filtered by scope and time context, grouped according to the selected view, then shown as summaries and possible reward decisions.
Views and scope
Kingdom Analytics aggregates eligible information across the permitted kingdom context. Alliance Analytics stays within one alliance. Player Analytics follows one player across the selected eligible events and boundaries. Custom Analytics applies supported premium grouping and filters; it is not an unrestricted database query. Shared or granted Analytics can expose a read-only view. That grant does not authorize changing results or reward rules.
Date boundaries and event selection determine which occurrences participate. Grouping happens after those filters. Drill-down should reconcile the displayed total with its contributing records; if it does not, check whether a filter, cumulative stage, result kind, or activity interpretation differs. Recalculation uses the current eligible source data and current applicable rule configuration. It cannot recreate records that were never saved.
Reward decisions
Reward rules can consider eligible participation records, score records, configured thresholds, event or stage context, and the precedence described by Analytics Aggregation and Reward Decisions. Missing values do not automatically mean zero unless the relevant rule explicitly treats them that way. When rules conflict, the configured decision order determines the displayed outcome; a manual change remains distinct and should expose its reason or source context.
Worked example: shared but read-only
Starting situation: Sam receives kingdom Analytics through an accepted grant. One alliance total looks too low. Inputs: Selected kingdom, date range, event filter, eligible result records. Rules: The grant permits viewing and drill-down but not editing source results. Branch: Sam finds one missing player result. Output: The dashboard remains read-only and explains the contributing records. Reason: Analytics access and result-management authority are separate. Next action: Sam sends the alliance, event, date, player, filters, and expected source to an authorized manager, who corrects the source batch and triggers normal recalculation.
When a view is empty or surprising
Check, in order: active scope; effective Analytics access; selected view; event and stage; start and end boundaries; whether results were saved or merely reviewed; lock or correction state; player membership interpretation; and whether the view is awaiting recalculation. Do not create duplicate results to make a total appear. Correct the source event, record batch, or reward rule.
Read next: Kingdom, Alliance, Player, Custom, or sharing and troubleshooting.