Analytics and Tracking

add_to_cart

Also called Cart addition, basket add

The GA4 event recording an item being placed in the basket, with its price, quantity and currency.

Quick facts: add_to_cart

Category
Analytics and Tracking
Also called
Cart addition, basket add
Level
Beginner
Affects
Funnel diagnosis, remarketing audiences, bidding signals
Where to see it
GA4 (DebugView, Monetisation reports), Google Tag Manager, Meta Events Manager
In this article4
  1. What add_to_cart measures
  2. Why add_to_cart matters
  3. Where add_to_cart goes wrong
  4. How to act on it

What add_to_cart measures

add_to_cart is the GA4 ecommerce event sent when a shopper puts an item into the basket. It carries the items array — identifier, name, price, quantity and any variant detail — along with the currency and the value of what was added, not the value of the basket as a whole.

It is the first step where a visitor commits to something. Views and clicks are interest; a basket addition is a stated intention to buy, which is why the event is used well beyond reporting.

Why add_to_cart matters

It splits your funnel loss into two very different problems. People who look at products and never add are being failed by the product page. People who add and never buy are being failed by the basket, the delivery terms, the payment options or their own trust in the shop. The remedies have nothing in common, and without this event you cannot tell which problem you have.

It is also the most useful remarketing audience most shops own, and a common signal for bidding on platforms that need more volume than purchases alone can provide. In smaller markets, where order counts can be too thin for automated bidding to learn from, basket additions often carry that load instead.

Where add_to_cart goes wrong

Quantity is the first trap. Shops that send a quantity of one regardless of what the shopper actually chose will under-report demand for anything bought in multiples, and the value sent will never agree with the basket total.

The second is counting the same addition twice, once from the theme’s own tracking and once from a plugin or tag container, which inflates the entire middle of the funnel and makes the basket look far leakier than it is. The third is firing the event on a wishlist, a saved item or a “notify me” button. Those are weaker signals and belong in separate events, or your remarketing will chase people who never intended to buy today.

How to act on it

Test it with a quantity greater than a single unit and with a variant selected, and confirm the value sent equals price multiplied by quantity in your own currency. Then compare add_to_cart against purchase over a period long enough to cover your usual buying delay, so that a lag is not misread as a leak.

If the gap is wide, examine the practical obstacles before the persuasive ones: delivery costs appearing late, a forced account before checkout, a payment method your customers do not hold, a form that fights with a phone keyboard. Those are the causes I meet most often, and every one of them is fixed in the shop rather than in the advertising. Keep the event consistent with the rest of your ecommerce tracking so the comparison stays trustworthy over time.

Do and do not

Do

  • Send the real quantity the shopper selected
  • Check for duplicate events from theme and plugin together
  • Compare basket additions with orders over a realistic period

Do not

  • Fire it on wishlist or notify-me buttons
  • Send the whole basket value instead of the item value
  • Optimise ads to basket additions when order volume supports purchase

Questions people ask about this

Should I optimise my ads towards add_to_cart or purchase?

Purchase is the outcome you want, so optimise towards it whenever the platform has enough orders to learn from. Where order volume is low, basket additions give the system more signal and are a reasonable interim target, provided you keep watching actual revenue. Move back to purchase as soon as the volume supports it.

Why does my add_to_cart count look too high?

Duplication is the usual reason. Many shop themes send the event themselves while a plugin or tag container sends it again, so every addition counts twice. Wishlist and notify-me buttons wired to the same event add more. Check what fires when you add a single item, using debug view, before drawing any conclusion about the basket.

Does add_to_cart include the value of the whole basket?

No. The value belongs to the item or items being added in that action, calculated as price multiplied by quantity in your shop's currency. Basket totals belong to the view_cart and checkout events. Mixing the two produces values that cannot be reconciled with your orders and quietly distorts any return-on-spend reporting built on them.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.