Analytics and Tracking

Product Performance Report

Also called item report, ecommerce purchases report

An item-level view showing views, basket additions, quantity sold and revenue for each product in the catalogue.

Quick facts: Product Performance Report

Category
Analytics and Tracking
Also called
item report, ecommerce purchases report
Level
Intermediate
Affects
Merchandising decisions, product page priorities, shopping feed strategy
Where to see it
GA4 Monetisation reports, shop platform sales reports, Looker Studio
In this article4
  1. What the product performance report shows
  2. Why it matters
  3. Where it goes wrong
  4. How to act on it

What the product performance report shows

Most analytics reporting stops at the order. This one goes a level deeper and lists each product on its own row, with the number of times it was viewed, added to a basket, bought, and the revenue it produced. It answers questions about the catalogue rather than about the shop.

The data comes from the item array your site attaches to ecommerce events. Every product view, basket addition and purchase carries a list of items, each with an identifier, a name, a price and often a category and brand. The report is a summary of those lists, so it only ever contains what your tracking bothered to send.

Why it matters

It separates a traffic problem from a product problem, which no site-wide metric can do. A product seen by many people and bought by almost none has an issue on its own page — the photography, the description, the price, the delivery estimate or a review that puts people off. A product bought by nearly everyone who sees it but seen by hardly anybody has a visibility problem, and the fix is merchandising, internal linking or advertising instead.

It also tells you where advertising money should go. Feeding a shopping campaign an entire catalogue treats a product that converts well and one that never sells as equals. Knowing which items earn their place lets you build product groups that match reality, and lets you stop paying for clicks on items the shop cannot sell.

Where it goes wrong

Missing or inconsistent identifiers cause the most damage. If a product’s identifier differs between the listing page, the basket and the purchase — or changes when a variant is chosen — the same item splits into several rows and none of them is right. The identifier you send should match the one in the shop platform and the product feed, so the same product means the same thing everywhere.

Incomplete instrumentation is the other pattern. Many shops track purchases properly but never send product views or basket additions, which leaves a report showing sales with nothing to compare them against. Variants are a third trap: reporting every size and colour separately buries the product, while collapsing them all hides the fact that one size never sells.

How to act on it

Start by proving the data. Open the report, pick a product you know well, and check that its view, basket and purchase numbers move in a sensible relationship to each other. If additions to basket exceed views, or a bestseller is missing entirely, fix the tracking before making a single decision from it.

Once it is trustworthy, use it for a short list of actions rather than a monthly read-through. Find the products with strong interest and weak conversion and rewrite those pages first, since the demand already exists. Find products that convert well but get little traffic and give them internal links, category placement or a campaign of their own. Pull the worst performers out of shopping feeds so budget stops leaking into them. If the item data itself is patchy, that belongs with the analytics and tracking work before any merchandising decision is made.

Do and do not

Do

  • Check item identifiers match across site, feed and platform
  • Send product views and basket additions, not only purchases
  • Rewrite pages where interest is high and conversion is weak

Do not

  • Act on the report before checking the numbers make sense
  • Let variants split one product across several rows unintentionally
  • Keep funding shopping clicks for items that never sell

Questions people ask about this

Why is a product missing from the report?

Almost always because its item data is not being sent. Products added through a custom template, a promotional block or a quick-buy button often bypass the tracking that normal listing pages use. Check the events on that product's own page in preview mode, and confirm the item identifier is present and matches the one in your shop platform.

Should variants appear as separate products?

Send both levels if you can. A variant identifier lets you see that one size or colour never sells, while a shared parent identifier lets you judge the product as a whole. If you must choose one, report at the level you make decisions at — usually the parent product for merchandising, the variant for stock planning.

How is this different from my shop platform's own sales report?

Your shop reports what was ordered and paid for, which makes it the authority on sales. The analytics report adds behaviour before the sale: how many people saw the product, how many added it to a basket, and where they came from. Use the shop for accuracy and analytics for diagnosis of why something is not selling.

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.