Voucher prizes, badges in widgets, and custom Store buttons
A Prize Inventory adds voucher prizes to raffles and leaderboards. Badges get embeddable widgets and audiences, and admins can set their own Store buttons.
01 ·A Prize Inventory for raffle and leaderboard prizes
Community Settings has a Prize Inventory, listed after Gamification. An admin sets up a voucher prize once, then attaches it with Add Prize to a raffle community goal or a leaderboard position. Each prize keeps a permanent Prize ID, and an edit changes only the awards earned after it.
- Codes come from a pool the admin uploads (pasted, or a CSV or TXT file), or the platform generates each one when the client confirms the claim, with an optional prefix of up to 12 characters.
- Expiry is set per prize: none, a fixed date, or a timeframe that starts when the code is revealed.
- A prize can point to a Store product with a percentage or fixed discount, or carry no code and serve as a tracked award.
- Archiving shows the admin which raffles and leaderboards use the prize, then stops new awards. Awards already earned stay available.
Vouchers join Credits and Tier Points as a prize a broker can hand to raffle and leaderboard winners. The codes, expiry and Store discount are set in one place, so a single voucher prize can serve several competitions.
02 ·How a voucher award reaches the winner
Each qualifying client gets an award when a raffle result comes in or a leaderboard period finalises. For a prize with uploaded codes, the platform reserves one code per unit. If the pool runs short, the award still goes through, and only the units without a code show Awaiting code, with a message the admin writes. The admin fills those units from the Award log, which covers every prize, or from a single prize's status view.
Clients claim from the My prize tab of the raffle or leaderboard. A code stays hidden until the client confirms the claim. Then it appears with its expiry and a copy action, and Use in store shows for a prize tied to a Store product. Confirming twice returns the same codes and never takes another one from the pool.
When the code pool runs short, the winner still sees the prize at once and can claim the units that have codes. The Award log shows the broker's team which units still need one.
03 ·Badges on a broker's own site or portal
Admins can now embed the badge page in two ways. In Badges settings, the admin switches on the badge widget, sets its appearance, theme, font, size, allowed domains and member identifier (Email is one option), checks the preview and copies the embed code. Badges is also a custom widget type under Community Settings > Widgets, with the same Settings, Style and Setup controls as the other custom widgets.
Either way, the client sees their profile, the All, Earned and Applied tabs and their progress toward each badge. They pick up to three badges to display, and they can apply for a custom badge with a message and an attachment, which then goes through the admin's existing approval flow.
Badges can sit where clients already go, on the client portal or the broker's site. A client can follow their progress toward the next badge, and apply for one, without leaving the page they came for.
04 ·Badges kept to the clients they are for
Each badge has an audience setting with the same choices as milestone stages: roles, individual members, tags, and combinations of roles that a member must hold together. Matching any one of them qualifies a member. A new badge starts with the community's @all roles selected, and a badge with nothing selected is open to nobody. The audience applies to awards, applications, the choice of display badges, profiles and widgets.
A badge meant for one segment of clients, such as a role or a tag, is earned and shown only within that segment, so each group can work toward its own set of badges.
05 ·Store buttons set per category or product
Store categories and products each have a Customize CTA button setting. A product with its own setting on uses its own button. Otherwise it follows its category, and with neither it shows the default Buy now. Each button has an Enabled and a Disabled state, each with its own title, icon and appearance. The Disabled state shows at 30% opacity when the client cannot buy, for example once they reach a purchase limit.
The Enabled state can link to a website. A click still runs the regular purchase, recorded in Order History and Purchase History, and the link opens after the purchase succeeds, in the same tab or a new one. Products also have Hide price on user front, and Discount Price is unavailable on a product priced at 0.
A Store item can send the client on to a website once they have bought it, and purchase limits, balance and permission checks still apply. A category's button sets the wording for a whole section of the Store in one place.
Each Spin the Wheel prize can carry its own segment image, with crop, zoom and Gaussian blur, and the segment colour stays underneath.
2 NovThe API Log's Received at filter returns logs for the chosen dates, in the table and in the CSV export.
2 NovThe Mini Games, Streaks and Leaderboard custom widgets preload the files their first screen needs, and bundle-mode custom widgets save one cache round trip per load.
2 NovThe Store groups live updates before they reach the page, and email notifications look up their recipients with optimised queries.
2 Nov