AI in Personalized Shopping: What to Show Each Visitor

You have one catalog, one set of visitors, and several kinds of website personalization available. The practical question is which visitor gets which one.

This article answers that by visitor situation: what a model can match on when it knows nothing about someone, what changes once it knows their history, what the cart adds, and how to pick the first one to build.

Jump to a section:

• What AI in personalized shopping matches on

• Contextual AI recommendations: matching on the current session

• History-based AI recommendations: matching on past visits

• Complementary AI recommendations: matching on the cart

• AI cart recovery: matching on why a shopper hesitates

• AI personalization benchmarks: what to expect from each type

• Match each behavioral segment to an input

• How to pick your first AI personalization campaign

What AI in personalized shopping matches on

AI in personalized shopping means matching a visitor to products they are likely to want, decided by a model reading behavior instead of by one merchandised list shown to everyone.

The match is made while the visitor is on the page, so the model works with whatever it knows at that moment.

Three inputs are available, and each one is present for a different share of your visitors:

Whatever a vendor calls the feature, the input behind it decides what the recommendation can be about.

A model with only the current session can tell that someone is comparing dining tables, and cannot tell whether they already bought one from you last spring.

Those inputs produce four types of AI personalization:

• Contextual recommendations, matched on the current session

• History-based recommendations, matched on past visits

• Complementary recommendations, matched on the cart

• Cart recovery, matched on the reason a shopper looks likely to leave

None of this reaches a visitor the model knows nothing about. Someone arriving from a shopping ad onto a product page has no history and no cart, so the only input is a session that started nine seconds ago.

Any personalization for that visitor has to be built from the session or not at all.

Contextual AI recommendations: matching on the current session

Contextual matching is the type that runs on a visitor with no history, and a first visit hands a model behavior and no preferences. A session shows what someone is doing while staying silent on who they are, and contextual matching is built around that limit.

That situation is the normal case rather than the edge case. On a median site we track, 67.6% of sessions are a single page view, and the middle half of sites fall between 56.2% and 79.5%.

Session depth on a median tracked site breaks down like this:

Sessions of three page views or more come to 17.8%. Personalization built on a visitor profile therefore reaches a minority of traffic, and contextual matching covers the rest.

What one session gives you:

• The category the visitor chose

• How many products they opened inside it

• The product they came back to

• The page they arrived on, and the source that sent them

• The device

What one session withholds:

• Size, budget, and taste

• Anything they viewed or bought on an earlier visit

• Whether they are buying for themselves

Contextual matching works from the first list only. Show best sellers to someone browsing a category and the suggestion is anchored to the one thing you know for certain, which is the category they picked themselves.

Nutrimuscle sells sports nutrition, where a first-time buyer choosing a protein has to compare products that read almost identically on a spec sheet.

The brand shows best sellers to visitors viewing products inside a specific category, and builds comparison tools by category so the suggestion answers the comparison the visitor is already in the middle of.

Its protein comparison tool works from the category alone:

Pierre Hardy runs the same input in its onsite feed, where a new visitor sees the pieces most people buy:

Device is on that first list, and it changes the result more than the other signals. A phone visitor is scrolling with a thumb on a small screen, while a desktop visitor has the product, the reviews, and two competitor tabs open at once.

The same recommendation performs differently in those two situations:

That splits into two builds. On a phone the recommendation is there to open up the catalog, so more items and a lighter ask work better. On desktop it is there to confirm a choice already half made, so fewer items and closer relevance to the product on screen do more.

History-based AI recommendations: matching on past visits

For a returning visitor, history changes the question from what is popular in this category to what this person already looked at. For a visitor who opened four bags last week, the four bags are the strongest thing you can show them.

émoi émoi shows recently viewed products in real time in its onsite feed, five items with image previews, reachable from any page. For a shopper who left mid-comparison, that is a shortcut back into the session they abandoned rather than a fresh set of suggestions to work through.

Maison Lejaby runs the same input across a lingerie catalog where finding a matching set is the hard part, and its E-Store Manager names the recently viewed notification as the brand's favorite.

Over four months the brand's feed campaigns held a 15% average click rate, with 16% on mobile against 13% on desktop, on traffic that is two thirds mobile.

Here is the recently viewed reminder in place:

