Reference (partial) — Operator behavior is verified from the profile search service used when you click Execute. Wording below is plain language; edge cases for unusual attribute types may still need brand-specific notes.

AND and OR

When you add more than one filter row, choose how they combine:

  • AND — A person must match every filter row to appear in the results.
  • OR — A person can match any one filter row to appear.

The table’s Status filter and Internal switch apply on top of your attribute filters—they narrow the same result set further.

See also: Singles Advanced Search

Choosing values

  • Choice questions — Pick answers from the list; the system stores answer keys (and may show admin labels in the picker).
  • Autocomplete-style questions — You can type or select display text; searches match how those answers are stored on the profile.
  • Boolean questions — Use the true/false keys shown in the picker, not only “Yes/No” labels.
  • Date questions — Use date pickers when the condition is “before” or “after” a date.
  • Is empty / Is not empty — No value field; the condition only checks whether the attribute has any answer.

Attribute types

Which operators appear depends on how the attribute stores answers.

Answer style Typical operators Common mistakes
Single or multi choice (pick from a list) Contains / In, Equals, Not equals, Not in, Is empty, Is not empty Using “Equals” when you only need “any of these answers”—use Contains / In instead.
Free text or autocomplete lists Contains / In, String contains, Is empty, Is not empty Typing display text that does not match how answers are stored; use the picker when offered.
Numbers (age, counts, scores) Bigger, Smaller, Between, Count bigger, Count smaller Using numeric operators on text fields, or the reverse.
Dates Date bigger (after), Date smaller (before), Is empty, Is not empty Using “Bigger/Smaller” meant for numbers instead of the date operators.
Yes / no (boolean) Equals, Contains / In, Is empty, Is not empty Choosing “Yes/No” labels in the UI that do not match the stored true/false keys.

Derived and linked attributes

Some filters behave differently from a plain profile field.

What you may see What it represents How to filter
Birth month / date of birth (often stored as birthmonth) The member’s birth date or month/year answer from onboarding. The list may sort by this field when you choose age-related column sorting elsewhere in Admin. Use Date after / Date before for age bands (for example “born before 1990-01-01”). Do not use numeric Bigger/Smaller on the date string itself.
Height Stored as a number on the profile (units depend on brand settings). Use Bigger, Smaller, or Between with numeric values.
Search Also (configured on an attribute) When attribute A is set to “search also” on attributes B and C, a single filter row on A matches if any of those linked fields satisfy the condition. You still pick attribute A in the filter row; matching expands automatically. Useful when the same concept is duplicated across related fields.
External Info / tag-rule keys Values written by Tag Rules (event counts, campaign tags). Filter by the tag key name and value like any other attribute. Pre-validation on other screens can read the same tags after a rule runs.
Profile settings keys Some brands expose internal settings (not questionnaire answers) as filterable names in advanced setups. The exact names in your picker depend on brand configuration. Treat like text or choice fields. If a name looks like a toggle or preference rather than a questionnaire answer, confirm with your brand lead before bulk-updating it.

Pre-validation vs search: Numeric Bigger / Smaller / Between and String contains work in Singles Advanced Search search but are not applied in pre-validation gates (questionnaires, communications, automated group attach). Unsupported operators in a pre-validation rule always fail—the step is hidden for every member. See pre-validation — questionnaire dropdown trap and which operators work where.

Condition operators

What you see in the condition dropdown and how it behaves on stored profile answers.

Operator (typical label) What it checks Values you enter Pre-validation gates
Contains / In The profile’s answer includes at least one of the values you list (common for multi-select or “any of these cities”). One or more answers Yes
Equals The answer set matches exactly what you selected (same items; order does not matter). Full set of answers Yes
Not equals The answer is not exactly that full set. Full set to exclude Yes
Not in The answer does not include any of the listed values. One or more values to exclude Yes
Bigger A numeric answer is greater than the number you enter. One number No — use only on Singles Advanced Search search
Smaller A numeric answer is less than the number you enter. One number No
Between A numeric answer falls between two numbers you enter (inclusive). Low and high number No
Date bigger (after) A date answer is after the date you pick. One date Yes
Date smaller (before) A date answer is before the date you pick. One date Yes
String contains Text in the answer contains your substring (not case-sensitive). Text to find No — search only; prefer Contains / In on stored choice keys in pre-validation
Is empty The person has no answer for this attribute (missing or blank). None Yes
Is not empty The person has some answer for this attribute. None Yes
Count bigger The attribute has more than N stored values (multi-value answers). One number (N) Yes
Count smaller The attribute has fewer than N stored values. One number (N) Yes

