Conditional Logic Examples and Use Cases
Conditional logic is easier to understand through examples than through abstract descriptions. This guide walks through four real-world scenarios that represent common use cases across different store types — with clear explanations of the logic used and why it works.
Example 1: Skincare Quiz Branching by Skin Type
Context: A skincare store wants to ask different follow-up questions depending on whether the customer has oily, dry, or combination skin. Customers with different skin types have different concerns, and asking everyone the same follow-up questions produces less accurate recommendations.
Quiz structure:
Question 1: "What is your skin type?" (Single selection: Oily / Dry / Combination / Sensitive)
Logic jumps:
If "Oily" is selected → Jump to Q2a (concerns for oily skin: excess shine, large pores, breakouts)
If "Dry" is selected → Jump to Q2b (concerns for dry skin: flakiness, tightness, sensitivity)
If "Combination" or "Sensitive" is selected → Jump to Q2c (general skin concerns)
Default → Jump to Q2c
What the customer experiences: Each customer sees only the follow-up question relevant to their skin type. An oily-skin customer never sees the dry-skin question, and vice versa. The quiz feels personalised from the very first branch.
Why logic jumps are the right choice here: The three sets of follow-up questions are completely separate — there is no reason for an oily-skin customer to ever see the dry-skin questions. Logic jumps create clean, distinct paths for each group.
Example 2: Gift Quiz Filtering by Recipient
Context: A gift shop wants to tailor questions based on who the gift is for. If someone is shopping for themselves, asking about the recipient's age and preferences is irrelevant and adds unnecessary friction.
Quiz structure:
Question 1: "Who are you shopping for?" (Single selection: For me / For someone else)
Show condition: "What is the recipient's age range?" only shows if the answer to Q1 is "For someone else"
Show condition: "What is your relationship to the recipient?" only shows if the answer to Q1 is "For someone else"
What the customer experiences: Customers shopping for themselves skip straight to questions about their own preferences. Customers shopping for someone else are asked the additional context questions about the recipient before continuing.
Why show/hide is the right choice here: The quiz flow is broadly the same for both groups — both are asked about budget, category preferences, and style. It is only these two specific questions that need to be conditional. A full logic jump is unnecessary; a show condition on those two questions achieves the same result with less configuration.
Example 3: Supplement Quiz Ending Early for a Specific Answer
Context: A supplement brand sells products designed for adults. If a customer indicates they are under 18, the brand does not want to show adult supplement recommendations. Instead, they want to end the quiz early with an appropriate message.
Quiz structure:
Question 1: "What is your age range?" (Single selection: Under 18 / 18–25 / 26–35 / 36+)
Logic:
If "Under 18" is selected → Jump to End (a result page configured with a message such as: "Our products are designed for adults aged 18 and over. Please speak to a healthcare professional for guidance suitable for your age.")
Default → Continue to Q2
What the customer experiences: Adult customers continue through the quiz normally. Customers who select "Under 18" are shown the end result page immediately, without seeing any product recommendations.
Why this works: Quizify's logic jumps allow you to route a customer to the end of the quiz (not just to another question) based on an answer. By configuring a specific result page for this segment, you handle the edge case gracefully without disrupting the experience for the majority of customers.
Whenever you use logic jumps, always define a Default rule. The Default rule is what happens if none of your specific conditions are met — it is your fallback path. Without a Default, customers whose answers do not match any condition may get stuck or follow an unintended path.
Example 4: Fashion Quiz Using Multiple Conditions for a Show/Hide
Context: A fashion store wants to ask about occasions (work, weekends, evenings out) but only when the customer selects a style that implies they dress for multiple contexts. Customers who select only "Activewear" only need activewear-specific questions.
Quiz structure:
Question 1: "How would you describe your style?" (Multiple selection: Casual / Smart Casual / Formal / Activewear)
Show condition: "What occasions do you dress for?" shows if the customer selects "Casual" OR "Smart Casual" OR "Formal"
Customers who select only "Activewear" skip the occasions question
What the customer experiences: Customers who select any non-activewear style see the occasions question, which helps the quiz recommend products suited to their lifestyle. Customers who select only Activewear skip it — their entire context is already captured.
Why multiple OR conditions are needed: The occasions question should appear for any customer who has at least some variety in their dressing context. Using OR conditions means the question shows if any one of the specified styles is selected — it is not necessary for all three to be selected.
Planning Your Own Logic
Before you start configuring logic rules in Quizify, take time to plan your quiz flow. Here is a practical approach:
1. Map your quiz flow on paper first. Write out your questions and draw arrows showing which answers should lead where. This gives you a visual reference to work from and makes it much easier to spot gaps or conflicts in your logic.
2. Identify which questions need branching. Go through your question list and note which questions have answers that should send customers to different paths or conditionally show/hide other questions.
3. Identify the trigger answers. For each branch, note the specific answer (or answers) that trigger the logic. These are the answers you will set as the source conditions in Quizify.
4. Choose the right logic type for each situation. Use logic jumps when groups of customers need to follow entirely different question paths. Use show/hide conditions when individual questions should appear or disappear for certain customers within the same overall flow.
5. Always add a Default rule to logic jumps. Any question with a logic jump should have a Default — the path customers take if their answer does not match any of your specific conditions. Without a Default, the quiz may behave unpredictably for edge-case answers.
6. Test every path thoroughly using Preview. After setting up your logic, use Quizify's Preview function to walk through your quiz selecting each answer option. Verify that every path leads where you expect, including the Default/fallback path. Testing before publishing saves your customers from encountering broken quiz flows.