📋 Overview
Most Amazon reporting starts counting after a shopper already reached your detail page, which means a listing that never gets clicked in search results looks identical to one that was never seen at all. Search Catalog Performance, a report in Brand Analytics, closes that gap by showing impressions, clicks, cart adds, and purchases for each ASIN in your catalog. This article covers what the report actually counts, how to triage a whole catalog with it in one sitting, and which fix belongs to which stage of the drop-off.
The report is available to brand-registered sellers. If you are not enrolled in Brand Registry, the diagnostic logic here still applies, but you will be working from Business Reports and advertising data only.
🔍 What This Report Counts — and What It Doesn’t
The value of this report comes from knowing precisely what is inside each column. Read it as a search-only funnel, not as total product performance.
The four stages
Each ASIN gets counts for four sequential events:
- Impressions — times the ASIN appeared in search results
- Clicks — times a shopper clicked through from those results
- Cart adds — times the item was added to a cart after that click
- Purchases — times it was bought
Amazon also supplies rate columns alongside the counts. Before you build any analysis on them, open the report’s own column definitions and confirm what each rate is divided by, because a “cart add rate” measured against impressions tells a different story than one measured against clicks. If you are unsure, compute your own ratios from the raw count columns — those are unambiguous.
Search-sourced, not all traffic
These impressions come from Amazon search results. Traffic that reaches your page from a competitor’s detail page, a browse node, your Store, an email, or an off-Amazon link is not part of the impression count. That is why purchase rate here will rarely match Unit Session Percentage in Business Reports, which counts units against all detail page sessions regardless of source.
Treat the two as answering different questions. Search Catalog Performance tells you how the search surface treats each ASIN. Business Reports tells you how the detail page performs once anyone lands on it.
ASIN-first, not query-first
This is the difference that decides which report you open. Search Query Performance is organized by search term: it shows how your brand or ASIN performed for each individual query. Search Catalog Performance rolls everything up by ASIN across all queries at once.
So the workflow is: use Search Catalog Performance to find which products are leaking and at which stage, then switch to Search Query Performance to find which queries are responsible for that leak.
🧭 Running a Catalog-Wide Funnel Triage
Budget about an hour for a catalog of a few dozen ASINs. The goal is a short list of products with a named problem, not a full rewrite of everything.
1. Open the report and pick a closed reporting period
Find Search Catalog Performance inside Brand Analytics in Seller Central. The report is published for fixed reporting periods rather than any custom date range you type in, so select a period that has fully closed. Confirm which period granularities are available to you when you open it.
A good result here is a period long enough that your slower ASINs have meaningful impression counts. Weekly data on a product that gets a few hundred impressions will swing wildly for reasons that have nothing to do with your listing.
2. Export and rank by impressions, not by sales
Pull the export into a spreadsheet and sort descending by impressions. This deliberately puts high-visibility, low-conversion ASINs at the top — the ones Amazon is already showing to shoppers and that are wasting that exposure. Sorting by revenue hides them, because they are not producing revenue.
3. Build three ratios per ASIN
From the raw counts, calculate for every ASIN:
- Clicks ÷ impressions — how compelling the search result tile is
- Cart adds ÷ clicks — how convincing the detail page is
- Purchases ÷ cart adds — how much friction sits between intent and checkout
Then compute the median of each ratio across your own catalog and compare each ASIN to those medians. Your catalog’s own median is a far more useful yardstick than any published benchmark, because it already accounts for your categories, your price points, and your brand’s recognition.
4. Tag each weak ASIN with its first failing stage
Walk the ratios in order and stop at the first one below your catalog median. That stage is the one to fix; ratios further down the funnel are often distorted by the earlier problem and are not trustworthy yet.
- Low impressions relative to similar ASINs — a relevance and coverage issue. The ASIN is not being surfaced for enough queries.
- Impressions fine, click ratio low — the search tile is losing the comparison. Main image, title clarity, price shown, review count and star rating, and delivery promise are what a shopper compares at that moment.
- Clicks fine, cart-add ratio low — the detail page is not closing. Secondary images, bullets, A+ Content, variation setup, and price against the visible alternatives.
- Cart adds fine, purchase ratio low — friction at the end. Check whether you held the Featured Offer, whether shipping speed slipped, and whether the item went out of stock mid-period.
5. Send impression-stage problems to Search Query Performance
For ASINs failing at the impression stage, open Search Query Performance and use the ASIN View for that product. You are looking for high-volume queries where the ASIN earns few impressions, which points to a relevance gap you can address in the title, bullets, attributes, and backend search terms — not at higher bids.
For ASINs failing at click or cart-add stage, no query report is needed. The fix lives on the tile or the page.
6. Change one element and wait a full reporting period
Because the report publishes on fixed periods, comparing a half-period before a change to a half-period after gives you nothing. Make the change, then compare like-for-like periods. If the ASIN carries enough traffic and you want a controlled read rather than a before-and-after, run it through Manage Your Experiments instead — Amazon recommends an 8 to 10 week run when you choose the duration yourself, so confirm the current guidance in the tool before you plan around it.
💡 Pro Tip: A cart-add-to-purchase gap that appears suddenly and across several unrelated ASINs at once is almost never a content problem. Check whether you lost the Featured Offer on those products during the period — shoppers add to cart from your page, then buy from whoever holds the offer.
⚠️ Where Sellers Misread This Report
Comparing impressions here to ad impressions
Sellers open the advertising reports and the catalog report side by side, see two different impression numbers, and assume one is broken. They measure different populations: advertising impressions count ad placements served, while this report covers your ASINs’ appearances in search results. Use each to answer its own question rather than trying to reconcile the totals.
Diagnosing a variation family from one child ASIN
In a variation family, a single child often absorbs most of the search impressions while the rest look starved. That is normal behavior, not a defect in the weaker children. Sum the family before you judge it, and only treat a child as a problem if it earns real impressions and still fails to convert.
Acting on a low-volume ASIN’s weekly swing
On a product with small impression counts, a handful of clicks moves the ratios dramatically. Sellers rewrite listings in response to noise, then rewrite them back a month later. Set a minimum impression floor below which you simply do not act, and aggregate those ASINs over a longer period instead.
Fixing the detail page when the tile is the problem
A poor click ratio gets answered with new A+ Content, which shoppers never see because they never clicked. If the first failing stage is impressions-to-clicks, restrict your changes to what appears in search results. Make sure your main image meets Amazon’s requirements and is at least 1,000 px on its longest side so zoom is enabled, and confirm it reads clearly at thumbnail size.
❓ FAQs
Does this report include sales from ads?
The counts reflect activity on Amazon’s search surface for your ASINs and are not split into paid and organic for you. To separate the two, compare against your Sponsored Products data from Measurement & Reporting > Sponsored ads reports over the same period — if advertised clicks account for most of an ASIN’s clicks, your organic search presence is thinner than the top-line number suggests.
Why do my purchases here not match my order count?
Orders in your sales reports include every traffic source and every path to purchase, including repeat buyers going straight to the product, Subscribe & Save deliveries, and traffic from off Amazon. This report only captures purchases that began with a search impression, so it will normally show fewer.
Can I use it to track a competitor’s ASINs?
No. It reports on ASINs belonging to your own enrolled brand. For competitive context on specific search terms, Search Query Performance gives you your brand’s share of the total query funnel, which tells you how much of the available demand you captured without naming who took the rest.
How often should I run this triage?
Monthly is enough for most catalogs, with a same-week check after any launch, price change, or main image update on a high-traffic ASIN. Running it weekly on a stable catalog mostly surfaces noise and tempts you into changes that have to be undone.