Concept guide (partial) — Rule logic and side effects below are verified from Admin and server code. Per-brand derived attributes (for example age from date of birth) may need extra notes on your brand—see the filter conditions reference.

What it is

Pre-Validation is a reusable way to say “only continue if this person’s answers and profile data match these rules.”

You build one or more rule groups. Each group contains rows that pick an attribute (or questionnaire answer), a condition (such as equals, contains, or is empty), and the value to compare against.

Each group also has an AND or OR switch:

  • AND inside a group — every row in that group must match.
  • OR inside a group — at least one row in that group may match.

When you add more than one group, the person qualifies if any one group fully passes (same pattern as combining filter groups elsewhere in Admin).

Pre-validation reads stored profile answers, external info tags, and some profile settings. It does not look at live analytics event counts—that is what Tag Rules are for.

How to build rules

The editor is the same component on groups, communications, questionnaire answers, and attributes.

  1. Open the Pre-Validation section on the screen you are editing.
  2. Add a rule group, then add rows: choose an attribute or question, a condition, and values when the condition needs them.
  3. Set AND or OR for that group.
  4. Optionally add another group if you need “(A and B) OR (C and D)” style logic.
  5. Save the parent record (group, communication, question, and so on).

The condition dropdown uses the same operators as Singles Advanced Search search—for example equals, contains, is empty, date before/after. See the reference for plain-language definitions:

Attribute filter conditions (reference)

Empty groups: A group with no rows is treated like no rules, so downstream actions (such as sending a communication) are not blocked by mistake.

Questionnaire editor walkthrough

Use pre-validation on individual steps so follow-up questions or content appear only when earlier answers qualify.

Pre-validation on questionnaires is stored on each step (a question row or a content row), not on the questionnaire header. Members only see your changes after you Publish the parent questionnaire.

On a question step

  1. Open Questionnaires → click the questionnaire → click a Q row to open View Question.
  2. Expand the Pre-Validation section (same label as on other Admin screens).
  3. If this question appears in more than one questionnaire, use the batch content picker at the top of the section to choose which copy of the step you are editing.
  4. Build rule groups the same way as elsewhere: rows inside a group, AND or OR inside the group, and separate groups combined as “any group may pass.”
  5. Click Save when the section shows a Save button (content-only steps auto-save when you change fields).
  6. Return to the step list and Publish when you are ready for members to receive the update.

On a content step (message, button, image, or questionnaire branch)

  1. From the step list, click a T or A row (not Q) to open the batch content editor.
  2. Open the Pre-Validation tab in the left navigation.
  3. Configure rules the same way as on questions. See content step types for what each row type does in the member app.

Fields on each rule row

FieldWhat to chooseEffect
Attribute or Question On questionnaire screens you can switch the row type. Attribute compares a stored profile field (or tag from external info). Question compares the member’s answer to another step in this questionnaire. Question-based rules are useful for “only show step 5 if they answered Yes on step 2.” Attribute rules are useful for “only show this block if city equals …” using data already on the profile.
Attribute / Question picker Pick the field or earlier question text from the list. Defines what answer is compared when the member reaches this step.
Condition Same operators as Singles Advanced Search for choice, text, date, and empty checks—see which operators work where below. Determines pass vs fail for this row.
Responses / Value For choice questions, pick one or more answers. For free text, type the value. Date conditions show a date picker. Is empty / Is not empty need no value. The answer(s) the member must match (or must avoid) for the row to pass.
Add `AND` condition (+ inside a group) Adds another row to the same group with AND between rows. Every row in the group must pass.
Add `OR` condition Adds a new rule group. The member qualifies if any one full group passes — this widens the audience.

Common mistake: OR where you meant AND

To require two rules together — "stale profile and gender is male or female" — put both rows in the same group using the + button inside it. Using Add `OR` condition instead creates a second group, and the member then qualifies on either rule. A broad second rule such as "gender contains male, female" matches almost your entire brand, so the audience grows to everyone instead of shrinking to the overlap.

