Leaderboards on a refresh schedule, and gamification webhooks
Leaderboards refresh on an interval you set, one list decides who views and ranks, and XP, coin, tier and level changes reach your systems in scheduled batches.
01 ·Leaderboards refresh on an interval you set
Each leaderboard takes a Refresh interval in whole minutes or hours, from 30 minutes up. It is 60 minutes by default, including on every existing leaderboard. The next refresh falls due one interval after the last one finishes, so a refresh that waits for calculation capacity moves the schedule along without queuing catch-up runs. One refresh covers every ranking period the leaderboard has switched on: all-time and the current day, week, month and year.
Traders keep the refresh button on the leaderboard, and it becomes available 30 minutes after the last refresh. It shows whether rankings are queued, updating or waiting to retry, and the previous rankings stay on screen until the new ones are ready.
The interval sets how closely a board keeps up with the activity it ranks. A short daily contest can refresh every half hour while a long-running board refreshes less often, each on its own setting.
02 ·One access list decides who views and who ranks
Leaderboard settings replace the separate Roles / Users and Viewing Permissions sections with one Leaderboard Access list, laid out like the store's product access. Each entry pairs an audience (roles, tags, users or a role combination) with one of three levels: Cannot View, View Only, or View and Appear in Rankings. You can edit an entry, switch it off without losing its settings, or delete it. New leaderboards start with everyone able to view and rank, and existing leaderboards carried their current access across, so nobody has to set them up again.
View Only lets a group follow a competition without entering it, such as staff accounts or a tier the contest is not for. Viewing and ranking sit in one list, so an admin sees both settings for an audience together.
03 ·XP, coin, tier and level changes, sent in batches
Custom Webhooks gain a Gamification type. It watches the changes you choose from Total XP, Total Coins, Tier and Level, and sends them in batched POST requests on a fixed UTC schedule: every hour, every two hours, daily, weekly or monthly. Each client with a selected change in that window gets one entry, with the community ID, the client's user ID and the time of their latest change. XP and coins carry the net change and the current total, and tier and level carry the current value. A test send uses synthetic clients and values.
A broker whose CRM or engagement platform builds segments and campaigns can keep loyalty balances and tiers in step there without polling for them. One scheduled request can carry up to 1,000 clients' changes.
04 ·Display settings for the Streaks widget
The Streaks widget gets display settings modelled on the Milestones widget. Streaks show in a Horizontal, Vertical or Tile view, with up to six per row in Tile. Under Sections Display you pick a streak and choose which of its details, progress, actions and activity appear, and whether its action conditions show in full, in a dropdown or as tabs. Anything a streak's own settings turn off stays off in the widget.
The same streaks can sit in a narrow sidebar or on a full page. Setting the widget per placement keeps a small card to the count and the next action, and gives the activity history room where there is space for it.
Milestone conditions list rolling fields in their own Rolling Fields group, after Custom Fields, and each group in the field picker opens and closes on its own.
14 SepEvery Milestone widget opens in the redesigned editor, and saving clears the unsaved-changes notice.
14 SepYou can retry a failed test delivery on a custom webhook, as you already could a live one.
14 SepLooking up a client by a custom identifier through the user info API counts only current, active clients, so it no longer returns a false duplicate-identifier response.
14 SepSelecting Verify on the Socials page keeps the trader on the platform they were viewing.
14 Sep