Conditional Sections Deep Dive

Overview

Conditional sections enable sophisticated survey branching by showing entire question groups based on checkbox selections. This advanced feature creates personalized survey experiences, reduces respondent burden, and enables complex multi-path surveys.

What You'll Learn:

• How conditional sections differ from skip logic
• Creating checkbox-triggered sections
• Advanced conditional patterns
• Combining conditional sections with skip logic
• Troubleshooting and optimization

Prerequisites:

• Familiarity with Survey Sections basics
• Understanding of checkbox questions
• Basic survey builder experience

Conditional Sections vs Skip Logic

When to Use Conditional Sections

Best For:

• Grouping multiple related follow-up questions
• Product-specific or role-specific question sets
• Multiple parallel branches from a single trigger
• Keeping survey organized and manageable

Example Use Cases:

• Product usage survey with separate sections per product
• Employee survey with role-based question groups
• Customer feedback with department-specific sections

When to Use Skip Logic

Best For:

• Individual question routing
• Complex multi-condition logic
• Navigation control (skip ahead, end survey)
• Fine-grained question visibility within sections

Example Use Cases:

• NPS score routing to different feedback questions
• Satisfaction-based follow-ups
• Qualification screening with early termination

Combined Approach

Use both together for maximum flexibility:

• Conditional sections: Major survey branches (product/role selection)
• Skip logic: Fine-tuning within each branch (satisfaction routing)
• Result: Sophisticated, well-organized surveys

How Conditional Sections Work

Trigger Mechanism

Requirements:

1. Must use checkbox question as trigger
2. Checkbox must have multiple options
3. Each option can trigger a different section
4. Multiple sections can trigger simultaneously

Why Checkbox Only?

• Allows multiple selections
• Each selection triggers corresponding section(s)
• Enables parallel question sets
• Natural user mental model

Display Logic

Respondent Experience:

1. Views and answers checkbox question
2. Selects one or more options
3. Corresponding sections appear immediately below
4. Deselecting option hides section dynamically
5. Changes happen in real-time

Visibility Behavior:

• Sections hidden until triggered
• No indication section exists
• Appear smoothly when condition met
• Stack vertically in creation order
• Each section maintains its own state

Condition Evaluation

OR Operator (Default):

• Show section if ANY selected option matches condition
• Most common use case
• Example: Show "Product A Section" if "Product A" selected

AND Operator (Advanced):

• Show section only if ALL selected options match condition
• Rare use case
• Example: Show "Premium + Enterprise Features" if both "Premium" AND "Enterprise" selected

Creating Conditional Sections

Step 1: Plan Your Survey Flow

Before building, map out the structure:

Questions to Answer:

• What are the main categories/products/topics?
• What questions are specific to each?
• How do categories relate?
• What are expected respondent paths?

Example Survey Plan:

Main Question: "Which products do you use?" (Checkbox)
- Option 1: Product A
- Option 2: Product B
- Option 3: Product C

Conditional Sections:
- "Product A Feedback" (3 questions) - triggered by Product A
- "Product B Feedback" (3 questions) - triggered by Product B
- "Product C Feedback" (3 questions) - triggered by Product C

Possible Paths:
- Product A only: See Product A section only
- Product A + B: See both Product A and B sections
- All three: See all three sections

Step 2: Create Trigger Question

1. Add new question to survey
2. Select "Checkbox" question type
3. Enter clear question text:
   • Example: "Which products do you use? (Select all that apply)"
4. Add options:
   • Each option represents a potential section trigger
   • Use descriptive option text
   • Example options: "Product A", "Product B", "Product C"
5. Set as required (recommended)
6. Save question

Best Practices for Trigger Questions:

• Clear, action-oriented question text
• 3-7 options (avoid overwhelming users)
• Mutually exclusive options (usually)
• Include "Other" with text field if needed
• Descriptive option labels

Step 3: Create Conditional Section

1. Click "Manage Sections" in left sidebar
2. Click "+ Add Section"
3. Enter section details:
   • Name: Descriptive, related to trigger option
   • Good: "Product A Detailed Feedback"
   • Bad: "Section 2"
   • Description (optional): Context for respondents
   • Example: "Please answer these questions about your Product A experience"
   • Type: Select "Conditional Section"
4. Click "Create Section"
5. Section appears in section list

Step 4: Configure Display Conditions

