What select_item measures
select_item is the GA4 ecommerce event for the click itself: somebody taps a product inside a list and travels to its page. It repeats the item’s identifier and, crucially, the list identifier and list name that the product was sitting in when it was chosen.
That list detail is what makes the event worth sending at all. Without it you already know a product page was opened; with it you know where the shopper was standing when they decided to open it, which is a different and more useful fact.
Why select_item matters
It closes the gap between a product being shown and a product being examined. Set the two side by side and you get a click-through rate for your own merchandising — for a category page, a search result set, a recommendation row, a homepage feature — which is the only fair way to judge those surfaces against each other.
It also protects the credit due to internal placements. A recommendation carousel that quietly drives a large share of your product page views will look worthless in any report that only counts arrivals from outside the site, and it tends to be the first thing removed in a redesign.
Where select_item goes wrong
It is the event most often skipped, on the reasoning that the product page view already records the visit. That is true, and it loses the source. The same product page can be reached from a category, a search, a recommendation or an external ad, and only select_item tells those apart.
When it is implemented, the usual fault is passing the list values on the impression and dropping them on the click, so the chain breaks at exactly the point it was meant to join. Firing it on any click within a product tile — a wishlist heart, a quick-add button, a colour swatch — rather than on navigation to the product also muddies the count and makes the click-through look better than it is.
How to act on it
Send the same list identifier and name that view_item_list used, and send the item identifier in the form your other events and your product feed already use. Test by opening the same product from two different lists and confirming the two events differ only in the list values.
Once the data is clean, use it to make merchandising decisions rather than to admire the funnel. Lists with many impressions and few selections need better images, clearer prices or different sorting; lists with a strong selection rate deserve more space and more products. Both changes are far cheaper than buying additional traffic, and both depend on the surrounding ecommerce tracking being consistent from impression through to order.
