Filter catalog

Pour :Administrateur

View of the 'search filters' page

This page lists all available filters in the advanced search (/app/contact/search), their format, and their precise behavior. For an overview of the tool, see Advanced search.

The filters are organized in nine collapsible sections. Each filter has a technical type that determines the displayed control: boolean, single selector, multiple selector, date range, number range, free field, keyword list to add (multi-tags).

Section 1 — Identity

Filter	Type	Use case
Gender	Boolean (Male / Female)	Target men for a minyan, women for a dedicated workshop
Name starts with	Text (prefix)	E.g.: COH to find Cohen, Cohenel, Cohenov…
First name contains	Keyword list	Type several first names (Sarah, Léa, Rachel…) with Include or Exclude mode
Date of birth	Date range	E.g.: born between 01/01/1950 and 31/12/1970
Age	Number range	E.g.: between 18 and 25 years old (based on date of birth)

★

Name: prefix, not contains

The Name starts with filter matches only the beginning of the name. It is fast (indexed). To search for a name containing a pattern in the middle, use the general text field at the top of the page instead.

Section 2 — Categories & relations

Filter	Type	Use case
Categories	Multiple selection (Include / Exclude / Equal)	Filter by applied tags (e.g.: #FIDELE, #PAIEMENT, Bar_Mitzvah_2026)
Number of categories	Number range	Detect under-classified contacts (0–1) or over-classified (>10)
Family relationship type present	Multiple selection (Include / Exclude / Equal)	Contacts with at least one Spouse, Parent, Child, Sibling, Grandparent, Grandchild, Ex-spouse, Brother/Sister-in-law, Cousin, Friend link
Number of registered parents	Number range	Find children without registered parents, children of large families, etc.
Number of registered children	Number range	Large families or parents without registered children

ℹ

Equal = exactly these categories

The Equal mode on Categories is strict: it only returns contacts who have exactly the chosen combination (no more, no less). Useful to audit a precise segment; avoid for broad segmentations.

Section 3 — Contact details: search & presence

Filter	Type	Use case
Email contains	Keyword list (Include / Exclude)	@gmail.com, @yahoo.fr to target by provider
Phone contains	Keyword list (Include / Exclude)	0140 for Paris landlines, +33 6 for French mobiles
Has an email	Boolean	Deliverability audit, identify contacts to recontact to retrieve an email
Has a phone	Boolean	Prepare an SMS campaign — exclude contacts without phone
Has an address	Boolean	Prepare a paper mailing
Has a date of birth	Boolean	Filter for the birthday reminders module
Number of emails	Number range	Detect contacts with primary email + secondary (>1)
Number of phones	Number range	Same for phones (primary + secondary)
Number of addresses	Number range	Detect multi-address contacts (residence + office, for example)

⚠

Primary email ≠ all emails

The Email contains filter matches any of the contact's emails (primary or secondary). On the other hand, Number of emails counts the total (primary + secondary). See Tricky points to clearly distinguish primary email and secondary emails.

Section 4 — Geography

Filter	Type	Use case
Country	Keyword list (Include / Exclude)	Target contacts from Israel, Spain, etc.
City	Keyword list (Include / Exclude)	Target Paris, Marseille, Lyon…
Postal code starts with	Keyword list (Include / Exclude)	75 for Paris, 13 for Bouches-du-Rhône, 69 for Rhône
Address contains	Free text	E.g.: Rue de la République
Phone area code	Multiple selection (Include / Exclude)	+33 (France), +972 (Israel), +1 (USA/Canada)…

★

Postal code and area code: think prefix

Postal code matches as a prefix: 75 matches 75001, 75002, etc. Phone area code matches at the beginning of the full number. Combine them for precise geographic targeting.

Section 5 — Contact statuses

Filter	Type	Use case
New contact	Boolean	List of recently created contacts not yet opened ("new" badge in the profile)
Deceased	Boolean	Filter hazkara reminders, exclude from campaigns
Archived	Boolean	By default, archived contacts are hidden. Activate this filter to see them

⚠

Archived ≠ Deleted

An archived contact is kept but hidden from current lists. A deleted contact is in soft delete (trash). See Tricky points to understand the three states (new / archived / deleted).

Section 6 — Documents & commitments

Filter	Type	Use case
Has documents	Boolean	Contacts with attachments (ID papers, supporting documents, scans)
Number of documents	Number range	Detect contacts with complete dossier (>3 docs) or empty
Has custom fields	Boolean	Contacts who have at least one value in a tailor-made field
Chlihouts present (level > 0)	Multiple selection (Include / Exclude / Equal)	Contacts registered in a ritual framework: Shabbat, Kashrut, Taharat Hamishpaha, Jewish School

Section 7 — System activity

Filter	Type	Use case
Contact creation date	Date range	Audit contacts added this month, this quarter
Last modification date	Date range	Contacts untouched for 2 years (archiving candidates), recently modified contacts

Section 8 — Custom fields (dynamic)

This section is generated dynamically from the custom fields you have created for your organization. The proposed control depends on the field type:

Field type	Control	Behavior
Text	Keyword list (Include / Exclude / Equal) + autocomplete	Suggests values already entered by other contacts
Number	Number range	Filter by min, max, or both
Yes / No	Boolean	Contacts having the Yes or No value
Date or Date & Time	Date range	Filter on a period

Example: if you created a text field car with the values Renault, Peugeot, Toyota… the search offers an autocompleted list with these values. Equal mode on Renault, Peugeot = contacts who have exactly these two values (rare case because most text fields are unique values — prefer Include).

ℹ

Custom fields: no uniqueness

Two contacts can have the same value in the same custom field. This is deliberate, but it explains why an Equal filter on a very common field returns many results. See Tricky points.

Section 9 — Financial activity

This is the most powerful section for donor segmentation. All these filters rely on completed payments (COMPLETED statuses).

Filter	Type	Use case
Analysis period (payments)	Date range	Limit the total calculation to a period (e.g.: 2025 donations only)
Total paid (€)	Number range	Donors > €500, micro-donors < €50, etc.
Number of payments	Number range	Regular donors (>5 payments), single donors (1)
Average amount per payment (€)	Number range	High-capacity donors (average > €200)
Average payments per year	Number range	Loyal donors (>3/year) vs occasional
Last payment date	Date range	Donors inactive for > 12 months (wake-up campaign)
First payment date	Date range	New donors vs historical
Payment methods used	Multiple selection	Bank cards, direct debits, checks, transfers, cash, in kind donations
Has an active subscription	Boolean	Current recurring donors
Has an ongoing pledge	Boolean	Donors committed to an unsettled pledge
Total amount of pledges due (€)	Number range	Pledges not yet paid per contact
Number of active pledges	Number range	Donors with multiple ongoing commitments

★

Financial activity: think about setting the period

If you combine Total paid with an Analysis period, the total is calculated only on this period. Without a period, the total accumulates all payments since contact creation. This is rarely what you want for an annual report.

Useful combinations

Here are some common recipes:

Loyal donors to recontact

• Financial activity: Number of payments ≥ 3, Last payment date between 01/01/2024 and 31/12/2024.
• Contact details: Has an email = Yes.
• Statuses: Archived = No.

→ List of contacts who donated regularly in 2024 but can be recontacted by email.

Large families for a children's event

• Categories & relations: Number of registered children ≥ 3.
• Geography: City = Paris.
• Contact details: Has a phone = Yes.

Contacts to archive

• System activity: Last modification date before 01/01/2023.
• Financial activity: Number of payments = 0.
• Contact details: Has an email = No, Has a phone = No.

→ Candidates for bulk archiving.

Men for a local minyan

• Identity: Gender = Male.
• Geography: Postal code starts with 75001.

Save for reuse

Once a useful filter combination is built, save it rather than rebuilding it each time. See Saved searches.