WebmasterID logoWebmasterID
Analytics metrics

Cart-to-detail rate

Cart-to-detail rate divides the number of add-to-cart events by the number of product-detail-page views for the same items. By anchoring the denominator to product views rather than sessions, it measures how effectively a product page converts an interested viewer into a cart add, independent of how much general traffic the store receives. GA4's ecommerce engagement reporting exposes this ratio.

Verified against primary sources

What this means

Cart-to-detail rate is add_to_cart events divided by view_item (product-detail) events. GA4 surfaces it in ecommerce engagement reporting as a product-level efficiency measure. Because the denominator is product views rather than sessions, the rate normalizes for traffic: a niche product with few but highly qualified viewers can show a strong cart-to-detail rate even with low absolute volume.

Reading it correctly

The rate isolates the product page from the rest of the funnel. It does not tell you whether carts convert to purchases — that is the checkout completion and purchase rate's job. Used together, cart-to-detail rate, checkout completion rate, and purchase rate decompose the e-commerce funnel into stages you can fix independently.

Because it is product-scoped, aggregate the numerator and denominator over the same item set; mixing products inflates or deflates the ratio in misleading ways.

How it appears in analytics and logs

A low cart-to-detail rate on a page with healthy views points to the product page itself — price, photos, stock, reviews, or description — rather than to traffic or checkout. A high rate with few views points to a discovery problem upstream.

Diagnostic use case

Compare how well individual product pages turn viewers into cart adds, holding traffic volume constant, to prioritize merchandising and product-page fixes.

What WebmasterID can help detect

WebmasterID records view_item and add_to_cart events first-party, so both sides of the ratio are measured without third-party cookies and bot views are filtered from the base.

Common mistakes

Privacy and accuracy notes

It is a ratio of two aggregate event counts. No personal identifiers are required to compute it.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.