Skip to content

Guide 32 · Ecommerce · GA4 + Tag Manager

Send the view_item event: the product page view that fills Items viewed

Checked 11 November 2026 · Verification: reference file checked in Python (figures recomputed from the worked example) · Steps traced to Google's developer docs and Analytics Help, opened 11 November 2026 · 5-minute read

A page_view never fills Items viewed. The view_item event does: send it when a product page loads, with the product and its value, or the Ecommerce purchases report stays at zero.

Expected signal

After step 3, DebugView shows a view_item event with value 30.03 and the tee in the items array, fired once per product page load. After about 24 hours, the Ecommerce purchases report shows the item in Items viewed, and the purchase journey shows the View product step.

Download the reference: the view-item-event reference (JSON) (873 bytes, MD5 42e41e0a693760deb97cd60abd900c15). It holds the event parameters, the worked example, and the recomputed figures.

What you need

  • The Google tag on the site. The event is sent through the Google tag; the install guide covers it.
  • Access to the website source code, or a Tag Manager container. The event fires when the product page loads, so it needs the page template or a data layer push there.
  • The product details for the page. The worked product is Google's own: Stan and Friends Tee, SKU_12345, 10.01 each.

The trace

  1. Fire the event when the product page loads. The view_item event measures viewing an item's details, so it belongs on the product detail page, not on the list page. Send gtag("event", "view_item", { currency: "USD", value: 30.03, items: [{ item_id: "SKU_12345", item_name: "Stan and Friends Tee", price: 10.01, quantity: 3 }] }). The value is the item's line: 10.01 × 3 = 30.03, using the same quantity the later add_to_cart will carry.
  2. Send the item, not just the page. The page_view that the Google tag sends automatically carries no product data. Without the items array, Analytics knows someone loaded a page but not which product they looked at, and Items viewed stays at zero in the Ecommerce purchases report.
  3. Check it in DebugView. Turn on debug mode, load the product page, and open DebugView (Admin, then Data display, then DebugView). Select the view_item event and check the value reads 30.03 and the items array holds the tee with price 10.01 and quantity 3. One page load must produce one event.
  4. Confirm the reports after about 24 hours. The Ecommerce purchases report counts items viewed from this event, and the purchase journey funnel uses it as the View product step. If the Pages and screens report shows product page views but Items viewed is zero, the page_view is firing and view_item is not.

Dead ends

DEAD END — PAGE_VIEW IS NOT A PRODUCT VIEW. The Google tag sends page_view on every page automatically, and page_view never carries an items array. A store that relies on page_view for product measurement has page views in the Pages and screens report and nothing in Items viewed. The two events measure different things.

DEAD END — VIEW_ITEM ON THE LIST PAGE. A list page shows many products; view_item is for the details of one item. Firing view_item for every product on a list page inflates Items viewed and mislabels list browsing as product viewing. The list page gets view_item_list; the product page gets view_item.

DEAD END — THE QUANTITY THAT DOES NOT MATCH THE CART. If view_item sends quantity 1 and add_to_cart later sends quantity 3, the view-to-cart rate in the report compares different quantities for the same product. Send the same quantity basis on both events so the funnel compares like with like.

End state

Every product page load sends one view_item event with the product, its price and quantity, and a value of 10.01 × 3 = 30.03 with currency USD. DebugView shows the event the same minute, and after about 24 hours the Ecommerce purchases report counts the item in Items viewed and the purchase journey counts the View product step.

Sources

Checked 11 November 2026. The event definition above is the one in Google's ecommerce developer guide and the recommended events reference, both opened 11 November 2026. No step was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The figures were recomputed in Python: 10.01 × 3 = 30.03. The reference file was checked the same way: its value equals the sum of price times quantity for its items.