The homepage quiz is back with a cleaner interface and the same backend contract. That matters because the goal of the quiz is not just to look nice. It helps us learn how sellers operate so we can improve onboarding, messaging, and future product decisions without breaking the data flow that already existed.
What improved
The new version is calmer to use. The question flow has better spacing, stronger type hierarchy, cleaner option states, and a result card that feels more deliberate instead of temporary.
We also tightened the submission behavior so it is harder to double-submit accidentally. That protects the quiz experience on slower devices and low-bandwidth connections.
What did not change
The important part is the contract. The quiz still asks the same three questions and still posts the same payload keys to the same endpoint. That means reporting and database writes remain compatible with the old implementation.
Keeping that contract stable lets us improve the interface without introducing hidden breakage into marketing analytics or downstream reporting.
- Same three-question flow
- Same payload keys
- Same `/api/marketing/quiz` endpoint
- Same database write behavior
Why this matters
A homepage quiz should do two things well: help the visitor understand where they fit, and give the business a sharper picture of who is arriving. If the UX is clumsy, people abandon it. If the payload changes carelessly, the insight disappears.
This version keeps both sides intact. Sellers get a quicker, clearer interaction, and the team still receives the data needed to understand acquisition patterns and ordering preferences.
Key takeaway
The new quiz is mostly a UX upgrade, but the real win is that the data layer stayed intact while the experience improved.