## 💡 Prerequisites
**Knowledge** We recommend that you read the following guide:
[Widget Configurator](🔗): This will help you understand the process of creating a widget. We’ll be using a similar process to configure a Recently Viewed Products Widget.
Make sure you have integrated [Recommendations and Pathways](🔗) with your site. Visit [this](🔗) article for more details.
# What is Recently Viewed Products Widget
Recently Viewed Products Widget allows you to **display personalized product recommendations** based on the user's past purchasing history, browsing behavior, and customer preferences.
This user-based widget enables you to re-engage and re-target shoppers who are actively browsing and searching for products on your site. These shoppers are at the top of your conversion funnel, so targeting them can **boost conversions** significantly. When high-intent shoppers get easy access to products they have already shown interest in, the chances of them making a purchase are higher.
Recently Viewed Products Widgets can be easily placed on pages such as the Homepage, Add-to-Cart, Order Confirmation, and Product Description pages to create a **tailored shopper experience**.
# Recently Viewed Widget Algorithm - How it Works
Recently Viewed Products Widget is powered by the Recently Viewed algorithm. Here’s an overview of how the algorithm works:
## Visitor Classification
The algorithm uses the following classification to identify visitors:
For signed-in shoppers **→** **[user_id](🔗) **parameter is used for visitor identification.
For new visitors (not signed-in) **→** Bloomreach Cookie (**[br_uid_2](🔗)) **is used by default.
The last 90 days' data is considered for both kinds of visitors.
## Building Widget Recall
The algorithm builds the widget recall with recommendations in real time based on the following:
**Shopper’s most recent PDP View and ATC interactions** This helps build a set of products that the user has browsed (in Quick view by visiting the Product Detail Page), Added to the cart but not purchased. This data is supplied by the [Bloomreach Pixel](🔗).
**Widget customizations** The widget recall set also reflects any customizations made by you for targeted campaigns
The resulting personalized recall set is then sorted based on recency.
Please note that the experience is not personalized if the Bloomreach Cookie (br_uid_2) is rejected by the visitor.
# How to configure the Recently Viewed Products Widget
Go to **`
Pathways & Recommendations`** to view the Widget Configurator.
Add the Widget Basic Info like **`
Widget Name`** and **`
Then, select the Primary Algorithm and Secondary Algorithm for the widget.
Primary Algorithm`**: From the Primary Algorithm dropdown, select “**Recently Viewed**” as the Primary Algorithm.
Secondary Algorithm`**: Choose the fallback algorithm for the Recently Viewed algorithm from the following options:
You can also set the **Result size** and **FL list** for the widget. When you finish adding the widget's basic information, click **`
Next Step`** to proceed.
Under the Product Grid tab, apply the merchandising rules for the Widget as described [here](🔗). Click **`
Save`** to save the widget configurations.
#### **Step 6**
Once the widget is configured, note the _widget_id_ provided on Widget Configurator homepage. The widget ID will be required in the [API call](🔗).
# How to access this feature
**Live Customers**: If you are already live, please reach out to [Support](🔗) to enable this feature.
**Integrating Customers**: Please reach out to your Technical Services representative who is helping with your integration.
## Points to Remember
The “Recently Viewed” algorithm is available as a Secondary Algorithm for the following Primary Algorithms:
Frequently Viewed Together
Frequently Bought Together
The working of the Preview functionality depends on the Primary Algorithm selected. If “Recently Viewed” is your Primary Algorithm, Preview functionality is not supported. Only the following PID-based algorithms support Preview functionality:
Frequently bought together
Frequently viewed together
# Frequently Asked Questions (FAQs)
**How does the widget recall change when the visitor signs in/signs out in the same session? ** There can be scenarios where the user signs in/signs out in the same browsing session. The widget behavior will be as follows: <br>
<table> <tr> <td><strong>Scenario </strong> </td> <td><strong>Widget Behavior</strong> </td> </tr> <tr> <td><strong>Shopper is not signed in and has browsed products recently in the past 90 days</strong> </td> <td>Shopper browsing history is tracked via Cookie. <p> Recently viewed products are shown in the widget </td> </tr> <tr> <td><strong>During the same browsing session, the customer first views products without signing in and later signs in to see additional products</strong> </td> <td>The widget recall shows a combination of products the shopper looked at both when they were logged out and when they logged in. </td> </tr> <tr> <td><strong>During the same browsing session, the customer first views products while signed in and later signs out to view additional products.</strong> </td> <td>The widget recall shows a combination of products the shopper looked at both when they were logged in and when they logged out. </td> </tr> </table>
**2. What is the maximum number of products stored per user?** 100 products