Widget sign-ins counted per widget and per community
Widget sign-ins are measured against a per-widget limit and a separate community-wide ceiling, and loyalty tiers can now start at 0.
01 ·Two counters behind a widget sign-in
Widget sign-in carries its own limits, held separately from the API rate limit a community sets for its integration traffic. A page can legitimately run several Returning.AI widgets for the same trader, and each one signs in on its own, because that sign-in is what resolves the widget's own configuration and issues its own refresh cycle. The platform now measures those sign-ins against two counters. The first covers one widget in one community for one identity, and carries the per-identity threshold a broker already has configured. The second is a community-wide ceiling across everything that identity signs into. It sits higher, it is configurable in its own right, and it holds against an identifier working through widget after widget. Each community keeps its own counters, so the same identifier in two communities counts separately in each, against each community's own threshold. Domain limits follow the same scoping.
A broker's portal page often runs a rewards summary, a store and a referral panel side by side, and one trader opening that page is three sign-ins. Sizing the limit to how a portal is laid out puts the threshold where real traffic sits, and the community-wide ceiling still holds the line above it.
Loyalty tiers can start at 0 as well as at 1.
1 AugA milestone countdown modal lists only the rewards that stage awards, and drops the reward block entirely when a stage awards neither XP nor coins.
1 AugMilestone groups and stages with a running countdown switch to a compact countdown at 768px of screen width and below, and back to the full format above it.
1 AugBulk milestone reevaluation reads a member's tracked values through a more selective query, so the work stays proportional to one member's history as a community grows.
1 Aug