Analytics and Tracking

view_item_list

Also called view item list event, select_item

A GA4 recommended ecommerce event sent when a visitor is shown a list of products, such as a category page, search results or a carousel.

Quick facts: view_item_list

Category
Analytics and Tracking
Also called
view item list event, select_item
Level
Intermediate
Affects
GA4 item list reports, category page analysis, product position testing
Where to see it
GA4 DebugView, Google Tag Manager preview mode, GA4 explorations by item list name
In this article4
  1. How view_item_list works
  2. Why it matters
  3. Common mistakes
  4. How to act on it

view_item_list is a recommended GA4 ecommerce event that your site sends when a visitor is shown a list of products, such as a category page, internal search results or a “you might also like” carousel. Its companion, select_item, is sent when the visitor clicks a product in that list. Together they show which lists earn attention and which products within them get chosen.

How view_item_list works

When a list appears, your site pushes the event with a name and ID for the list, plus an items array describing the products shown:

  • item_list_name and item_list_id: a readable label and a stable code, for example “Women’s raincoats” and “cat_womens_raincoats”, or “Related products” for a carousel on product pages.
  • index on each item: its position in the list, starting at 1 or 0 as long as you are consistent.
  • The usual product fields: item_id, item_name, price, item_brand and item_category.

When a shopper clicks a product, select_item sends the same list name and ID with the single product chosen. The product page then fires view_item. That chain lets GA4 report items viewed in a list, items clicked and the click-through rate for each list and position.

GA4 limits how many items a single event can carry, and long lists with infinite scroll or “load more” buttons can exceed it. Sending items in batches as they come into view is more accurate than dumping a whole category at page load.

Why it matters

For most online shops, category pages are the pages that win organic search traffic for broad product terms, and internal search serves the visitors who already know what they want. view_item_list tells you how those pages perform once people arrive. A category that gets plenty of list views but few clicks is often sorted badly, shows thin product information on its cards, or puts out-of-stock items at the top.

Position data answers a recurring merchandising question: whether products near the top sell because they are good, or only because they are near the top. It also shows whether a recommendations carousel earns its space or just slows the page down.

Common mistakes

  • Vague list names such as “list” or “products”, which make the report unreadable.
  • Naming the same list differently on different templates, so one category appears as three lists.
  • Sending every product in a 300-item category the moment the page loads, which overstates what people actually saw.
  • Leaving out index, so position analysis is impossible.
  • Sending view_item_list without select_item, which means you can count impressions but not clicks.
  • Forgetting internal search results, often the list with the clearest buying intent on the site.

How to act on it

Write down every product list on the site, including homepage blocks, filtered category views, search results and carousels, and give each a fixed name and ID. Ask your developer or shop app to send view_item_list and select_item with those names and the index of each product, then check them in Tag Manager preview mode.

After a month of data, compare list click-through rates by category and by position, and test one change at a time: a new default sort order, better product card information or fewer items above the fold. Category performance sits at the centre of ecommerce SEO, so this is data I want before recommending changes to category structure or content.

Do and do not

Do

  • Give every product list a fixed, readable name and ID
  • Send select_item alongside view_item_list
  • Include each product's position in the list

Do not

  • Send every product in a long category at page load
  • Name the same list differently on different templates
  • Forget internal search results

Questions people ask about this

What is select_item and do I need it?

select_item is the event sent when a visitor clicks a product inside a list. Without it, you know how often a list was shown but not how often it led anyone to a product. If you send view_item_list, send select_item too, using exactly the same list name and ID.

Should I track homepage carousels with view_item_list?

Yes, if they show products and you want to know whether they earn their space. Give each carousel its own list name, such as "Homepage new arrivals". If a carousel rarely gets clicks, that is useful evidence for replacing it with something faster or more helpful.

Does view_item_list affect my SEO directly?

No. It is a measurement event, and Google Search does not use your GA4 data to rank pages. What it gives you is evidence about how category pages behave for visitors, which helps you decide what to change on pages that search traffic lands on.

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.