History only works where the visits can be joined to one person. A shopper who browsed on a phone at lunch and returned on a laptop that evening counts as two visitors unless they signed in.

Complementary AI recommendations: matching on the cart

Once a visitor has an item in the cart, the input changes again, because what a cart describes is the purchase rather than the person.

That makes complementary matching the most dependable of the three: a first-time visitor with an item in the cart can be matched as accurately as a customer of five years.

Pierre Hardy triggers frequently-bought-together suggestions from cart contents while the shopper is still deciding, and places a "complete your look" block beside the cart as an embedded section of the page rather than a message on top of it:

The limit here is catalog depth. Complementary matching needs enough order history for the model to learn which items travel together, so a retailer with a small catalog or a short trading history will see thinner suggestions until the data accumulates.

AI cart recovery: matching on why a shopper hesitates

A visitor about to abandon a full cart is where personalization and discounting get confused with each other. The reflex is to offer money off, and hesitation has more than one cause.

Four common ones:

• Shipping cost or delivery date

• Doubt about size or fit

• Comparison shopping

• Payment friction

A discount answers the first cause and pays out on all four, including the shoppers who were going to buy anyway.

Matching on hesitation means the model predicts likely abandonment during the session and the message addresses the reason: shipping thresholds for the first, sizing help or reviews for the second, complementary suggestions for a shopper still comparing.

On a median site running personalized recovery, 14.6% of the visitors who interact with the message go on to convert.

Recovery also reaches a shopper who has not given an email address, which is the part a recovery email cannot cover.

Pierre Hardy applies it selectively, to high-value carts only:

A second version keeps the cart itself in the message, so the shopper sees what they are leaving behind:

A cart value threshold, a first-order flag, or a delivery region keeps recovery aimed at the carts where the margin supports an incentive.

Those same thresholds decide how much a store can spend recovering an abandoned cart.

AI personalization benchmarks: what to expect from each type

Here is the shape of our own base, measured per site so that one large customer cannot move the numbers.

Click rates and post-engagement conversion rates by matching type:

Three readings from those numbers:

• Recommendations convert at about a quarter of recovery's rate once a shopper engages, which places them closer to discovery than to closing.

• Recovery's range is far wider, 4.3% to 28.5% against 6.9% to 17.7%, so targeting accounts for more of its outcome.

• Below roughly 7% click rate, a recommendation campaign sits in the bottom quarter of our base.

Figures are Wisepops campaign data for August 2025 to July 2026, taken per site. Every site in it already runs onsite campaigns, and the rates describe engagement with a campaign rather than incremental revenue against a holdout.

Match each behavioral segment to an input

Four kinds of matching are now available, each fitting a different visitor. Choosing between them means knowing which visitors your traffic contains and in what quantity, which is a grouping question rather than an algorithm question.

Six ways of grouping visitors by behavior, and the signals behind each, are set out in behavioral segmentation for ecommerce. What matters for personalization is narrower: a segment is useful only if it tells you which input to match on.

Behavioral segments and the matching each one supports line up like this:

What that table cannot tell you is how much of your traffic sits in each row, and that number is the one that decides where to start.

A store where the first row is a third of all sessions has a contextual problem to solve before anything else. A store where the second row is thin will get very little from narrowing recommendations by comparison behavior.

How to pick your first AI personalization campaign

1. Check what share of your sessions are a single page view

In your analytics, break sessions down by page depth. Above 60% single-page puts contextual matching first, because history and cart inputs exist for too little of your traffic to start there.

2. Write down which of the three inputs you already collect

Session signals are available to anyone. History needs visits joined to one visitor, so check whether yours are. Cart contents need the cart state readable while the visitor is still on the site.

3. Build one campaign, for your largest segment, using the input that segment has

One campaign, one segment, one input. A single-page segment gets best sellers from the landing category. A returning segment gets recently viewed items. A cart segment gets complementary items.

4. Run it against a control in the same position

Duplicate the campaign with a fixed product set instead of the model's picks, or hold back a share of visitors who see nothing. Same trigger, same placement, same audience. Compare click rate and the conversion rate of visitors who engaged.

5. Read the result against the benchmark before changing the algorithm

Under 7% click rate puts you in the bottom quarter of our base, and the cause is usually the segment, the trigger, or the placement. Change one of those and rerun step 4. Move to a second segment once the first campaign beats its control.