Definition
An add-to-cart is the action of placing a product in the shopping cart or basket. Add-to-cart rate counts the sessions in which that happened at least once and divides by all sessions in the same period and segment.
Sessions with an add-to-cart ÷ Sessions × 100(%)
- Sessions with an add-to-cart count each SessionA group of one user's interactions with a site or app in one visit, ended by inactivity. once, however many items were added. Counting events instead would let one enthusiastic shopper inflate the figure.
- Sessions are all visits in the period and segment, including those that never reached a product page.
Two denominators
The session-based rate above answers "of everyone who visited, how many started buying?" It is affected by traffic that never looked at a product, such as visitors to the blog or store-locator page. A product-view-based rate divides sessions with an add-to-cart by sessions that viewed a product, and answers "of the people who saw a product, how many wanted it?" That version isolates the product page. Both are legitimate; they produce very different numbers, and a report must say which it uses. Frameworks that treat product-page engagement as a planning stage, such as RACE applied to sales, usually prefer the product-view base.
Where the data comes from
In Google Analytics, ecommerce events supply the counts: an event fires when a product page is viewed and another when a product is added to the cart. If the add event is missing on some templates, such as quick views on category pages, the rate is understated. The GA4 ecommerce tracking tutorial covers instrumenting the full set of events from product view to purchase.
How to interpret it
Higher is better, and the rate is most informative beside conversion rate, as two branches of a KPI tree.
- Add-to-cart steady, conversion falling. Shoppers still want the products; something after the cart is losing them. Look at checkout, payment, delivery costs and site errors.
- Add-to-cart falling, conversion falling. The problem sits earlier: the products, prices, stock, page content or the traffic itself.
- Add-to-cart rising, conversion flat. More people start, the same number finish. Either the new adds are lower intent or the checkout cannot convert them.
The KPI trees guide shows how this split is laid out so that each branch has an owner. Read the rate by category, device and traffic source too: a sale on one category or a burst of low-intent traffic moves the site-wide figure without telling you why.
A garden tool shop looks past the product pages
Trowelsprig Garden Tools sees its conversion rate fall from 2.4% to 1.7% over three weeks in April, on about 60,000 sessions a week. The merchandising team prepares new product photography. Before it ships, the analyst checks add-to-cart rate: it has held at 7.8% throughout. Shoppers are adding as often as before, so the leak is downstream. Checkout drop-off by browser shows that a new payment step, added at the start of April, fails on one mobile browser that carries 18% of sessions. The fix to the payment step restores conversion to 2.3% within a week, and the photography project is reprioritised.
What moves it
- Price display. Clear prices, including any delivery cost or multi-buy offer, help shoppers decide on the page rather than after adding.
- Imagery and product information. Photographs, sizes, materials and reviews answer the questions that otherwise stop a shopper adding.
- Stock and variants. Out-of-stock sizes or colours, and variant selectors that are hard to use, block adds directly.
- Delivery promises. A visible delivery date or free-delivery threshold can tip a decision.
- Traffic quality. Broad or low-intent traffic lowers the session-based rate without any change on the page.
- Tracking. A missing add event on one template, or a duplicated one, moves the rate without any change in behaviour.
The product page optimisation guide covers these levers in detail.
Related metrics
Cart Abandonment RateShare of shopping carts created that did not become an order. is the next stage: of the carts created, how many never became orders. Together the two decompose CVRShare of visits or clicks that convert., the share of sessions that ended in a purchase. SessionA group of one user's interactions with a site or app in one visit, ended by inactivity. is the unit both rates are counted in, and AOVAverage revenue per order. completes the picture for revenue, since a change that raises add-to-cart by encouraging small, single-item baskets may not raise revenue at all.
What good looks like
There is no reliable universal benchmark, and the site does not cite one. The rate depends on the denominator, the category, the price point, the traffic mix and how the shop defines a session, and published figures rarely say which they use. Judge it against your own history by category, device and source, and beside conversion rate: what matters is whether the two are moving together, and which of them moved first.
Common mistakes
- Not stating the denominator, so session-based and product-view-based rates are compared.
- Counting add events instead of sessions, which rewards multi-item baskets twice.
- Calling an add-to-cart test a win without checking that orders followed. A lift in adds that does not carry through to purchases has not paid off, a trap the test pitfalls guide describes.
- Reading the site-wide rate when one category or source drove the change.
- Ignoring missing events on quick-view or category-page add buttons.
- Reporting add-to-cart without conversion rate. In a monthly pack such as the monthly marketing report template, show the two side by side so readers can see which branch moved.