The editor marks the boundary between groups with an OR label. On one-time communications each group also shows a live profile count next to it — if a group you meant as a filter shows a number close to your whole member base, it is a separate OR group, not an added condition.

What members see in chat-style questionnaires

When the member moves through a Lora-style questionnaire, the system evaluates pre-validation on each upcoming step:

  • Rules pass — the step is offered normally (question, message, or linked sub-questionnaire).
  • Rules fail — the step is skipped or stored as hidden in the chat thread. The member is not shown an error message; the flow simply continues without that step.
  • They change an earlier answer — steps after the edited answer are re-checked. A step that was visible may become hidden (or the reverse) if their new answers change eligibility.

Answers the member already submitted stay saved even when a later step becomes hidden. Pre-validation controls visibility and offer order, not whether past answers are deleted.

Lora chat where a skipped step is not shown after pre-validation fails
Waiting for screenshot. Capture: a chat-style questionnaire where a follow-up step is hidden—the member sees the flow jump past it with no error message after an earlier answer disqualifies them.

Slide vs chat: The same rules are stored on each step, but On Boarding Slides and On Boarding Chat evaluate them differently. See Slide vs chat questionnaires before relying on branching in slide flows.

Worked example

Show a follow-up only for members who live in a specific city:

  1. Add your main location question earlier in the flow (if it does not exist yet).
  2. On the follow-up question or content row, open Pre-Validation.
  3. Add one group with one row: type Attribute, pick your city attribute, condition Contains / In, value = the city answer key(s) you want.
  4. Publish the questionnaire. Members outside that city never see the follow-up; members who qualify see it when they reach that point in order.

See also: View Questionnaire · Content step types

Slide vs chat questionnaires

Pre-validation on questionnaire steps behaves differently depending on the questionnaire Type you chose when creating it. Rules are saved the same way in Admin; the member app applies them through different pipelines.

See questionnaire types for which types use chat vs slides. This section covers On Boarding Chat, Home Lora Chat (and collapsible), vs On Boarding Slides.

TopicChat-style questionnairesSlide / wizard questionnaires
Where rules run verified — Primarily on the server as each step is delivered in Lora chat. The member app also re-checks visibility when messages load. verified — On the member device when the slide deck opens. Steps that fail are removed from the pager before the member swipes.
What members see when rules fail The step is skipped in the chat thread—no error message, no empty bubble. The slide never appears in the deck (the page count shrinks). There is no “skipped slide” placeholder.
When rules are re-checked verified — After the member edits an earlier answer, later steps are re-evaluated. A step that was visible may disappear (or the reverse). verified — Evaluated once when the questionnaire opens. Swiping forward does not re-filter the remaining slides mid-session.
Hidden step answers Earlier answers stay saved. Hidden steps are not offered again unless rules change. verified — When the member finishes (or the deck is empty), hidden question steps receive an automatic system skip so the profile records that those steps were not shown.
Attribute-based rules Compares profile attributes and saved questionnaire answers. Compares profile attributes only at open time. Works when the attribute is already on the profile before the slide flow starts.
Question-based rules (“show step 5 only if they answered Yes on step 2”) verified — Supported: the chat pipeline passes earlier answers from this questionnaire when evaluating rules. Unreliable — The slide deck does not pass in-flow answers into the rule check at open time. Use attribute-based rules, or prefer a chat-style questionnaire for answer-dependent branching.
Numeric operators (Bigger, Smaller, Between, String contains) Not supported on the server gate—rules using these operators always fail (step hidden for everyone). See dropdown trap. May work for attribute-based rows only—the slide app evaluates a wider operator set on the device. Still test on staging; do not assume parity with Singles Advanced Search search.

Operator summary by questionnaire type

