Quiz builds tend to spend their effort on the questions. Question order, answer wording, how many to ask, where the drop-off is. All of that matters and most of it is well covered.
Then the results page gets built in an hour on the last day.
Interact’s platform data, drawn from more than 80 million leads, puts start-to-finish completion at 65% and start-to-lead conversion at 40.1%. Two thirds of people who start finish. Which means the questions, broadly, are working. The purchase decision happens after all of that, on a page most brands treat as an output screen.
Three things, and they happen in this order in the reader’s head.
Confirm they were heard. The customer answered seven questions. The page needs to reflect those answers back before it sells anything, because otherwise the recommendation reads as a product the brand wanted to move.
Justify the recommendation. Not exhaustively. One clear reason per product, tied to a specific answer.
Make the next action unmistakable. One primary button, doing one thing.
This is the first block and it does the confirming. It restates the customer’s inputs in your language rather than theirs, which is where the value is: “Dry skin, fragrance sensitivity, morning-only routine” tells them you understood, and repeating their exact selections back as a checklist does not.
Weak version: a headline that says “Your Results.” Strong version: a two-line summary that a customer would recognise as a description of themselves.
One sentence per recommended product, connecting it to an answer. “Because you mentioned fragrance sensitivity” beats any amount of ingredient copy at this position on the page.
The mistake worth naming is stacking every benefit the product has. The customer did not ask for the full case. They asked one question and the page is answering it.
This is where a quiz either converts or hands the customer back to browsing. If the results page pushes people to a collection page, the quiz has done the work of narrowing and then discarded it.
Sensez renders specific SKUs on the results page with a direct add-to-cart, and syncs against your Shopify catalogue so anything out of stock drops out of the recommendation automatically. That second part is unglamorous and matters more than it sounds: a results page recommending a sold-out product does more damage than a generic one, because it burned seven questions of goodwill first.
Image weight is the other thing to watch here. Results pages carry the most imagery in the whole quiz flow, and the page loads at the exact moment of highest intent. Do quiz apps slow down your Shopify store covers the general problem, and the results page is where it bites hardest.
One or two alternatives, clearly subordinate. This gives the customer a choice without reopening the whole catalogue, and it catches the person whose primary recommendation is nearly right.
One primary action. Add to cart, add the bundle, or subscribe. If your page has three buttons of equal weight, it has no primary action.
Sensez supports bundle logic here, where the quiz assembles a complementary set based on answers and adds the whole thing in one click, and can apply a bundle discount at checkout automatically. Whether a bundle or a single product should be the primary action depends on your price point, and it is a good first test.
A results page recommending a sold-out product does more damage than a generic one, because it burned seven questions of goodwill first.
Sensez quizzes route through conditional branching. Later questions appear based on earlier answers, so two customers can take genuinely different paths through the same quiz.
This has a design consequence people miss. If the paths diverge, the results pages should too. A customer who was routed down a beginner path and one routed down an advanced path should not land on identically structured pages with different SKUs swapped in. The beginner page needs more explanation and fewer options. The advanced page needs specificity and can afford to skip the education.
Practically: map your major branches, then check that each terminal state has a results page written for it. Most quizzes have three or four meaningfully different outcomes and one results template.
Three positions, three different trades.
Gating before results gives you the highest capture rate and the lowest quality of consent. The customer has invested seven answers and wants the payoff, so most of them will hand over an address, and some of those addresses will be fake or abandoned.
Gating partially, showing the recommendation and holding the detail, is the middle position and the hardest to execute without feeling like a trick.
Ungated, with the email request after results, produces fewer addresses and better ones. It also removes the friction at the highest-intent moment, which matters more if your primary goal is the purchase rather than the list.
There is a fourth option worth knowing about: capturing the email early but showing results regardless. Sensez supports capturing the address before the results page and triggering a Klaviyo flow if the customer drops off without buying, which recovers a share of the people who would otherwise vanish. This gets you the list without gating the payoff.
If your quiz exists primarily to build an email list, gate. If it exists primarily to sell, do not. Most brands say the second and build the first.
Fewer than a collection page, more than one.
One recommendation reads as a decision made for the customer and leaves nowhere to go if it misses. A dozen recreates the problem the quiz was supposed to solve.
The research here is often cited badly, so worth being accurate about. Iyengar and Lepper’s 2000 study found people more likely to buy when offered six options rather than twenty-four, in a supermarket jam display and two other settings. That study has had a difficult decade: a 2010 meta-analysis across fifty studies found close to no overall effect, and later work suggests it shows up under particular conditions rather than universally. So the honest version is that fewer options probably helps in some circumstances and the evidence is not settled enough to give you a number.
What does hold up as practical guidance:
Where the quiz lives changes what the results page should do.
Sensez publishes a quiz three ways: as a full-page landing experience, as an embedded block inside a product page, or as a timed pop-up. Each one hands the customer off differently.
A full-page quiz owns the whole screen, so its results page can be the destination and should carry the full recommendation, reasoning, and bundle. A product page embed sits inside an existing page with its own add-to-cart, so the results have to resolve without fighting the surrounding page. A pop-up quiz needs the shortest results treatment of the three, because the customer was interrupted rather than seeking it out.
One thing to confirm on your own build rather than assuming: the documented placements are landing page, product page, and pop-up. If you are planning a collection page embed, check it against your setup before designing around it.
If your quiz exists primarily to build an email list, gate the results. If it exists primarily to sell, do not. Most brands say the second and build the first.
Test the primary action first. Single product versus bundle as the main button is the highest-leverage change on the page and the easiest to read.
Test the email gate second, and test it as a revenue question rather than a capture question, or you will always conclude that gating wins.
Do not bother testing button colours, headline microcopy, or image crops until the two above are settled. At mid-market volume you do not have the traffic to resolve small effects, and a test you cannot resolve is worse than no test because it produces a confident wrong answer.
On volume: if your quiz sees a few hundred completions a month, a test needs a quarter to say anything. Run fewer, bigger tests. A dedicated piece on quiz A/B testing is coming, and quiz analytics decoded covers what to instrument first.
Some verticals cannot write the results page the way a coffee brand can.
CBD and supplement results pages carry claim restrictions that apply to the reasoning block specifically, since that is where copy drifts toward what the product does for a condition. Write the reasoning against the customer’s stated preference rather than an outcome.
Adult wellness results pages inherit the discretion requirements collected during the quiz. If the customer indicated a need for discretion, that governs imagery on the results page, not just the packaging.
Wine and other age-restricted categories have an age gate interacting with the results page, and the order of those two screens is worth deliberately deciding rather than inheriting from a template.
The four vertical playbooks go deeper on each: CBD, supplements, pet food, wine, and adult wellness.
Open your own results page and answer one question: could a customer tell, from the page alone, which of their answers produced this recommendation?
If not, that is the first fix, and it is a copy change rather than a rebuild. Everything else on this page is optimisation on top of a page that is already doing its job. If you would rather have the results page designed alongside the quiz logic instead of after it, that is what our Concierge builds do.
