What add to cart rate measures
Count the sessions in which at least one item was added to the cart, divide by all sessions, and you have the rate. Some shops measure it against product page views instead of all sessions, which is a stricter and often more useful version: it asks how persuasive the product page was, rather than mixing in visitors who never reached one.
Whichever denominator you choose, pick one and keep it. The two versions produce very different numbers from the same data, and a shop that quietly switches between them will convince itself something improved when nothing did.
The measurement depends on an event firing correctly. In GA4 the add_to_cart event carries the item, the price and the quantity, and if it fires on page load, or twice on a single click, or not at all on a quick-add button, everything built on top of it is wrong. Verify the event before you trust the metric.
Why add to cart rate matters
It splits the funnel at exactly the point where two very different problems separate. A low add to cart rate with a healthy checkout completion rate means the traffic or the product page is the problem: wrong audience, wrong keyword, weak images, missing information, an unclear price. A healthy add rate with weak checkout completion means the product is fine and the checkout is losing people.
That distinction is worth real money, because the two fixes have nothing in common. One sends you back to targeting and product content; the other sends you to delivery charges, payment options and form length.
It is also an early signal. Purchases are rare enough on a small shop that changes take a long time to prove themselves, while adds happen often enough to show a difference sooner. For a shop in Nepal where much of the traffic arrives from a phone through social feeds, the add rate on mobile compared with desktop is often the first place a page problem shows up.
Where add to cart rate goes wrong
Treating it as a goal in itself is the main trap. It is easy to raise by encouraging casual adds — a bright button, an offer that turns out not to apply — and the extra carts simply become abandonment later. The metric only means something when it is read next to what happened afterwards.
The other failures are measurement ones. Bot traffic and internal visits inflate sessions, quick-add widgets on category pages often fire no event at all, and a shop comparing its rate to some general benchmark is comparing across product types, prices and traffic sources that have nothing in common.
What to do about it
Confirm the event first, then segment before you act: by device, by landing page, by channel and by product. A shop-wide rate rarely tells you where to work, while the same figure split by source usually points straight at one campaign or one page template.
On the page itself, the reliable improvements are unglamorous — clear price including what delivery will add, honest photographs of the actual item, stock and delivery expectations visible, variants that do not reset the page, and a button that does something visible when pressed. Test them one at a time as part of ordinary conversion rate optimisation, and always check the change against the checkout completion rate so you can see whether the extra carts turned into orders.