Quiz analytics and logs, and a store purchase callback
A store SDK callback fires after a successful purchase, published quizzes gain an analytics view, and quiz activity joins the Mini Games Log.
01 ·A callback after a successful store purchase
The store widget SDK can now call your own systems the moment a purchase succeeds. Once the order is recorded and the coins are deducted, the platform sends a one-way callback to your SDK host carrying the purchase details: the product and its cost, the trader by your own custom identifier, their coin balance before the purchase, the cost, the balance after, and the time it happened. The callback does not wait for a reply and reads nothing back, and if it is missing or fails the purchase still goes through, so the trader is never blocked. A new Callback Log in settings records every trigger with the details sent and the time, so your team can confirm what went out for a given purchase.
A callback at the moment of a store redemption lets a broker's own platform record or act on the spend as it happens, rather than polling for it. The Callback Log gives support a place to confirm a callback fired and what it carried, so the spend half of the earn-and-spend loop reaches the broker's systems without a separate reconciliation step.
02 ·An analytics view for quizzes
Published quizzes gain an Analytics view, opened from the quiz card or the quiz editor. It shows the total responses and when the last one arrived, then a summary card for each question with a chart and a legend of counts and percentages. Single-select and multi-select questions read as a share of the answers given, and a score-prediction question groups responses by scoreline. An option set as the right answer carries a Correct Answer tag. A question or option removed after traders had answered is kept from each attempt and marked as deleted, so past responses still read correctly once a quiz is edited.
Quiz results only shape a broker's next quiz if they can read them at a glance. A per-question breakdown, with the right answers marked and removed content preserved, turns a run of attempts into something a broker can learn from and keeps the activity earning its place in the loop.
03 ·Quiz activity in the Mini Games Log
Quizzes join the Mini Games Log alongside Spin the Wheel. A Game History lists a quiz's completed attempts, newest first, searchable by display name or email and downloadable as a CSV, and opening an attempt shows the trader, their answers, and the score. A User Log gives a per-trader view with attempts used, attempts remaining, best score, and last completed, and compares several quizzes side by side. An admin can set a trader's attempts count as a direct number, which feeds their remaining attempts. From an attempt an admin can also correct the answers or the score, with a recompute that rescores from the edited answers, a warning when a manual score does not match, the original response kept and restorable, and every change written to an edit history with the reason.
When a trader queries a quiz result, a broker needs the attempt in front of them and a way to put it right. A searchable history, per-trader metrics, and an attempt they can correct with an audit trail settle the question from one place, so a run of quizzes stays manageable as the community grows.
A round of custom widget fixes across the earning overview and other embedded widgets, covering responsiveness and layout.
13 JulLoading earlier messages in a channel is faster and smoother on large communities.
13 Jul