Condition editor opens automatically after creating conditional section:

1. Trigger Question: Select checkbox question from dropdown
2. Display Conditions: Configure which options trigger display
   • Click checkbox options to select
   • Can select single or multiple options
   • Example: Select "Product A" option
3. Operator: Choose logic
   • OR: Show if ANY selected option matches (default, recommended)
   • AND: Show if ALL selected options match (rare)
4. Click "Save Conditions"

Example Configurations:

Single Option Trigger:

• Trigger Question: "Which products do you use?"
• Selected Options: ["Product A"]
• Operator: OR
• Result: Section shows when "Product A" selected

Multiple Option Trigger (OR):

• Trigger Question: "Which products do you use?"
• Selected Options: ["Product A", "Product B"]
• Operator: OR
• Result: Section shows when EITHER "Product A" OR "Product B" selected

Multiple Option Trigger (AND):

• Trigger Question: "Which products do you use?"
• Selected Options: ["Product A", "Product B"]
• Operator: AND
• Result: Section shows ONLY when BOTH "Product A" AND "Product B" selected

Step 5: Add Questions to Section

1. Create new questions OR move existing questions
2. Assign to conditional section:
   • Drag and drop method
   • Or use question menu → "Move to Section"
3. Questions only visible when section triggered
4. Can include any question types
5. Can have 1-10+ questions per section

Question Organization:

• Group related questions together
• Order logically within section
• Consider question dependencies
• Balance section length

Step 6: Test Conditional Logic

1. Click "Preview Survey"
2. Navigate to trigger question
3. Test each checkbox option:
   • Select option
   • Verify correct section appears
   • Check questions display properly
4. Test combinations:
   • Multiple options selected
   • All options selected
   • Deselecting options
5. Verify section hiding/showing works

Advanced Conditional Section Patterns

Pattern 1: Product Matrix

One trigger question, multiple product sections:

Setup:

• Checkbox: "Which products do you use?"
  • Product A, Product B, Product C, Product D

Sections:

• "Product A Feedback" (triggered by Product A)
• "Product B Feedback" (triggered by Product B)
• "Product C Feedback" (triggered by Product C)
• "Product D Feedback" (triggered by Product D)

User Scenarios:

• Selects A + C: Sees Product A and Product C sections
• Selects all: Sees all four sections
• Selects B only: Sees Product B section only

Benefits:

• Clean organization
• Each product gets focused questions
• Survey length adapts to user's products
• Easy to analyze product-specific feedback

Pattern 2: Role-Based Branching

Different question sets by role:

Setup:

• Checkbox: "What best describes your role?"
  • Developer, Designer, Product Manager, Executive

Sections:

• "Developer Experience" (if Developer)
• "Designer Experience" (if Designer)
• "Product Manager Experience" (if Product Manager)
• "Executive Experience" (if Executive)

Use Case:

• Team satisfaction survey
• Each role gets relevant questions
• Can select multiple roles (e.g., Designer + Product Manager)
• Reduces survey fatigue

Pattern 3: Issue Investigation

Multi-level conditional sections:

Level 1 Trigger:

• Checkbox: "Did you experience any issues?"
  • Technical, Billing, Support, Other

Level 1 Sections:

• "Technical Issue Details" (if Technical selected)
• "Billing Issue Details" (if Billing selected)
• "Support Issue Details" (if Support selected)

Level 2 Trigger (within Technical section):

• Checkbox: "What type of technical issue?"
  • Login, Performance, Feature Bug

Level 2 Sections:

• "Login Issue Follow-up"
• "Performance Issue Follow-up"
• "Bug Report Form"

Depth Recommendation: Max 2-3 levels

Pattern 4: Feature Usage Deep Dive

Learn about specific feature usage:

Setup:

• Checkbox: "Which features do you use regularly?"
  • Analytics, Reporting, Automation, Integrations

Sections:

• "Analytics Dashboard Feedback" (detailed analytics questions)
• "Reporting Tools Feedback" (report-specific questions)
• "Automation Feedback" (automation use cases, reliability)
• "Integration Feedback" (which integrations, stability, wishes)

Benefits:

• Targeted feature feedback
• Avoids asking non-users about features
• Identifies power users vs casual users
• Informs product roadmap

Combining with Skip Logic

Why Combine?

Conditional Sections: High-level survey structure

Skip Logic: Fine-tuned routing within structure

