A Master Widget, Spin the Wheel webhooks and reward events in Salesforce
One widget can switch between up to 12 others, wheel activity goes out by webhook, reward events export to Salesforce, and four more logs open to the API.
01 ·One Master Widget in front of up to 12 others
A new Master Widget puts existing widgets behind one row of tabs or options, and each one opens its linked widget in the same space. An admin picks up to 12 widgets from types such as Milestones, Streaks, Mini Games, Leaderboard, Referral, Store and Earning Overview. A Master Widget cannot hold another Master Widget.
An admin can reorder each item, switch it off, give it a title of up to 40 characters and an optional icon, and align the row left, centre or right. Clients land on the first enabled item. The linked widgets keep their own settings, and if one is deleted later the rest keep working.
A broker can give the whole program one place in its client portal, so clients reach milestones, the store and the leaderboard from a single embed.
02 ·Every Spin the Wheel action, sent to your own systems
A Spin the Wheel type in Custom Webhooks sends seven wheel actions to a CRM, marketing platform or automation tool: spin used, spin earned, spin expired, prize won, prize claimed, streak earned and streak broken. An admin chooses the actions and the wheels, inactive ones included. Each event carries the wheel, spin result, prize, reward, streak and multiplier as recorded.
Events go out one request each, or in batches on a schedule from hourly to monthly, in UTC. A batch keeps every event separate, in time order, up to 1,000 a batch. A failed delivery never undoes a spin, prize or reward.
A broker's CRM can act on a prize won or a broken streak, for example with a message about the client's next spin.
03 ·Reward events, written into Salesforce
With Salesforce connected, an admin can switch on a reward event export in the integration's new Reward Event Settings and choose the event types: XP changes, coin changes, level changes, tier changes and redemptions. Each event becomes its own record in a custom object the broker sets up in its Salesforce org, so Salesforce holds the history of every change, and a replayed event updates its existing record.
Before the export can start, the platform checks the connection, the object and its fields, and lists anything not ready. Records go in batches of up to 200, only failed rows retry, and events wait out Salesforce API limits. Each record carries identifiers, the XP or coin change, level and tier changes and redemption status, and no email, phone or trading data.
A broker's CRM and sales teams can report on loyalty activity inside Salesforce, next to the client data they already work from.
04 ·Four more community logs over the API
The community logs API, opened on 30 Sep with four logs, also returns the Raffles Log, the Streak Log, the Referral Log and the Audit Log, as JSON pages or a CSV file on the same terms. The Raffles Log can be narrowed to one raffle, and its CSV lists every ticket code. The Audit Log adds filters for category, actor and IP address. The Referral Log CSV shows the referrer and the referred client side by side, with each one's identifier when the community has one set.
A data team already pulling loyalty activity into its own reporting can add raffle entries, streaks, referrals and admin changes through the same API key.
Gamification custom webhooks can send with POST, PUT, PATCH or DELETE, and the chosen method applies to Send Test, live delivery and retries.
13 OctCurrency Overview is now Earning Overview across the admin panel, and its activity list gives raffle ticket purchases and Match Prediction entries, refunds and payouts their own readable rows.
13 OctA Leaderboard widget with its description switched off hides the empty details card.
13 Oct