All updates

An embeddable store, a webhook history, and email templates you can build

Embed the rewards store on an outside site where traders spend coins, read the history of every incoming webhook, and build email templates per type.

01 ·Put the rewards store on an outside site

The rewards store can now sit inside a broker's own web and mobile app as an embeddable widget. A trader signs in to the widget and spends their coins on items there, the way they would inside the community, and a broker themes the widget to match the surrounding portal. A Purchase History travels with it, so a trader can see the items they have redeemed from the same place.

Why it matters

A broker who keeps traders in their own portal wants the place to spend coins to live there too, not behind a separate link. Dropping the store into the portal where a trader already is keeps the earn-and-spend reward loop in one continuous flow, themed so it reads as the broker's own.

02 ·Read the history of every incoming webhook

An incoming webhook now keeps a history a broker can open from its setup. The history lists each call it has received in date order, marked Success, Failed, or Processing, with a search and a filter that narrows to a chosen outcome. A broker opens any entry to see the data that came in with it.

Why it matters

A broker feeding data in from their own systems wants to confirm a call arrived and see what it carried, not guess from the result downstream. A per-webhook history with the data of each call gives a broker a record to check a sync against when a value looks off.

03 ·Build email templates for each type of message

The email templates settings now hold more than one template per type of message, and a broker marks which one is active for that type. A broker edits a template, renames it, and the active one is the version traders receive. New templates arrive for the welcome email a trader gets on joining, the email that verifies a new registration, and the one that carries a one-time code for a sign-in reset, each editable to carry the community's name and wording.

Why it matters

The first emails a trader gets, joining and confirming an account, set the tone for the community. Letting a broker keep several versions and pick the active one means those messages read in the broker's own voice rather than a default.

04 ·Chart a custom field on the analytics dashboard

The analytics dashboard can now build a chart from a custom field. A numerical field can be shown as a total or an average and broken out by role, and a true-or-false field can be drawn as a doughnut or a bar, with the bar set to count or to percentage and held to the value a broker wants on the axis.

Why it matters

A broker who tracks their own data in a custom field wants to see it move alongside the built-in numbers, not export it to read it. Charting a field a broker defined, split by role, puts the cut they care about on the same dashboard they already watch.