What is Recently Viewed?

Recently Viewed is a storefront module that lists the products a visitor has opened during the current or an earlier session. It usually appears as a horizontal row at the bottom of product detail pages, on category pages, on the cart page or as a dedicated area in the customer account. The list is ordered by recency, deduplicated and limited to a small number of entries. Its purpose is navigational rather than promotional: shoppers who compare several items across a catalogue can return to a candidate without repeating a search or using the browser history.

Definition

Recently Viewed records product views as an event stream tied to an identifier. For anonymous traffic that identifier is a cookie or a local storage key, for signed in accounts it can be a customer id, which allows the list to follow across devices. The storage location determines consent handling, since local storage on the device is treated differently from a server side profile, and in the European Union that distinction matters for tracking consent. Frequent variants add a remove control, a price change marker or stock status. Pitfalls include showing sold out items without a hint, keeping entries far beyond their relevance window, and exposing browsing history on shared devices.

Why it matters

In a composable setup the view history lives outside the rendered page. The storefront writes view events to a client store, a session service or a customer data platform, and reads the list back through an API when a page renders. Because the content is specific to one visitor, the block is excluded from shared caches and loaded after the cached shell, which keeps product pages statically cacheable. Product identifiers from the history are resolved against the catalogue API, so price, availability and media stay current instead of being frozen at view time. Consent state decides whether the history is persisted on the server at all.

Use cases

Typical placements are the lower area of the product detail page, the empty state of a search or category page, the cart page next to the summary, and the customer account. On mobile a compact horizontal scroller keeps the block out of the main reading flow. Merchandising teams sometimes combine the module with an entry point into a comparison view, so a visitor can move directly from the history into a side by side view. Onsite retargeting and email can reuse the same event stream where consent covers that purpose. Measurement looks at return clicks into product pages and at assisted conversions rather than at direct revenue.

Related

Explore Personalization · First-Party Data.