Recently viewed implementation

Recently viewed implementation is a block that automatically remembers the products a visitor has viewed and shows them on the homepage, in the catalog or on a card. Nothing needs to be clicked — the history is collected by itself, and a person easily returns to what caught their eye, instead of searching again or forgetting. How it differs from favorites (see the “Wishlist / favorites implementation” service): into favorites a person puts what they definitely want to save and buy, deliberately with a button; “recently viewed” is collected by itself and shows the whole path of choosing — what was interesting in passing and what is no longer relevant. We do it for guests (browser storage — lost on clearing cookies or in incognito) and for logged-in users (history on all devices). Importantly and honestly: it is not a sales driver and not a magic button, but it noticeably reduces losses when a visitor returns to products — especially in a large catalog. And since it is browsing history, it works by cookie consent: without consent the guest history is not stored, the block is enabled only after consent via the banner (see the “Cookie banner with CMP” service). It pays off where the visitor views many products (catalogs, marketplaces); on a site with three items there is little point, and we will say so. About price, honestly: from 10,000 ₽ it is the adaptation to your catalog, the setup by cookie consent and the universality for guests and the account, which most boxed modules do not have; if a standard CMS block is enough for you, we will say so. Picture this: a person viewed five models, went to the homepage — and at the bottom there is “you recently viewed”, and they return to the one they need in one click. The base price starts from 10,000 ₽; it depends on guest/account and the display location.

• The visitor viewed a product, left and forgot — it is hard to find it again.
• To get back to what was viewed, you have to search again — many do not return.
• The catalog is large, the visitor loses the thread — it is unclear what they have already seen.
• You miss an easy way to bring a person back to what interested them without ads.

• A “you recently viewed” block on the homepage, in the catalog, on a card
• Automatic collection of the browsing history — without user actions
• For guests — browser storage; for logged-in users — on all devices
• Setting the number of products and the display location
• Working by cookie consent: without consent the guest history is not stored (linking with the CMP)
• Responsive, a tidy block on a phone
• Integration with the catalog, moving to the card and the cart

• The visitor can easily return to what was viewed — without searching again
• Less lost interest — what was viewed is always at hand
• A small boost to conversion is likely in large catalogs — an unobtrusive reminder of the products
• Easier navigation in a large catalog — it is visible what was already studied

• You leave a request and describe the catalog, guest/account, the display location
• We implement history collection, the display block, accounting for cookie consent
• We test and launch

• How is “recently viewed” different from favorites?

  Favorites (see the “Wishlist / favorites implementation” service) is a deliberate choice: a person clicks “add to favorites” themselves on what they want to save. “Recently viewed” is collected automatically and shows the whole path of choosing — what was opened in passing. Favorites is “I want to save this”; recently viewed is “here is what you viewed recently”. They are often shown together.

• Will it greatly boost sales?

  Honestly — no, it is not the main sales driver but a convenient and inexpensive experience improvement. It gently brings the visitor back to what they viewed and, in large catalogs, gives a small boost to conversion, but on its own it does not work miracles. People take it precisely as a navigation improvement, not as a “magic button”.

• What about cookies and consent?

  “Recently viewed” is browsing history, so for guests the data is stored in the browser and works by cookie consent: without consent the history is not stored. If you have requirements under the personal data law or the GDPR, we tie the block to the consent banner (see the “Cookie banner with CMP” service) so everything is correct.