At a glance
For each search term that drives traffic to your products, which of your ASINs actually wins the sale. Built on Amazon Brand Analytics, this table ranks your ASINs by their conversion contribution for a given query, so you can see whether the right product is capturing the demand behind a keyword. It answers questions like “for the query that brings the most clicks, is my hero ASIN or a weaker variant getting the purchases?” and it is the bridge between search visibility and search-driven sales.
| What it counts | A per-query ranking of your ASINs by their share of conversions (purchases) for that search term, drawn from Amazon Brand Analytics Search Query Performance and related reports. Each row pairs a query with the ASINs converting on it and their relative rank. |
| Brand Registry requirement | Brand Analytics data requires Brand Registry enrolment. If your brand is not registered, this card has limited or no data. See Brand Registry Coverage. |
| Why it matters | Search visibility without conversion is wasted impressions. This card tells you whether the demand behind a keyword is being captured by your best product or leaking to a weaker listing (or to a competitor), which guides advertising, content, and variation strategy. |
| Click vs purchase share | Brand Analytics distinguishes the ASIN that gets the clicks from the ASIN that gets the purchases. A query where one ASIN gets the clicks but another converts signals a listing or pricing mismatch worth fixing. |
| Organic vs ad | The card reflects conversion contribution at the query level. To separate paid from organic capture, pair with Organic vs Ad Sales Share. |
| Granularity | Amazon’s Brand Analytics is aggregated and anonymised; figures are relative ranks and shares rather than exact per-buyer detail. |
| Reading the table | Look for queries where a high-traffic term converts on the wrong ASIN, or where your hero ASIN ranks below a variant. Those are the actionable rows. |
| Currency / unit | number (rank / share) |
| Time window | 30D (rolling 30 days, aligned to Brand Analytics reporting periods) |
| Alert trigger | none (reference / diagnostic card) |
| Roles | owner, marketing |
Calculation
Calculated automatically from your Amazon Seller Central and Brand Analytics data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A coffee brand on Amazon US, Brand Registry enrolled, 30-day Brand Analytics period ending 01 May 26. All numbers illustrative.| Query | Top click-share ASIN | Top purchase-share ASIN | Notes |
|---|---|---|---|
| ”ground coffee” | House blend 1kg | House blend 1kg | Aligned, hero ASIN wins both |
| ”espresso beans” | Espresso 250g | Espresso 1kg | Clicks go to the small pack, purchases to the value pack |
| ”decaf coffee” | Decaf 500g | Competitor (not yours) | Your ASIN gets clicks but loses the sale |
| ”coffee gift set” | Gift box | Gift box | Aligned |
| ”single origin” | Variety pack | Single-origin Ethiopia | Wrong ASIN ranks for the query |
- “espresso beans” is a packaging-mix story, not a problem. Clicks land on the 250g pack but purchases convert on the 1kg value pack. That is healthy: browsers click the cheap entry point and buy the better-value size. No action, but worth knowing for ad targeting.
- “decaf coffee” is a genuine leak. Your ASIN earns the clicks but a competitor captures the purchase. That points at price, reviews, or content losing the buyer after the click. This is the highest-value row to investigate, you are paying (in ad spend or organic rank) to send buyers who then convert elsewhere.
- “single origin” is a content / variation mismatch. The variety pack ranks for a single-origin query. Buyers searching “single origin” want the Ethiopia bag, not a mixed pack. Improving the single-origin listing’s relevance for that term recovers intent-matched demand.
- Aligned rows are the baseline, not the insight. “ground coffee” and “coffee gift set” convert on the right ASIN. They confirm the engine works; the value is in the misaligned rows.
- This is a diagnostic card with no alert. It does not fire a threshold; it is a worklist you read during search and advertising reviews. Pair it with the search-term cards below to turn rows into actions.
Sibling cards merchants should reference together
This card is the bridge between visibility and sales; read it with:| Card | Why pair it with ASIN Conversion Rank by Query |
|---|---|
| Search Query Share (Brand) | Tells you how much of branded search you own; this card tells you which ASIN converts it. |
| Top Branded Search Terms | The branded queries feeding this table. |
| Top Non-Branded Search Terms | The non-branded discovery queries where conversion-rank leaks matter most. |
| Organic vs Ad Sales Share | Separates whether the conversion came from paid placement or organic rank. |
| Brand Registry Coverage | This card needs Brand Registry; coverage gaps explain missing data. |
| Top ASINs by Revenue | Cross-check whether your top revenue ASINs are also the ones winning their queries. |
Reconciling against Amazon Seller Central
Where to look in Amazon Seller Central:Seller Central → Brands → Brand Analytics → Search Query Performance (and the Search Catalog Performance / Top Search Terms reports). These show, per query, the ASINs earning clicks and conversions, which is the source for this card.Brand Analytics is only available to Brand Registry enrolled sellers, and the reports are aggregated and anonymised by Amazon. Timing, settlement, and reporting-lag table:
| Topic | Detail |
|---|---|
| Timezone | Brand Analytics reports use Amazon’s reporting calendar for the marketplace; Vortex IQ aligns its 30D window to those reporting periods as closely as the data allows. |
| Reporting cadence | Brand Analytics reports are released on Amazon’s schedule (often weekly / periodic), not real time. The card refreshes when new Brand Analytics data is available, so it can lag live sales. |
| Aggregation / anonymisation | Amazon aggregates and anonymises Brand Analytics. Figures are relative ranks and shares, not exact per-buyer counts, so the card cannot be reconciled to individual orders. |
| Brand Registry dependency | If enrolment lapses or an ASIN is not under your brand, it drops out of Brand Analytics and out of this card. |
| Reason | Direction | Why |
|---|---|---|
| Reporting-period alignment | Either | Brand Analytics uses its own period boundaries; a 30D window will not always align exactly to Amazon’s weekly buckets. |
| Aggregation method | Either | The card derives a conversion rank from Amazon’s share metrics; different aggregation choices shift the ordering at the margin. |
| Data freshness | Ours may lag | Brand Analytics releases periodically; the card shows the latest available period, which can trail recent sales. |
| ASIN-set scope | Either | If the card focuses on your top revenue ASINs, low-volume ASINs Amazon still lists for a query may be excluded. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
google-analytics.revenue-trend | Different search universe. GA4 sees your DTC site search and Google organic; Amazon Brand Analytics sees on-Amazon search. Independent populations. | A query strong on Amazon may be weak on Google and vice versa; do not expect the rankings to match. |
shopify.total_revenue | Independent channel. On-Amazon conversion does not appear in Shopify. | No reconciliation; use to understand where search demand converts across channels. |