Operator familyChat questionnairesSlide questionnaires (attribute rows)
Contains / In, Equals, Not equals, Not in, Is empty, Is not emptyYesYes
Date after / Date before, Count bigger / Count smallerYesYes
Bigger / Smaller / Between / String containsNo (always hidden)May work on device—test before production
Question-based rows (compare another step’s answer)YesAvoid—use chat type or attribute rules

Practical guidance: Use chat-style types when you need follow-up steps that depend on answers given minutes earlier in the same flow. Use slides when branching depends only on data already on the member’s profile (for example city or approval status). After changing pre-validation on a live slide questionnaire, ask a test member to close and reopen the flow—mid-session edits to rules or earlier answers will not reshuffle slides until the next open.

Related: Publish and stages · Content step types

Questionnaire dropdown trap

On questionnaire and content steps, the Condition list shows every operator name—even ones the server does not evaluate for pre-validation.

What happens if you pick an unsupported operator: The rule always fails for every member. The step is treated as hidden or skipped, as if nobody qualified. There is no error message in Admin or in the member app.

Safe operators on questionnaire steps: Contains / In, Equals, Not equals, Not in, Is empty, Is not empty, Date after, Date before, Count bigger, Count smaller.

Avoid on chat-style questionnaire steps: Bigger, Smaller, Between, String contains—they work in Singles Advanced Search search but not in the Lora server gate, communications, or automated group attach.

Slide questionnaires: Attribute-based rows on On Boarding Slides may evaluate numeric operators on the device—see Slide vs chat. Chat types and all non-questionnaire uses still treat those operators as always-fail.

If you need a numeric band (for example height or age), use Date after / Date before on a birth-date field, split the flow with choice-based branches, or filter members with Singles Advanced Search before a manual campaign—not numeric greater-than on a chat-style step.

Full operator matrix: which operators work where · filter conditions reference

Which operators work where

The condition dropdown looks the same in many places, but not every operator is evaluated in every feature.

Operator familySingles Advanced Search searchPre-validation (groups, comms, questionnaires)
Contains / In, Equals, Not equals, Not in Yes Yes — primary operators for choice and text answers.
Is empty / Is not empty Yes Yes
Date after / Date before Yes Yes — supports fixed dates and relative “days ago” style values when your brand uses them.
Count bigger / Count smaller Yes Yes — for multi-value answers (how many values are stored).
Bigger / Smaller / Between (numeric) Yes Not supported in pre-validation gates today. Rules using these operators always fail (step hidden for everyone). Use date operators on birth-date fields or choice operators instead.
String contains Yes Not supported in pre-validation gates today. Always fails. Prefer Contains / In on choice keys.

Full operator definitions: Attribute filter conditions.

Derived and special attributes

Some attribute names behave differently from plain questionnaire answers — the same rules apply in pre-validation, communications, groups, and Singles Advanced Search search.

Attribute / conceptWhat it comparesOperator tips
Birth month / date of birth (often birthmonth) Date stored on the profile; may be derived when a sensitive birth-date field syncs from identity providers. Use Date after / Date before for age bands. Avoid numeric Bigger/Smaller on questionnaire steps — see dropdown trap.
Height Numeric value (units depend on brand settings). Works in Singles Advanced Search search with numeric operators. On questionnaire pre-validation gates, numeric operators always fail — use choice-based branches or search first.
Search Also (on an attribute) When configured on an attribute, a single rule row searches that attribute or any linked attribute names in the comma-separated list. Useful for “any of these seminary answers” without duplicating rows. Documented in depth on filter conditions reference.
External info / tag keys Tag-rule outputs and imported values stored outside standard bio/pref tables. Pick the external attribute name from the same picker as other profile fields.

Profile settings in rules

Some brands expose internal profile settings as filterable attribute names.

When you pick a name that matches a key in the member’s profile settings (notification toggles, feature flags, and similar), pre-validation reads the live setting value at evaluation time — the same way Singles Advanced Search search does.

  • Settings are not copied into questionnaire answers — they stay on the profile settings record.
  • If a setting key is missing, the row is treated as empty for Is empty / Is not empty checks.
  • Exact names in your picker depend on brand configuration — confirm on staging before production comms depend on a setting row.

