What is Conditional Logic?

Conditional Logic lets you control when, how, and whether a question appears—based on prior responses or system data. This allows you to create smarter, more personalized surveys that adapt to each participant’s journey.

---

Purpose

• Personalize surveys based on individual answers
• Skip irrelevant questions
• Drive dynamic follow-up logic (e.g., show open-ended fields only for dissatisfied responses)
• Reduce cognitive load for the user

---

Core Configuration Options

Option	Description
Yes, always ask	Always show the question and require an answer
No, never ask	Hide the question for all participants
Yes, if not pre-populated	Only show the question if there’s no prior data (e.g., metadata missing)
Visible only in read-only mode	Show the question but disable editing

---

How to Configure

1. Apply visibility/editability controls under the question’s settings.
2. Use Display Logic or Hide Logic to set conditional triggers.
3. Choose the source field (prior question or metadata) and select your logic operator.

---

Display Logic

Purpose: Show this question only if a specific condition is met.

Use Case:
→ Only ask “Rate Feature X” if the participant said “Yes” to “Have you used Feature X?”

---

Hide Logic

Purpose: Remove this question from view if a certain condition is met.

Use Case:
→ Hide “Tell us why not” if the participant gave a satisfaction score ≥ 4

---

How to Add Logic

Click “Add Display Logic” or “Add Hide Logic” under the question settings. Then:

1. Select a source field:

   • A previous question
   • A metadata field (e.g., CASEID, CustName)

2. Choose an operator and a value (see below)

---

Supported Operators

Operator	Description
is	Triggers when the answer matches exactly (e.g., “Country is United States”)
is not	Triggers when the answer does not match (e.g., “Response is not ‘No’”)
less than	Triggers for numbers below a threshold (e.g., “Rating < 4”)
less than or equal to	Triggers for numbers ≤ threshold (e.g., “Score ≤ 7”)
greater than	Triggers for numbers > threshold (e.g., “Age > 18”)
greater than or equal to	Triggers for numbers ≥ threshold (e.g., “Score ≥ 8”)
between	Triggers for numeric ranges (inclusive), e.g., “Score between 3 and 5”

---

Source Fields for Logic

When adding a Display or Hide rule, the logic can be based on:

1. Metadata Fields

These are hidden system values like:

• CASEID
• CustName
• Language
• UserType

Use when: you want to branch logic based on known attributes (e.g., user type, location, ID match).

2. Previous Questions

All questions you’ve added in the survey appear here—whether it’s:

• Rating: “How would you rate your experience?”
• Multiple Choice: “Which features did you use?”
• Open Ended: “Tell us what we can improve.”
• NPS: “How likely are you to recommend us?”

Just scroll and select the exact question text as the reference.

---

Example Scenarios

Scenario 1: Display Logic

Condition: Show “What didn’t work for you?"
If: Rating question “Rate your experience” is less than 4

Scenario 2: Hide Logic

Condition: Hide “Explain why you didn’t continue”
If: Multiple Choice “Did you complete the sign-up?" is “Yes”

Scenario 3: Metadata-Based Logic

Condition: Show “Please confirm your location”
If: Metadata field City is not populated

---

Best Practices

• Always test logic paths before launch
• Keep conditions simple and intuitive for the participant
• Use metadata when survey personalization depends on external data
• Avoid overlapping Display and Hide rules for the same question—they may conflict

---

This is part of the Survey Guide in Zykrr’s Documentation Hub.
Need help setting up logic trees, metadata triggers, or validation rules? Contact support@zykrr.com.