Together: Powerful, well-organized surveys

Example: Customer Satisfaction Survey

Level 1: Conditional Section (Product Selection)

Checkbox: "Which products do you use?"
→ Conditional Section: "Product A Feedback"

Level 2: Skip Logic (Within Product A Section)

Question: "Satisfaction with Product A?" (1-5 rating)
→ Skip Logic:
  - If rating ≤ 2: Show "What disappointed you most?"
  - If rating ≥ 4: Show "What do you love most?"

Benefits:

• Clean major branches via sections
• Nuanced routing via skip logic
• Best respondent experience
• Maintainable survey structure

Implementation Strategy

1. Plan both layers before building
2. Build sections first (major structure)
3. Add skip logic second (fine-tuning)
4. Test each layer independently
5. Test combined behavior thoroughly

Best Practices

Section Design

Naming:

• Use clear, descriptive names
• Match trigger option language
• Example: Trigger "Product A" → Section "Product A Feedback"

Description:

• Explain section purpose
• Provide context for respondent
• Set expectations for number of questions
• Example: "The following 3 questions are about your Product A experience"

Length:

• 2-6 questions per section (ideal)
• Max 10 questions per section
• Break very long sections into multiple sections
• Balance depth vs respondent fatigue

Trigger Question Design

Question Text:

• Be explicit about multiple selections
• Example: "Which products do you use? (Select all that apply)"
• Clear call-to-action

Options:

• Comprehensive but not overwhelming
• 3-7 options ideal
• Include "None of the above" if applicable
• Include "Other" with text field if needed

Placement:

• Early in survey (after intro)
• Before conditional sections
• After any qualification questions

User Experience

Smooth Transitions:

• Sections appear/disappear gracefully
• No jarring layout shifts
• Clear visual separation

Clear Context:

• Section headers clearly visible
• Description provides purpose
• Questions obviously related to trigger

Progress Indicators:

• Show overall progress even with conditional sections
• Update dynamically as sections appear
• Don't penalize for longer paths

Testing Strategy

Comprehensive Testing:

• Test all checkbox combinations
• Test selection and deselection
• Test on mobile devices
• Test with screen readers
• Pilot test with real users

Edge Cases:

• No selections (if allowed)
• All selections
• Rapid selection changes
• Browser back button behavior

Analytics for Conditional Sections

Key Metrics

Trigger Rate:

• % of respondents who saw each section
• Identifies popular vs unused sections
• Helps prioritize product/feature focus

Completion Rate:

• % who completed section after seeing it
• Identifies problematic sections
• Shows engagement by section

Time Metrics:

• Average time per section
• Median time (removes outliers)
• Time distribution

Example Analysis:

Product A Section:
- Trigger Rate: 65% (most popular)
- Completion Rate: 95% (high engagement)
- Average Time: 1m 45s

Product D Section:
- Trigger Rate: 12% (rarely used)
- Completion Rate: 78% (some drop-off)
- Average Time: 3m 20s (taking longer)

Actions:
- Invest in Product A (high usage, engagement)
- Investigate Product D (longer time, lower completion)
- Consider removing rarely-triggered sections

Optimization

Based on Analytics:

1. Remove sections with <5% trigger rate
2. Simplify sections with high drop-off
3. Shorten sections with very long completion times
4. Focus on high-trigger, high-completion sections

Troubleshooting

Issue: Section Not Appearing

Checklist:

1. Verify trigger question is checkbox type
2. Check condition configuration (correct option selected)
3. Ensure section type is "Conditional"
4. Test in preview mode
5. Check for JavaScript console errors

Common Fixes:

• Reconfigure conditions
• Verify trigger option spelling matches exactly
• Clear browser cache

Issue: Wrong Section Appears

Debugging:

1. Review all conditional section mappings
2. Check for duplicate triggers (multiple sections, same trigger)
3. Verify operator (OR vs AND)
4. Test each option individually

Solutions:

• Remove duplicate triggers
• Adjust operator if needed
• Reconfigure conditions

Issue: Section Won't Hide

Symptoms:

Section stays visible after deselecting checkbox

Causes:

• Required questions in section (can't hide with validation errors)
• Browser caching issue
• Skip logic conflict

Solutions:

1. Make questions optional or remove validation errors
2. Hard refresh browser (Ctrl+Shift+R)
3. Review skip logic for conflicts