SnapWeb Rewards integration

SnapWeb integration

In Display → SnapWeb, the optional Gamification page is a flexible composition. Open Configure, enable each section that belongs on that page, and give the selected sections their layout order. There is no automatic “all” choice: selecting every section is an explicit administrator decision. Reward history, Balances, Achievements, Ranks, Achievement catalog, Rank catalog, Quests, and Streaks can also be enabled as independent focused pages, at the same time as the flexible page or instead of it. Every destination owns its route, navigation label, navigation visibility, and order. Shared point-type visibility and fallback rules live under Display → Content & privacy. The Cointacted SnapWeb bridge owns native pages and navigation; Gamification owns their data, privacy, and feature decisions.

Every enabled route loads directly, works with browser back/forward, uses no iframe in the native experience, and loads the member stylesheet only when mounted. SnapWeb also maintains a server-rendered fallback document for direct and unenhanced requests. It follows SnapWeb Auto, Light, and Dark theme attributes and remains responsive. Reward history is chronological and paginated. Other views use labelled tables with explicit empty rows; on narrow screens each row becomes a labelled card. Signed-out visitors receive the configured sign-in message or a hidden surface without making a private member request. The configured empty-state policy is also honored.