# Ranking Rules

#### **Summary**

Using ranking rules, you can change the order of search and category results as you wish. This procedure results in a soft sorting of the results and various business rules can be mapped with it.

If, for example, your target group can be described as bargain hunters, it is worth using the ranking to push discounted products, i.e. place them higher up in the search results.\
If internal costs for returns cause you a headache, products with a low return rate can be pushed. Rankings can work permanently or in a specific period of time, e.g. B. tied to an action.

Ranking rules are intended as a global approach (concerning the entire product range or all search results); for individual, targeted interventions we recommend using [Campaigns](/docs/discovery/campaigns.md).

#### **General Settings**

When checking the ranking, upper and lower case does not matter.

Ranking rules are part of the basic settings

![](/files/81UWeG8NKxibkQp8W1eP)

When you open the ranking view, you will first see an overview of all the rules created:

![](/files/TYpZb42Rm4U9C1Skc5f7)

|                                                                                                                                                             |                                                                                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|                                                                                                                                                  Indication | Function                                                                                                                                                             |
| [![](/files/gRdFEVa6kAhORTJLBeTz)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/d873dd13-0276-47ae-9ba4-9ff67340c344.png) | Indicates that the respective entry is currently locked by a user or blocked by an open transaction                                                                  |
| [![](/files/FmAQvIZjUMPiv64DDVI8)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/f5c1996e-0cea-4155-8da6-adf92ddc54d9.png) | Select multiple ranking rules                                                                                                                                        |
| [![](/files/aBFHIyOew94xie29XEfJ)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/9de7cd49-a627-4195-98dd-6b0fe78b3907.png) | Edit existing ranking rules                                                                                                                                          |
| [![](/files/dgXP26Hz0JBHfgUSMrCC)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/9cb3faa9-b68c-4bba-b408-06df70e7f0c5.png) | Shows whether the ranking rule is active or inactive                                                                                                                 |
| [![](/files/s1hvKpPcA910KKUCsJAp)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/66fc0879-fede-412f-895b-60f339549dc0.png) | Show and hide entries that were deleted within a transaction. Only works in an active transaction and only applies to the deletion of entries within the transaction |
|                                                                                                                            ![](/files/KLqq0AKqKbgblvxD5IuT) | The search allows you to quickly find entries in order to edit them, for example                                                                                     |
| [![](/files/UpVZSkKuAVoEuyoqkzCO)](https://github.com/FACT-Finder/documentation/blob/main/ng/documentation/images/392de20b-9e12-4388-bc20-d04186d86187.png) | By clicking on the arrow, the campaigns can be sorted alphabetically in ascending or descending order.                                                               |

#### **Creating new Rule**

If you want to create a new rule, click on the **NEW RANKING RULE** button at the top right of the overview page.

***

> **Triggers and effects**

**In the Triggers and adjustments** tab you can specify how the rule should work:

![](/files/CuObNqsPKj3zJHUyuOdz)

* Detailed information about how **conditions** work can be found on the sub-page [Available condition types](/docs/discovery/ranking-rules/available-condition-types.md) and under [Combine conditions](#combine-conditions).
* You can use the **DELETE RANKING RULE** button to remove the open rule.

***

> **Scope**

Here you can decide which areas the ranking rule applies to - search, navigation, suggestion or a combination of the three.

![](/files/5sKoDb6X31bQiAkXn18o)

By default, search and navigation ranking rules are configured.

To use a ranking rule for a suggest type , the type must be linked to all fields that are set for the rule under 'Triggers and Effects'. You can add the fields on the [Suggest Import page](/docs/import/selecting-suggest-product-and-search-data.md).

***

> **Name and period**

**I**n the **Name and Period** tab you can configure general settings for your ranking rule:

![](/files/yRggFSpJj1OJVDKT7JLi)

* In the **Rule name** field, you specify the name that is displayed in the overview. Use clear names so that other users know immediately what the rule does.
* The **validity period** determines the period in which the rule applies. It is determined by the start and end dates. If you do not make any changes to it, the rule applies immediately and permanently as there is no end date set.
* You can activate or deactivate the rule by checking **Active.**

#### **Combine conditions**

You have the option to combine different conditions.

There are basically two ways to evaluate this: with **AND** or with **OR**. **AND** means that all conditions must be met for the rule to apply. **OR** means that only one condition must be met for the rule to apply.

In practice, this means that for **OR**-valued conditions, after the first condition is fulfilled, the subsequent ones are no longer checked!

The conditions in FactFinder are color-coded. Conditions colored green are always **OR**-valued, while conditions colored red are **AND**-valued.

***

> **Adjustment management**

You can add a new effect using the **plus symbol** under an effect. These are OR-valued, so the first applicable adjustment is applied.

![](/files/a9C6HPV3omlUU3684BMJ)

***

> **Adding Conditions**

If your mouse cursor is over the condition, a button will appear on the right that you can use to add another condition for the effect:

![](/files/xssQl9RyHIrRY5DXDAKJ)

These conditions are **AND**-valued, so they must all be met for an effect to be applied:

![](/files/QTXwrEmXdIOe7RiiEwIw)

Additional **AND**-weighted conditions can be added using the red **plus symbol :**

![](/files/5vm1DqCsIhRfkNio8EO1)

Instead, you can also add another **OR**-weighted condition using the **Alternative Condition** button :

![](/files/OHkXcNqU7LmhCn8HxjMy)

In this way, very complex conditional constructs can be created that achieve the effects you want. Below you will find an example of what this might look like in practice.

> **Example: category-specific brand ranking**

You want to build category-specific brand rankings. In the backpacks category, you want to push Adidas products the most (3%), The North Face products the second most (2%), and Deuter products the third most (1%). All other manufacturers or brands should be treated normally. The ranking created would then look like this:

![](/files/34oDsT2Aq20JWyt6zkJL)

#### **Live Ranking**

You can also apply ranking rules to **CSI** or **Geo** fields. Since the contents of these fields are customer-specific, the ranking is not calculated in advance (during import), but rather at the moment of the request (live).

Depending on the amount of data and other factors, live rankings have an impact on performance, i.e. on loading times. Live rankings should definitely be tested or discussed with the FactFinder team before being transferred to a productive system.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fact-finder.com/docs/discovery/ranking-rules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