See also: filter conditions — profile settings keys.

Introduction and shidduch views

Pre-validation on attributes can hide rows from matchmaker-facing introduction screens.

On view introduction and matchmaker shidduch attribute tables, each attribute may carry its own pre-validation rules. When rules fail for a party, that attribute row is hidden from the matchmaker view — the underlying answer is not deleted.

Only attributes with Public or SMEAndMe visibility are eligible for shidduch display; other policies are filtered out before pre-validation runs.

When your brand enables the bypass matchmaker pre-validation app feature, matchmaker views may show eligible attributes without evaluating per-attribute pre-validation — confirm with your brand lead before relying on hidden sensitive fields in production.

Configure per-attribute rules on Attributes → open attribute → Pre-Validation section.

Pre-validation on communications

Narrow who receives a template when the trigger event fires.

On each communication row, open Pre-Validation in the header or audience section. Rules run per member at send time—after the trigger matches but before any channel delivers.

  • Rules pass — Active channels (push, email, SMS, WhatsApp, chat sequence, etc.) send as configured.
  • Rules fail — That member is skipped for this template only. No error is shown to the member; they simply do not receive this comm.
  • Empty rule groups — Treated as no gate; the comm is not blocked.

Operator reminder: Use only supported operators (see which operators work where). Numeric Bigger/Smaller/Between and String contains always fail—every member would be skipped.

One-time sends: Pre-validation still applies when you use Send now or Send by profile IDs—profiles that fail rules are filtered out silently.

Trigger timing and parameters: Communication trigger events.

Pre-validation on groups

Who may be attached automatically—not who managers add manually.

When pre-validation is set on a Groups definition:

PathPre-validation applied?Effect when rules fail
Automated attach (system jobs, info-screen Group next events, some signup flows) Yes Profile is not added. Attached attributes and default profile status on the group do not run.
Manual attach from Admin (Add member to group) No Manager can add anyone regardless of rules. Attached attributes still merge onto the profile.

Use groups pre-validation when you want segmentation without ops hand-adding members. Use Singles Advanced Search search when you need a one-off list—search does not attach groups.

Group attach side effects: Groups guide.

Where it appears

Area in AdminWhat pre-validation controls
Groups When the system attaches someone to a group automatically (not when a manager adds them manually). Failed rules skip the attach.
Communications Whether a member receives email, push, chat, or in-app content for that communication. Failed rules skip the send for that person.
Questionnaires (questions & content steps) Whether a follow-up question or content item is shown in the member’s questionnaire flow, or hidden when they no longer qualify. Configure on the question or batch content editor; see question list for publish.
Profile attributes (Shidduch / sensitive views) Whether an attribute appears on certain introduction or matchmaker views when your brand uses pre-validation on attributes. See Introduction and shidduch views.
Global filters & auto-update profile codes Which profiles match reusable named filters used in content and automation settings.

What happens when rules fail

Effects depend on where the rules live—pre-validation never shows an error popup to the member by itself.

Groups (automated attach)

The person is not added to the group. Attached-attribute rules and default profile status on the group do not run. Manual add from Admin still works even when rules would fail.

Communications

That communication is skipped for the member for that send or event—no email, push, or chat line from that comm. Other communications are unaffected.

Questionnaires

Steps that fail pre-validation are skipped or hidden in the member flow (no error popup). If the member edits an earlier answer, later steps are re-evaluated and may appear or disappear. Saved answers are kept. See questionnaire walkthrough above.

Attributes on introduction views

The attribute row may be hidden from the matchmaker view when rules fail. This is a display gate, not a delete of the underlying answer.

Singles Advanced Search uses the same condition operators for searching people, but search is read-only—it does not attach groups or send messages when rules match.