Skip to main content
Card class: Non-HeroCategory: Marketplace

At a glance

ASIN Conversion Rank by Query is a brand analytics & search metric tracked from Amazon (Selling Partner) data. It surfaces operational signal at the brand analytics & search layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Brand Analytics & Search category to build a complete diagnostic picture; cross-reference the related cards listed below for context.
What it countsASIN Conversion Rank by Query as exposed by the Amazon (Selling Partner) integration. The metric is computed from the latest available data and refreshed on the standard data refresh.
Sample typeBackend API data from Amazon (Selling Partner), refreshed on the standard data refresh.
Why it mattersThe metric appears in the Brand Analytics & Search category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities.
Reading the valueCompare the current period to the prior period to identify direction. Cross-reference siblings for the full diagnostic picture.
Currencynumber
Time window30D
Alert trigger—
Sentiment keyamzn_conversion_rank
Rolesowner, marketing

Calculation

Calculated automatically from your Amazon (Selling Partner) 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 representative reading of ASIN Conversion Rank by Query for a typical merchant on Amazon (Selling Partner). The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

Sibling cards merchants should reference together

CardWhy merchants reach for it
amzn_organic_vs_ad_shareBrand Analytics & Search sibling: Organic vs Ad Sales Share.
amzn_search_query_shareBrand Analytics & Search sibling: Search Query Share (Brand).
amzn_top_branded_keywordsBrand Analytics & Search sibling: Top Branded Search Terms.
amzn_top_non_branded_keywordsBrand Analytics & Search sibling: Top Non-Branded Search Terms.
ama_aovSales sibling: Average Order Value.

Reconciling against the vendor’s own dashboard

Where to look in Amazon (Selling Partner)‘s own dashboard: The Amazon (Selling Partner) dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:
ReasonDirectionWhat to do
Period boundary. Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods.VariableMatch the period range.
Time zone. Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone.MarginalConfirm time zone match.
Filter scope. Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view.VariableMatch filter settings.
Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does ASIN Conversion Rank by Query update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. Q: Why does my Amazon (Selling Partner) dashboard show a different number? The most common reasons are period-boundary differences (Vortex IQ uses 30-day rolling vs vendor’s calendar months), time-zone alignment, and filter scope (profile-level vs vendor’s all-account view). Match these settings before assuming a real divergence. Q: How does ASIN Conversion Rank by Query relate to other brand analytics & search metrics? Track this card alongside the siblings listed above to build a complete picture. Single-metric reads can mislead; the diagnostic value is in the cross-reference. Q: Can I customise the alert threshold? Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust to match your business baseline rather than relying on the generic default.

Tracked live in Vortex IQ Nerve Centre

ASIN Conversion Rank by Query is one of hundreds of KPI pulses Vortex IQ tracks across Amazon (Selling Partner) and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.