Analytics and Tracking

select_item

Also called Product click, item list click

The GA4 event recording a click on a product within a list, carrying the placement it was chosen from.

Quick facts: select_item

Category
Analytics and Tracking
Also called
Product click, item list click
Level
Advanced
Affects
Merchandising measurement, internal placement credit, funnel completeness
Where to see it
GA4 (DebugView, Explorations), Google Tag Manager, browser developer tools
In this article4
  1. What select_item measures
  2. Why select_item matters
  3. Where select_item goes wrong
  4. How to act on it

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.

Do and do not

Do

  • Carry the list name and identifier through to the click
  • Fire it only on navigation to the product page
  • Test the same product from two different lists

Do not

  • Skip it because product page views are already tracked
  • Fire it on wishlist, swatch or quick-add clicks
  • Send an item ID that differs from the product feed

Questions people ask about this

Is select_item worth implementing on a small shop?

It is worth it once you have more than one way of surfacing products, such as categories plus search plus a recommendation row. On a shop with a single flat catalogue it adds little. The value comes from comparing placements, so if there is nothing to compare, spend the effort on the purchase and basket events first.

What is the difference between select_item and view_item?

select_item records the click on a product inside a list and carries the list it came from. view_item records the product page opening and describes the product in detail. They usually happen a moment apart, but only select_item can tell you which placement earned the visit, which is what makes merchandising measurable.

Should select_item fire when someone adds to basket from a list?

No. Adding straight from a list is a basket event, not a product selection, and should be sent as add_to_cart with the list values attached if you want to keep the placement. Firing select_item there inflates your click-through numbers and makes a listing look more persuasive than it actually is.

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.