What to do if a recommendation has 0% coverage?
Explanation of the issue:
If you have noticed that a recommendation has 0% coverage, it means that the recommendation was not able to find any matching items in the catalog based on selected event attributes in the recommendation metric.
A recommendation can search items only based on the item_id attribute. It means that a data format in events used to generate recommendations must be exactly the same as item_id in the catalog. Additionally, the catalog filter must not be too strict - you must make sure that there are items that match catalog filters.
Example 1: Mismatched event data
Let’s look at this example. Here we have a “Popular Right Now” recommendation template that uses the purchase_example.item_id attribute to check what products customers are buying.
Currently, the coverage is 0% meaning that the recommendation cannot find any item_ids from Purchase_example.item_id attribute values in the catalog test used in the recommendation. The catalog has 2 items, one of them has ID Jeans-001-blue.
There is only one purchase_example event in the database currently and it has the following attributes:
