
How to build a product quiz and preference center in Klaviyo
Build a product quiz people finish, store the answers as Klaviyo properties and segments, use them in your welcome flow, and offer fewer emails before none.
The Wizel Team
Email marketing strategist · · 7 min read
On this page
- Decide which kind of quiz you need
- Write the questions from the flows backward
- Put the email gate before the results
- Store the answers as properties and segments
- Use the answers in the welcome series and campaigns
- Build a preference center that saves the unsubscribe
- How to build a product quiz and preference center in Klaviyo
- Frequently asked
A quiz is a sign-up form that also tells you what to send. Build one, collect the answers, then send everyone the same welcome email, and you've made a slow pop-up. This guide covers building a quiz people finish, the questions to ask, storing the answers in Klaviyo, using them in the welcome series and campaigns, and a preference center that keeps people who were about to unsubscribe.
5-8
questions in a product-matching quiz people finish, in about 60-90 seconds
Decide which kind of quiz you need
Build a quiz only when the answer changes what the person should buy. The chapter on growing a list that buys covers that test, and the guide to running modern email marketing shows where the list fits in the whole program. Add one more filter: the result has to say something about the visitor. "Your skin is oily" or "you train for endurance" is a result. A pantry staple or a seasoning has no result to give, so a quiz there is a slower pop-up. If the result touches health, keep it to what the brand can stand behind. A quiz isn't a diagnosis.
| Build | Questions | Where the email goes | Ends on |
|---|---|---|---|
| One question on the pop-up | 1, the one a flow will branch on | Before the question | The welcome code, sent by email |
| Pop-up quiz | 3-5, with 3-4 options each | After the last question, or straight after the first | The welcome code, sent by email |
| Product-matching quiz | 5-8, one per screen on mobile, with a progress bar | After the last question, before the results | One matched product and its matched offer |
Taking the email straight after the first question of a pop-up quiz keeps the visitors who drop out halfway; it suits pop-ups of two questions or more. A matching quiz keeps the gate before the results, because the results are what the visitor is working toward.
For agencies auditing a new client: one zero-party question that a flow will branch on belongs on the pop-up checklist beside the offer and the timing. It's a smaller build than a quiz, and it proves the wiring before you build one.
Write the questions from the flows backward
Start from the properties, not the questions. Pick the 4-6 facts your flows will branch on (the list growth chapter has a table by store type), then write one question for each. If a question doesn't change the recommendation or write a property you'll use, cut it. Every question past eight loses a few more people.
- Easy and fun first, personal later. Open with the goal or a preference; age range or a skin concern comes near the end. Never open with the sensitive question.
- Three or four options, stacked. More choices, or options side by side, stall the tap.
- Simple beats clever. "Who are you shopping for? Men / Women / Both" takes under a second and still splits the list into groups worth sending different emails to.
- Ask why they're shopping, and allow "just browsing". The list growth chapter explains both: the reason tells the welcome flow what to sell, and a forced choice writes false data.
| Question | Options | Property | What changes |
|---|---|---|---|
| Who are you shopping for? | Dog / Cat / Both / Just browsing | pet_type | Which welcome branch they get |
| How old are they? | Puppy or kitten / Adult / Senior | life_stage | The formula you recommend |
| How big are they? | Small / Medium / Large | pet_weight_band | Portion size and reorder timing |
| What would you change about mealtime? | Picky eater / Sensitive stomach / Energy / Nothing yet | primary_concern | The proof and objection email one leads with |
| When's their birthday? | Pick a month | pet_birthday | A birthday email |
Put the email gate before the results
Ask for the email after the last question and before the results, with a line like "Enter your email to see your results." Gate at the start and you've earned nothing yet, so it converts like a pop-up. Show the results first and you've given away the reason to sign up.
- Say they're joining the list. A quiz that asks for an email before the results is a sign-up form, with the same consent rules as a discount pop-up. Say plainly that they're subscribing to marketing email.
- Save the answers at submit, so every property is on the profile before the first welcome email goes out.
- Results: one product, one offer. Show the best match and its matched offer, such as "your oily-skin starter set, 15% off." A page that lists the whole catalog tells the visitor the quiz was for show.
- Send the code by email. Say on the results page that the offer is on its way, and put the code in the first welcome email, as with any pop-up.
Store the answers as properties and segments
Wire the quiz end to end before it goes live. A quiz whose answers never change what you send is a decorative pop-up that cost far more to build.
| Step | In Klaviyo |
|---|---|
| Answer to property | Each question writes one profile property at submit: skin_type: oily, goal: sleep, roast_preference: dark |
| Property to segment | One segment per result group, such as skin_type equals oily |
| Segment to welcome branch | The welcome flow opens with a conditional split on the property; each branch leads with the matched product, proof and objection |
| Property to campaigns | Launches and restocks go to the matching segment first: "dark roast is back" reaches dark-roast drinkers 24 hours early |
- Fixed values, one fact per property. Name properties in lowercase with underscores and give each a set list of answers, never free text. Ten free-text properties with 40 spellings of "oily" segment nothing.
- Stamp the date. Save when each answer was given, as a companion date property or the quiz submission date, so "answered over 12 months ago" is a segment rather than a guess.
- Test with two addresses of your own. Take the quiz twice with different answers. If both get the same hero product in welcome email one, the mapping is broken.
Use the answers in the welcome series and campaigns
The welcome series is where quiz data pays first, because the first pitch arrives already matched. Split on the property at the top of the flow, before email one, and write each branch around its answer: the owner of a picky eater gets the formula, the proof and the objection for picky eaters, and the "just browsing" group gets your default series. In campaigns, the answers decide who hears about a launch or restock first; behavior segments handle the rest of the targeting.
- Route gift buyers away from refills. Ask "Who did you buy this for?" in the order confirmation or a day later. Gift buyers leave the replenishment flow and get a reminder before the occasion next year.
- Ask one question at a time after sign-up. A one-click poll in a regular campaign ("What are you shopping for next?" with 3-5 linked buttons, each writing the property) costs the reader one tap. For a high-priced product or a founder-led brand, a plain-text "hit reply and tell me your main goal" gets fewer answers but richer ones.
- Refresh answers after about 12 months. Pets grow, sizes change and goals shift. A one-click poll ("still team dark roast?") or a yearly "update your picks" campaign refreshes the data and doubles as an engagement send. Where an answer and recent orders disagree, the orders win.
Build a preference center that saves the unsubscribe
Put "fewer emails" on the page before "no emails". Someone who picks a weekly digest was about to unsubscribe; at one email a week, they stay a buyer. The unsubscribe link itself still has to be visible and work in one click, with no login or extra steps, as the consent rules require. The preference center offers a softer choice; it never blocks the exit.
| Option | What it writes | How sends respect it |
|---|---|---|
| How often: everything, a weekly digest, or big moments only | A frequency property | Every campaign excludes the tiers it isn't meant for |
| Pause for 30, 60 or 90 days | A pause property with its end date | Excluded from campaigns until the date passes |
| Categories (menswear or womenswear, coffee or equipment) | One property per choice | Targeting reads it on every send |
| Skip Mother's Day or Father's Day | skip_mothers_day: true | Every holiday send excludes it |
Offer only the choices your sends will honor. An ignored preference is worse than no preference center at all.
The pause matters most where people buy twice a year, as with gifts: pausing keeps them for the next occasion. For Mother's Day and Father's Day, and for baby and pregnancy products generally, send a short opt-out email 2-3 weeks before the date: one click to skip that occasion's emails, everything else stays. It costs one campaign slot. The property it writes has to sit in the exclusions of every holiday send, including the last-minute ones.
Your next step: list the 4-6 properties you'd branch on and the email that reads each one. Drop any question whose answer has no email waiting for it. Then build the first email those answers change, using the welcome email series guide.
How to build a product quiz and preference center in Klaviyo
- 1
Pick the properties
Choose 4-6 facts your flows will branch on and name the flow or campaign that reads each one.
- 2
Write the questions
Write one multiple-choice question per property, 5-8 in all, easy ones first, with 3-4 options and a just browsing answer.
- 3
Gate before the results
Ask for the email after the last question and before the results, saying plainly that they are joining the marketing list.
- 4
Show one match
Show one matched product and its matched offer, and send the code in the first welcome email.
- 5
Map answers to properties
Save each answer at submit as a lowercase profile property with fixed values, plus the date it was given.
- 6
Build segments and branches
Make one segment per answer and open the welcome flow with a conditional split on the property.
- 7
Target campaigns
Send launches and restocks to the matching segment first.
- 8
Add the preference center
Offer frequency tiers, a 30, 60 or 90-day pause and holiday opt-outs before a one-click unsubscribe, and exclude on them in every send.
- 9
Refresh yearly
Re-ask answers older than 12 months with a one-click poll, and let recent orders override stale answers.
Frequently asked questions
What is zero-party data?
Information a customer tells you on purpose, such as their size, their dog's weight or who they're shopping for. It's only worth collecting if a flow or campaign changes because of it.
How many questions should a product quiz have?
Five to eight for a product-matching quiz, taking 60-90 seconds, with one question per screen on mobile. A quiz inside a pop-up should stop at three to five.
Where should the email sign-up go in a quiz?
After the last question and before the results. At the start it converts like a pop-up, and after free results people have no reason to sign up.
How do I use quiz answers in Klaviyo?
Save each answer as a profile property with fixed values, build a segment for each answer, and open the welcome flow with a conditional split on that property so each group gets a different first email.
What should an email preference center include?
A choice of how often (everything, weekly or big moments only), a 30, 60 or 90-day pause, holiday opt-outs and any category choices you'll honor, shown before a one-click unsubscribe.


