What Is eCommerce Analytics? A Plain Guide to the Numbers That Actually Move Revenue

You pull up your Shopify Analytics on a Monday. Revenue is down 11% week-over-week. You look at sessions: stable. You look at conversion rate: stable. You look at traffic sources: nothing unusual. The dashboard is full of numbers and none of them explain what happened.

That is the fundamental problem with how most stores use ecommerce analytics. The numbers are there. The answer is not.

This guide covers what ecommerce analytics actually is, what it is supposed to do, where most stores run into a wall, and which specific reports separate useful insight from noise.

What ecommerce analytics is

At the most basic level, ecommerce analytics is the practice of collecting, organizing, and interpreting data about how customers find, browse, buy from, and return to an online store.

The goal is not to measure everything. It is to answer questions that change what you do next week: which products are converting, which are leaking traffic, which customers are likely to return, and where in the purchase path you are losing people you could have saved.

Done well, ecommerce analytics turns a morning ritual of staring at dashboards into a habit of asking one specific question, getting a clear answer, and acting on it.

Done poorly, it produces a spreadsheet no one looks at and a reporting stack that costs more time to maintain than it returns in decisions.

The two kinds of analytics most stores mix up

There is a distinction that matters enormously for how you choose tools and how you interpret data, but most guides skip it.

Marketing analytics answers: who came, from where, and did they buy? It is the language of sessions, channel attribution, cost per acquisition, and ROAS. Tools like GA4, Meta Ads Manager, and Triple Whale live here. These tools are designed for the question “which campaigns are working?”

Product analytics answers: which products, categories, and customer behaviors are driving purchases, repeat orders, and lifetime value? It asks questions like “which product does a customer tend to buy first that predicts a second purchase?” or “which category has a 43% cart abandonment rate while the rest of the catalog sits at 12%?” For a deeper look at the product side specifically, what product analytics is and what it can do for your store covers the distinction in more detail.

Most stores only have marketing analytics. They can tell you which Facebook campaign drove 200 clicks. They often cannot tell you that 160 of those 200 clicks landed on a product that converts at 0.3% because the size guide is missing from the listing.

The gap between these two types is where most ecommerce revenue problems live.

The numbers that actually move revenue

Not all ecommerce metrics are equal. Here is where to focus.

Conversion rate by product, not site-wide. Your store’s overall conversion rate is an average that hides enormous variance. A site-wide 2.1% CVR could include a hero product converting at 8% and a featured item converting at 0.4%. The average tells you nothing; the product-level breakdown tells you exactly where to spend an hour of merchandising attention. Why your eCommerce conversion rate is a misleading metric goes into exactly how this average obscures what is actually happening.

Cart abandonment by product. Aggregate abandonment rates are another unhelpful average. When you break abandonment down by SKU, you typically find that 3 to 5 products are responsible for a disproportionate share of total abandonment. One might be a high-price item where checkout friction matters. Another might have a sizing issue. Another might simply need a better product image.

In a Stormly cart abandonment breakdown, you can see exactly which products appear most frequently in abandoned carts versus completed orders. A women’s sneaker in size 8 showing up in 41% of abandoned carts versus 9% of completed orders is not just a data point. It is a specific action: restock, add a size note, fix the product page.

Repeat purchase rate by first-purchase product. This is a metric most ecommerce stores have never seen, because it requires combining first-order and second-order data at the product level. It answers: “Which product does a customer tend to buy first that makes them come back?”

Some stores find that a low-margin consumable (a face wash, a protein supplement, a phone case) has a repeat purchase rate 3 to 4 times higher than a high-ticket item. If you do not know this, your acquisition strategy may be optimized for the wrong product entirely. When Stormly runs a product cohort, it shows exactly this: the percentage of customers who made a second purchase within 90 days, broken down by which product they bought first.

Retention by category over time. Which product categories keep customers coming back and which attract one-time buyers? Stormly’s retention curve, filtered by category, shows the drop-off shape after a first purchase. A skincare category that retains 38% of first-time buyers through month 3 looks very different from a shoes category that retains 9%. Those two numbers point toward very different marketing and merchandising priorities.

For context on where typical stores land, eCommerce retention rate benchmarks by category shows average ranges and what moving from the median to the top quartile is actually worth in revenue terms.

See eCommerce analytics in action with a free Stormly trial.

Where Shopify Analytics and GA4 fall short

Both tools are useful. Neither gives you the full picture.

Shopify Analytics is good for revenue totals, orders, and basic product performance like units sold and revenue per product. Its limits show up when you try to ask behavioral questions. It does not track what a visitor did before buying, it does not show which product pairs tend to be bought together, and it does not break down abandonment by product step. Several merchants on r/shopify have reported that Shopify’s add-to-cart count is simply wrong, or that it shows 0 purchases for a day where they packed real orders. Native reporting is a starting point, not a full analytics layer.

GA4 is better for behavioral and funnel data, but it models everything as events. For a store that thinks in products, carts, and categories, you have to build the event taxonomy yourself, maintain it, and then write custom explorations to get to the product-level questions. The result is usually a partial answer that takes a full day to produce.

Neither tool gives you a product cohort, a first-purchase-to-repeat-purchase retention curve, or cart abandonment broken out by SKU without significant custom work.

The third layer: product-level analytics for ecommerce

The gap between marketing analytics and genuine product intelligence is where purpose-built ecommerce analytics tools operate.

Tools built for this layer do not require you to define events or build custom funnels. They understand that an online store’s unit of analysis is a product: which products convert, which retain customers, which leak. They treat the catalog as the primary dimension, not a secondary filter.

Stormly is built specifically around this model. It connects to a store’s order and behavior data and surfaces the product-level questions marketing analytics cannot answer: which SKUs are dragging down your overall conversion, which first-purchase products predict a returning buyer, where the checkout funnel breaks by product rather than overall. Reports like these do not require an analyst or a BI request queue. For stores that want answers on demand, self-serve analytics for eCommerce teams covers how to set this up so product questions get answered without waiting.

For a full comparison of which tools cover which specific jobs across marketing analytics, behavioral analysis, and product-level decisions, eCommerce analytics tools organized by the decision you are trying to make maps the landscape without the usual generic feature matrix.

How to know if your current setup is missing something

Three questions worth answering honestly:

1. Can you name the three products in your catalog with the highest abandonment-to-purchase ratio right now, without building a custom export?
2. Do you know which product category retains the highest percentage of first-time buyers through month 2?
3. Do you know which product most of your second-time buyers purchased first?

If any of these take more than a few minutes, your current analytics layer has a gap. Not because the tools you are using are bad, but because they were not designed for this specific job.

The good news is that the data to answer all three questions is almost certainly sitting in your order history. The question is whether your analytics setup surfaces it as a decision or leaves it buried in a raw export.

What to do next

eCommerce analytics covers a wide range. Marketing analytics (sessions, attribution, ROAS) gives you the acquisition picture. Product analytics (SKU-level conversion, retention by category, first-purchase cohorts) gives you the product and merchandising picture. Most stores have the first type and are missing the second.

The starting point is to run a product cohort on your last 6 months of orders. Which 5 products have the highest repeat purchase rate? Which 5 have the lowest? Those 10 data points tend to change how you think about your catalog faster than any session-level dashboard can.

See your store’s product-level eCommerce analytics in action. Start a free Stormly trial.