What view_item measures
view_item is the GA4 ecommerce event fired when somebody opens a single product’s page. It carries an items array holding that product’s identifier, name, price and whichever attributes you choose to send — brand, category, variant — along with the currency and the value of the product being looked at.
It sits between seeing a product in a list and putting it in the basket, so it marks the point where general interest becomes specific. One product, one intention, recorded with enough detail to be joined to everything that happens afterwards.
Why view_item matters
It is the workhorse of product-level reporting. Comparing product views with basket additions tells you whether the product page is doing its job; comparing product views with list impressions tells you whether the listing is. Neither question can be answered without this event in place.
It also feeds advertising. Remarketing audiences of people who examined a product without buying, and dynamic product ads that show the exact item again, are both built from view_item and the identifiers it carries. If those identifiers do not match the ones in your product feed, the ads have nothing to show and the audience quietly does nothing.
Where view_item goes wrong
Variants cause most of the damage. A shop that sends a different identifier for every size or colour splits one product across many rows, while a shop that sends only the parent identifier loses the ability to see which variant actually sells. Pick one approach, send both the parent and the variant fields, and stay consistent across every event.
Price is the next problem. Sending a price with currency symbols, thousands separators, or tax treated differently from the order confirmation produces values that never reconcile with the shop’s own figures. The third fault is firing the event on quick-view popups as well as full product pages without distinguishing between them, which double counts interest and flatters weak products.
How to act on it
Check the event on a real product with a variant selected, using GA4’s debug view or your browser’s network tab, and confirm the identifier is exactly the one your feed and your purchase event use. That single check prevents most of the mismatches that otherwise surface months later as broken remarketing.
Then treat the relationship between product views and basket additions as a page-quality measure. Where it is weak, the fix is almost always on the page — missing sizes, unclear delivery, no stock information, a payment method the customer does not hold — rather than in the advertising that brought them there. Keeping the whole chain of ecommerce tracking events aligned is what keeps that comparison honest.
