Introduction to ranking rules
This guide will provide you with the necessary information to use ranking rules in the Merchandising Studio. This is not a technical guide.
Ranking rules are strategies developed at the category (and sub-category) level, which govern the relative sequence (ordering and sorting) of products returned to a shopper, influencing purchase decisions and meeting your eCommerce strategy. Ranking rules, therefore, underpin search, category or product lister pages.
Why are ranking rules important to you?
- Allows products to be shown with relevance to key metrics such as stock, brand, or season.
- Allows the exploitation of current trends and analytical data to promote popular items and increase overall conversion rates.
- Helps you promote the correct items without the need for manual merchandising.
Overview
Key information about this feature:
| Purpose of this feature | Controls how Fredhopper returns items on your lister page |
| Menu name in Merchandising Studio | Ranking |
| Sub-menu name in Merchandising Studio | Ranking rules |
A ranking rule consists of triggers and sorting actions based on attributes or ranking attributes.
Ranking rules are linear. When a ranking rule consists of several sorting actions, Fredhopper applies them one after the other. Extra attributes influence the ranking rule when several items have equal values for the same attribute.
When to use ranking rules
- Create general guidelines about the top and the bottom results from queries.
- Promote or demote items with the highest or the lowest values for a chosen attribute.
- Filter items that meet a certain condition and push them to the top or the bottom results from queries.
Scopes
When you create a ranking rule you will need to choose a scope. A scope is a mapping of your organisational structure in your Merchandising Studio and allows you to form 'areas of effect' for your rule.
Scopes can be as vast (site-wide) or as granular (the dresses page of the mobile Spanish site) as possible. From the overview page of your ranking rules page, multiple scopes can be selected to view all related rules in those scopes; this is the default option.
A ranking rule is related to one scope only. Ranking rules can be copied to other scopes once they are created.
Triggers
Triggers define where, when or under what circumstances an action occurs in your site. An action is something a customer does when looking for products or items in your catalogue. This could be via a search, or navigating to a product listing page. Therefore, you add ranking rules that match your strategy for product listing pages.
- Triggers are 'conjunctive', used when a trigger AND an action have been configured in a ranking rule, i.e. When a user reaches landing page A AND show them X products
- All trigger conditions must be satisfied to result in the action
Triggers are selected from the dropdown (this list is an example):
Common triggers
Option |
Description |
|---|---|
| <any custom trigger> | The rule triggers when it meets the specified custom conditions. |
| Keyword | The rule triggers when the shopper runs a search for a specific term. |
| Navigation steps | The rule triggers when the shopper makes a specific or a relative number of navigation steps. |
| Number of results | The rule triggers when a query produces a specific or relative number of results. |
| Query type | The rule triggers for a specific type of query. |
| Result type | The rule triggers for lister pages of specific types. |
| User/Catalogue location | The rule triggers for a specific page or navigation path. |
| Value distribution | The rule triggers when it meets the conditions for the specified attribute values. |
| Brand | The rule triggers when a Brand name is or is contained in the navigation or search. |
| Device type | The rule triggers when a specified device type is being used by the shopper. |
When using a user/catalogue location, you must also choose one of the following:
Trigger |
Example |
Will be triggered when... |
Won't be triggered if |
Graphical representation |
|---|---|---|---|---|
Contains* |
User location contains Fragrance | A customer has reached a location that contains 'Fragrance'. However, it will also continue to show/be triggered after the customer selects additional facets in the location. To illustrate: if one customer navigates Beauty > DKNY > Fragrance and another customer navigates Beauty > Fragrance > DKNY, the campaign or ranking will be triggered in both cases because both paths contain the location Fragrance. | If the location does not contain the location specified in the trigger*** | |
Ends with* |
User location ends with Fragrance | A customer reaches the location 'Fragrance'. To illustrate: if one customer navigates Beauty > DKNY > Fragrance and another customer navigates DKNY > Beauty > Fragrance, the campaign or ranking will be triggered in both cases because both paths end in the location Fragrance. | Until a customer gets to the location Fragrance and it will also not be shown/triggered if the customer selects additional facets in the location | |
Equals |
User location equals Women > Shoes > Ugg | The path a customer followed to get to the Ugg facet is exactly equal to the specified user location, in this case, Women > Shoes > Ugg. | If a customer gets to the Ugg facet by navigating Shoes > Women > Ugg or Ugg > Women > Shoes or any way that is not exactly equal to the path defined in the trigger | |
Starts with |
User location starts with Women > Shoes > Ugg | A customer has followed the exact path defined in the trigger. It will also continue to be shown/triggered after the customer selects additional facets in that location. To illustrate: the campaign or ranking triggered for 'User location starts with Women > Shoes > Ugg' will also be triggered for 'User location starts with Women > Shoes > Ugg > Size EU 41/UK 7' and 'User location starts with Women > Shoes > Ugg > Size EU 41/UK 7 > £50 or more'. | If a customer gets to the Ugg facet by navigating in any way that is not equal to that defined in the trigger |
*CAUTION
It is important to note that the 'contains' and 'ends with' triggers refer to locations and not the term/word expressed in the trigger. If a trigger is not behaving as you would expect, it is most likely the case that your store category tree includes two or more locations with the same name (see 'Different user locations with the same name' below). Or that you are not taking the behaviour of the type of facets in use into account (see 'Facets' below). Other triggers, such as the Dominant Category, Dominant Brand, Dominant <attribute> and Current Item, can also trigger campaigns or rankings in specific locations (that may not be expected) but the focus of this article is catalogue/user location triggers.
Different user locations with the same name
In the example of 'User location contains Watches', 'Watches' is the customer-facing name for that category’s ID. In this example, there are two different categories with the same name in the catalogue:
The two categories named 'Watches' have different category IDs. So, in effect, our locations look like this:
Even though you may expect any path that contains the word 'Watches' to trigger the ranking or campaign in question, the category ID of the selection and not the name should be contained in the path for it to show.
In the case of a 'User location contains Watches' trigger, it will not apply to both Home > Men > Watches and Home > Women > Watches as these refer to different locations; in effect Home > Men > ID:18684 and Home > Women > ID:17780.
What do these user locations look like in the Merchandising Studio?
When selecting the user location for Home > Women > Watches and you want to create a 'contains' trigger, navigate to the location you want to be contained in the trigger.
This results in a 'User location contains Watches' trigger: Home > Women > Watches, and you want to create a 'contains' trigger.
However, this does not apply to both Men > Watches and Women > Watches, as when the setting the location, we used Women > Watches circled in red below:
This location contained in the trigger is, therefore, Women + Watches = ID: 17780.
Following the same process for user location Home > Men > Watches, the location contained in the trigger is Men + Watches = ID: 18546.
The resulting triggers look the same in the Merchandising Studio because they have the same name, but refer to different locations.
Points to remember:
- User locations are not static but are dependent on the path a customer follows.
- Different customer journeys can strongly indicate different purchasing interests and intentions.
- The same set of products can be merchandised differently for different customers, following different paths to get to those products and displaying different intentions.
- User location triggers can apply to both campaigns and rankings.
- There are four different types of user location triggers:
- Equals
- Starts with
- Contains
- Ends with
- User locations comprise of the category and/or ID and not the term used.
- Categories are hierarchical (comprising of parents and children).
Action
This is where you rank by an attribute (as per your data file) or ranking attribute (rc). If applicable, you can choose to sort these by ascending or descending order, for example, a review rating can be sorted, but a device type cannot.
You can add more than one action by clicking on Add Sort Field.
Select an attribute or a ranking cocktail from the Rank by dropdown menu, and configure its sorting.
| Option | Description |
|
Default Descending order. Sorts from Highest to lowest value |
|
| Ascending order. Sorts from lowest to the highest value. |
Important
When using a ranking attribute, check its pushing setting and the normalisation of its attributes. Make sure that they cause the ranking cocktail to behave as expected. For more information, see 'Getting Started with ranking attributes'.
Standard ranking rules
Set up ready for you to publish or edit within your Merchandising Studio:
- Black Friday Sale
- Trending & Popular Strategy
- Sale Strategy
- New In Strategy
- Highest Converting Strategy
- Search Strategy
Scenarios
In this first scenario, the trigger is that when a shopper lands on Mens > Jeans > Regular & Classic fit product landing page, the product's action will be to sort firstly by Review Rating (high to low) then by Price (high to low):
This second scenario is that we want to apply the ranking attribute (cocktail); rc_newin_strategy to Women's Accessories across our FR Store (site):
Best practices
To ensure you are using ranking rules efficiently, you might want to explore and apply these recommendations.
Maintain at least two default ranking rules
Ranking rules determine the sorting order of items on lister pages. If no ranking rule triggers for a query, Fredhopper lists items using natural sort. Natural sort is a sorting order determined during the indexing of your data. Because it relies on the indexing process, it might vary between each reindex. You cannot control natural sort.
To avoid sorting items by natural sort, you need to maintain default ranking rules. You need one for lister pages shown after navigation and one for lister pages shown after search.
When your Fredhopper team configures Fredhopper for the first time, they will create default ranking rules for you. However, you might need to re-create or change them or add more defaults. In this case, follow these guidelines:
- Name your rankings 'Default navigation ranking' and 'Default search ranking'.
- Label them as default.
- Use the Result type trigger for each, and set it to Navigation or Search, as needed.
- Use a ranking that works for your product types and shoppers across all categories. For example, sort by relevance, margin, featured items, or new arrivals.
- Avoid sorting by brand for your default, because this strategy of ranking/sorting may change over time.
- Avoid sorting by top-rated for your default, because this strategy of ranking/sorting may change over time.
Maintain category ranking rules
Different categories contain items with different characteristics, some of which might be category-specific. Consider maintaining additional ranking rules for your categories that reflect the unique purpose of the category.
For example: in a Clearance category, sort by 'percent off' in an Apparel category, sort by new arrivals; in a thematic category, sort by relevance or featured.
To create a rule that triggers for a category, you can use a User location trigger.
Use labels
In a lengthy list of rules, labels help you find the rule you are looking for more quickly. Make sure that you have a concise list of labels and a clear naming convention for new labels. Establish internal guidelines for labelling and apply them.
In compound ranking rules, start with the attributes with the fewer possible values
In ranking rules with several sorting actions, begin with the attributes with the fewest possible values, i.e. an attribute with only two possible values. This increases the odds that the next sorting action will impact the sorting order.
Example
This example shows how attribute values influence the sorting of items.
Item |
Attribute X |
Attribute Y |
Attribute Z |
|---|---|---|---|
| A | 1 | 7 | 53 |
| B | 0 | 3 | 95 |
| C | 0 | 6 | 48 |
| D | 1 | 10 | 32 |
| E | 1 | 7 | 65 |
| F | 0 | 3 | 97 |
Table 1: List of unsorted items and their respective attributes
Item |
Attribute X |
Attribute Y |
Attribute Z |
|---|---|---|---|
| D | 1 | 10 | 32 |
| E | 1 | 7 | 65 |
| A | 1 | 7 | 53 |
| C | 0 | 6 | 48 |
| F | 0 | 3 | 97 |
| B | 0 | 3 | 95 |
Table 2: Items sorted, starting with X, then Y, then Z (from a few possible values to many possible values). All sorting is descending (from largest to smallest).
In this case, all attributes affect the sorting.
Item |
Attribute X |
Attribute Y |
Attribute Z |
|---|---|---|---|
| F | 0 | 3 | 97 |
| B | 0 | 3 | 95 |
| E | 1 | 7 | 65 |
| A | 1 | 7 | 53 |
| C | 0 | 6 | 48 |
| D | 1 | 10 | 32 |
Table 3: Items sorted, starting with Z, then Y, then X (from many possible values to few possible values). All sorting is descending (from largest to smallest).
In this case, only the first attribute affects the sorting.
Use numbers instead of text to flag items
Flag attributes let you mark an item as having or not having a characteristic. You can later use the flag to filter items when you present them to shoppers.
You can create a flag with text. For example, yes and no, or true and false values. As an alternative, you can use numbers. For example, 1 signifies yes or true and 0 signifies no or false. If you use numbers, you can then use the flag attribute in ranking rules and ranking cocktails.
Use caution when ranking by historical data
In some cases, past data might lead to continuously promoting or demoting the same items. In others, it might erroneously promote some items over others.
When you use historical data, choose relative attributes and limited time frames. For example, sort by average gross sales per day instead of an absolute number of sales for all time.
Example 1
You have a ranking rule that sorts items by page views. Items with the most page views appear first.
In this example, newer items always appear on the last pages because they don't have page views. Furthermore, items at the beginning of the list usually receive more attention. As a result, items with many page views continue to gather page views and appear at the top.
Example 2
You have a ranking rule that sorts items by average user rating. The average user rating is calculated as the sum of all ratings divided by the number of users who submitted ratings. Items with the highest scores appear first.
In this example, an item with just one or two very high ratings (5/5) might appear before an item with a lot of reviews but a lower average score (4.9/5).
If available, use predictive data
If you have access to any predictive data, use it in your rankings. This lets you create dynamic lists of items tailored to shoppers and their history.
Things to remember:
- You should always have a ranking rule for each lister page.
- Always have a default ranking rule, if nothing else.
- Housekeeping - retire ranking rules either delete or archive if they are not live or currently required across your site.
- Remember to check which Scope a ranking rule is applied to when troubleshooting.
Are you ready to create a new ranking rule? View our step-by-step guide.
Comments
0 comments
Please sign in to leave a comment.