Pre-validation gates include questionnaires, communications, automated group attach, and attribute visibility on some matchmaker views. If you need numeric greater-than on a questionnaire step, use a date operator on a birth-date field or restructure the rule—see pre-validation — which operators work where.

Worked examples

Common searches on Singles Advanced Search. Attribute names differ by brand—pick the equivalent field from your attribute list.

Find members in two cities (OR)

  1. Add filter row 1: city attribute, Contains / In, value = Chicago.
  2. Add filter row 2: same city attribute, Contains / In, value = Denver.
  3. Set the top-level combiner to OR.
  4. Click Execute. Anyone whose city answer includes Chicago or Denver appears.

Approved members who answered “Yes” on two questions (AND)

  1. Set combiner to AND.
  2. Row 1: questionnaire answer attribute, Equals, value = the stored key for “Yes”.
  3. Row 2: second answer attribute, Equals, value = “Yes”.
  4. Set the table Status filter to your approved status.
  5. Execute — only people matching both answers and that status show up.

Members missing a photo attribute (empty check)

  1. One row: photo-related attribute, Is empty, no value field.
  2. Execute — lists everyone with no answer stored for that attribute.

Members in an age band (date on birth field)

  1. Pick your brand’s date-of-birth or birth-month attribute (often labeled like a birth date on the attribute list).
  2. Row 1: condition Date after, value = start of the band (for example 1985-01-01 for “born after 1984”).
  3. Row 2: condition Date before, value = end of the band (for example 1995-01-01 for “born before 1995”).
  4. Set combiner to AND and click Execute.

Use date operators—not numeric Bigger/Smaller—on date-stored attributes. For pre-validation on questionnaires, numeric greater-than is not supported; use the same date operators there.

Members in an age band (date operators)

  1. Pick your birth-date attribute (often labeled like birth month or date of birth).
  2. Row 1: Date after = 1990-01-01 (born after that date → younger than ~36 in 2026).
  3. Row 2: Date before = 2000-01-01 (born before that date → older than ~26 in 2026).
  4. Set combiner to AND — both rows must match (roughly ages 26–35). Adjust dates for your brand’s definition of an age band.

Tip: Use Date after / Date before on date fields—not numeric Bigger/Smaller on the stored date string.

Height between two numbers

  1. One row: height attribute, Between, low = 160, high = 180 (units match how your brand stores height).
  2. Execute — lists members whose stored height falls in that inclusive range.

This pattern only works on Singles Advanced Search search. Do not copy the same numeric Between row into questionnaire pre-validation—it will not gate steps there.

Approved members only, excluding test accounts

  1. Build your attribute filter rows as usual.
  2. Set the table Status filter to your approved (or active) status.
  3. Turn off Internal so internal/test profiles are excluded from the result set.
  4. Execute — status and internal filters apply on top of your attribute rows.

Tag from a rule (external info)

  1. After a Tag Rules run, pick the rule’s key name in the attribute picker (same spelling as the rule key).
  2. Use Contains / In or Bigger depending on whether the tag stores text counts or numbers.
  3. This finds everyone the rule tagged—not people who merely performed the underlying event before the rule executed.

Before bulk update: Run the same filters with Execute and walk a few pages. Bulk Update Attributes applies the identical filter set but writes new attribute values—mistakes affect every matching page.

Bulk update behavior

How Bulk Update Attributes uses the same operators as search.

Bulk update reuses your filter rows exactly as Execute does—same attribute, condition, values, AND/OR, table status filter, and internal toggle. The server pages through matches 200 profiles at a time until no rows remain.

OptionDefaultPlain-language effect
Override current values Off Only profiles with an empty value for the chosen attribute are updated. Existing answers are left unchanged.
Override current values On Every matching profile receives the new value, replacing any previous answer.

Does not: trigger profile re-approval, send communications, or refresh the matcher immediately. For tag-rule keys stored as external info, confirm you are writing the attribute name members and rules actually read.

See the feature page: Singles Advanced Search — bulk update and bulk migrate.

Limits and tips

  • Execute loads results in pages of 200 members at a time (the UI default). The server accepts up to 500 per page if a custom integration requests it—ordinary Admin browsing uses 200.
  • Bulk Update Attributes walks the same filter in chunks of 200 until no more profiles match, then updates each person—large searches can take several minutes.
  • You can bookmark or share a search; filter rows are kept in the page address.
  • Sort order on the results table follows the column you choose (for example relevance, or birth date when that derived field is in play).
  • Bulk Update Attributes uses the same filters as Execute but changes data—see the feature page before running it.