> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/product-finders/matching-rules.md).
# Matching Rules
Choose which products your Product Finder shows, in which order, and the benefits that tell visitors why a product fits, with Matching Rules on the Matching tab.
The **Matching** tab is where you choose your Finder's products. Its **Matching Rules** decide which products the Finder shows, in which order, and the benefits that tell visitors why a product fits them.
Matching Rules replace the filters on answers in the Flow tab, and the **Results Filtering Rules**, **Product Benefits** and **Product Ranking** settings in **Setup → Data**.
The Matching tab has two sub-tabs:
| Sub-tab | Its rules apply |
| ----------- | ---------------------------------------------- |
| **Answers** | When a visitor picks that answer |
| **Finder** | To every result, whatever the visitor answered |
Click **Save** to save the rules on both sub-tabs together.
{% hint style="info" %}
The first time you open the Matching tab, a short tour shows you around. To take it again, click the **?** icon next to **Save**.
{% endhint %}
## How a Matching Rule works
Each rule reads as a sentence:
* **When** - The condition a product must match, for example *Waterproof \[equal to] Yes*.
* **Then** - What happens to the products that match.
* **And say** - An optional benefit shown on matching products in the results, for example "Keeps you dry in heavy rain".
Beside each rule, a chart shows how many of the Finder's products the rule affects, and **Visitor sees** previews what a matching product shows.
## Add rules to an answer
{% stepper %}
{% step %}
#### Pick a question and an answer
Open **Matching → Answers**, then select a question and one of its answers. Answers that already have Matching Rules are checked, with an icon for each thing their rules do.
{% endstep %}
{% step %}
#### Add a Matching Rule
Click **+ Matching Rule**. New rules are added to the top of the list.
{% endstep %}
{% step %}
#### Set the condition
Under **When**, set the condition for the products the rule applies to.
{% endstep %}
{% step %}
#### Choose what happens
Under **Then**, choose one:
| Choice | What it does |
| ---------------------------- | ------------------------------------------------------------------------ |
| **Only show a benefit** | The results stay as they are. Matching products show the rule's benefit. |
| **Only show these products** | Products that don't match are hidden when this answer is picked. |
| **Move these up or down** | Matching products gain or lose points. All products stay visible. |
For **Move these up or down**, choose how many points matching products get:
* **Mismatch** (-10), **Good match** (+5) or **Perfect match** (+10).
* **Custom points** - Enter any number. A negative number moves products down.
* **Points from a property** - Multiply a numeric product property by a number of points, so products with higher values score more. The property needs a minimum and maximum in its validation range.
For **Only show these products**, select **Also order them by a property** to rank the remaining products by a numeric property.
{% endstep %}
{% step %}
#### Add a benefit (optional)
Under **And say**, enter the benefit text. Click the thumbs-up icon to show it as a disadvantage instead.
Use **#** to set where the benefit is listed on a product. Lower numbers come first, and benefits without a number come after them.
{% endstep %}
{% step %}
#### Save
Click **Save**.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
A rule that shows no benefit and neither hides nor moves products does nothing. The rule says so until you choose what it does.
{% endhint %}
### Question Weight
Each question has a **Question Weight**: how much its answers' rules count towards a product's **Match score**, compared with the other questions. A weight of 2 makes every Matching Rule of its answers count double, 0.5 makes them count half, and 0 leaves the question out of the score.
You'll find it above the answer's rules, next to the question and answer name.
## Add rules for the whole Finder
Open **Matching → Finder** to add rules that apply to every result, whatever the visitor answered. Click **+ Matching Rule**, set the condition under **When**, then choose under **Then**:
| Choice | What it does |
| ---------------------------- | -------------------------------------------------------------------------------------------- |
| **Only show a benefit** | The results stay as they are. Matching products show the rule's benefit. |
| **Only show these products** | Products that don't match are never shown. The rule shows how many products this leaves out. |
| **Boost or bury** | Moves matching products up (**Boost**) or down (**Bury**) in the results. |
A Boost or Bury is a percentage of the best score a product can get from the visitor's answers, from 0% to 200%. Select **Scale the push by a property** to scale it by a numeric product property.
A Boost or Bury changes only the order of the results. Products keep the same Match score, and the rule shows no benefit.
{% hint style="info" %}
If your Finder still ranks by absolute weights from the old Product Ranking setting, the Finder sub-tab shows a note. Those weights keep working.
{% endhint %}
## Check the results
Open the **Products** tab and answer the questions to see the products your rules return. The **Match** column shows each product's Match score. Hover the info icon next to it to see the benefits the product matched and what each rule added. See [Product Quality Assurance](/how-to-guides/product-finders/product-quality-assurance.md).
## Frequently asked questions
Where did the answer filters and the Setup data rules go?
They are Matching Rules now. An answer's existing filters and benefits appear as Matching Rules on that answer in **Matching → Answers**. The answer settings in the Flow tab and **Setup → Data** both show a banner. Click **Open Matching** to go straight to the rules.
What's the difference between Only show these products and Move these up or down?
**Only show these products** hides every product that doesn't match. **Move these up or down** keeps every product and changes their order. Use it when a product that doesn't match can still be a good result.
Why doesn't a Boost or Bury show a benefit?
A Boost or Bury changes only the order of the results, not how well a product matches the visitor's answers, so there is no benefit to explain.
Do I need to publish after changing Matching Rules?
Yes. Saving updates your draft. Publish a new version in the Versions tab to make the changes live. See [Publishing & Versions](/how-to-guides/product-finders/publishing-and-versions.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.crobox.com/how-to-guides/product-finders/matching-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.