Start with the correct field type
Text
Use text conditions for titles, categories, tags, authors, and other words. Common comparisons include contains, excludes, and exact match. Normalization settings can reduce differences caused by case or spacing.
Number and price
Use numeric conditions for prices, ratings, counts, measurements, or percentages. You can compare greater than, less than, equal values, or ranges. Confirm that the field contains one consistent numeric value rather than several unrelated numbers.
Date
Use date conditions for published dates, deadlines, or updated times when the visible format can be parsed safely. Depending on the editor, compare before, after, between, or within a recent number of days.
Understand AND and OR at both levels
Conditions can be combined inside one field, and separate field groups can have their own relationship. Read the rule as a sentence before applying it.
AND: every requirement must match
Use AND when you want cards whose title contains “wireless” and whose price is below 100. Adding more AND conditions usually narrows the result.
OR: at least one requirement may match
Use OR when a category may be “Design” or “Tools,” or when either of two tags is acceptable. Adding OR conditions usually broadens the result.
Practical filter examples
- Product shortlist: title contains a keyword AND price is between your minimum and maximum.
- Recent articles: author is one of two names OR tag matches one of several topics, AND date is within the recent period.
- Directory cleanup: hide entries whose status exactly matches an unwanted label.
- High-rated items: rating is greater than or equal to your threshold, then sort descending if the container can be changed safely.
Build one part at a time. Apply the first condition, confirm the result, then add the next field or comparison. This makes it easier to identify which part changed the result.
Handle missing and unreadable values explicitly
A card may use a different layout, omit the selected field, or show a value that cannot be parsed as the chosen type. Decide whether those cards should remain visible or be excluded.
An orange outline can indicate a field that was missing or unreadable while the policy is set to include that card. It does not necessarily mean the condition failed. Reselect the field, correct the data type, or add a separate card type for a recurring alternate structure.