App Marketplace Metrics Glossary

Plain-language definitions for every metric AppRanks publishes across public app, audit, and comparison pages. This glossary explains what each number means, how we calculate it, and where it appears, so you can read our rankings and trend charts with confidence. Terms cover ratings and review counts, marketplace rank, visibility and velocity measures, and the audit scoring rubric. Each definition links directly to the surface where the metric is shown so you can see it in real context.

Ranking & visibility metrics

How AppRanks tracks where an app sits in the marketplace — keyword rankings, category positions, and featured placements.

Marketplace ranking: Marketplace ranking is the position an app holds on a category leaderboard — for example, #4 of 218 in Shopify's Reviews category. The marketplace itself decides the order using a multi-signal algorithm: install velocity (how fast new merchants are installing in the recent window) typically dominates, followed by average rating, review count, listing freshness (recent updates to title, description, screenshots, pricing), and category fit (how cleanly the app's tags match its leaderboard category). On Shopify specifically, recent install momentum and a sustained rating at or above 4.5 are the two strongest single levers a developer can pull. WordPress weights active install count more heavily; Atlassian weights Spotlight/badge membership; Salesforce weights the publisher's tier. Knowing which signal moves rank on your platform tells you which optimization compounds — install-velocity platforms reward acquisition pushes, rating-heavy platforms reward post-install support investment.
Category position: The numerical rank an app holds within a single marketplace category — for example, position #4 in "Reviews" out of 218 tracked apps in that category. Position is computed by the marketplace and mirrored exactly by AppRanks; we don't re-rank or re-weight. Each app can hold multiple positions (one per category it's listed in), and the positions move daily as the marketplace recomputes its leaderboards. AppRanks tracks position changes across 7d, 30d, and 90d windows so you can see whether an app is climbing, stable, or sliding. A drop of 5+ positions in a week typically maps to either a competitor surge or an app's own listing-quality regression (slower load, missing screenshots, support issues that triggered low reviews); correlating the position-change date with the listing-change history usually identifies the cause within a few hours of investigation.
Category leader: The top-ranked app in a marketplace category — typically the #1 position on the public category leaderboard. AppRanks computes category leadership directly from the marketplace's published leaderboard data — there's no AppRanks-invented category-leader designation. Leadership is per-category, not per-platform: an app can be #1 in "Pre-orders" while ranking #50 in "Marketing". Category leaders typically have 5-10x the install velocity of the median app in the same category, and they receive disproportionate featured-section placement (which reinforces the leadership). For new merchants, the category leader is usually a safe default — it has been validated by the largest user base — but it's not always the best fit, since leaders often skew toward feature-rich and pricier offerings. Always compare leaders against the top 3-5 alternatives before committing; the audit rubric scores both leadership and merchandising quality independently.
Featured placement: An editorial slot on the marketplace where an app gets surfaced beyond its organic ranking — typically a hero card on a category page, a "new and trending" rail, a Spotlight badge, or a Cloud Fortified / Top Vendor distinction. Featured placements are a strong install-velocity signal because they reach merchants who weren't searching for the app by name. AppRanks tracks featured-section memberships per platform; when an app loses a featured slot, the public app page shows the change in the "Featured Placements" section with the date of the change. On Shopify the most-watched featured rails are the App Store homepage carousel, the category Spotlights, and the Built for Shopify badge. On Atlassian the equivalent is Spotlight membership combined with Cloud Fortified status. Losing a featured slot often precedes a measurable install-velocity drop — typically visible in the next 3-10 days of velocity data.

Review & rating metrics

User feedback signals — review counts, velocity (recent activity), and rating distributions.

Review velocity: The number of new reviews an app received over a rolling window — typically 7, 30, and 90 days. Velocity is more diagnostic than total review count for established apps: a 5-year-old listing with 10,000 reviews and a v7d of 0 is signaling stagnation, while one with v7d of 50 is signaling healthy momentum. AppRanks calculates velocity by diffing successive review-count snapshots, so it captures real new reviews rather than estimating from rating-change patterns. The diff approach also means we capture review removals (when a marketplace deletes spam) — these surface as negative-velocity blips. For a Shopify app with 100 reviews and a v30d of 12, the rule of thumb is healthy: roughly one new review every 2-3 days, putting it on the same growth curve as the category median. We display velocity as a raw count rather than a rate so it stays comparable across apps with very different rating bases.
Review velocity (7-day): The number of new reviews an app received in the trailing 7 days. The 7-day window is the most sensitive of the three velocity ranges AppRanks publishes (7d, 30d, 90d) — it surfaces the most recent momentum but also the most noise. A v7d of 0 on a previously-active app warrants attention but isn't immediately a problem (review batches arrive irregularly); a v7d of 0 sustained for two consecutive weeks is a real stagnation signal. Conversely, a v7d spike often correlates with a recent feature launch, a press mention, or a marketplace promotion — context worth checking against the app's update history. Compare v7d against v30d to read momentum: v7d × 4 ≈ v30d means flat; v7d × 4 > v30d means accelerating; v7d × 4 < v30d means decelerating from a recent peak.
Review count: The total number of public, marketplace-published reviews an app has received over its lifetime. Review count is a coarser signal than review velocity — a 10-year-old app with 50,000 reviews may have flat current momentum, while a 6-month-old app with 200 reviews could be growing rapidly. AppRanks displays both metrics on every app page so you can disambiguate. We diff successive snapshots to track velocity, and we flag anomalous drops (which usually mean the marketplace removed reviews flagged as fake). Review count includes only reviews still visible on the source marketplace at the most recent crawl — deleted reviews drop out of the count immediately on next refresh, no hidden cache. For comparing two apps in the same category, look at both the count AND the velocity; a high-count low-velocity app may be coasting on reputation that's eroding.
Rating distribution: The breakdown of an app's reviews across the 1-5 star scale, expressed as counts or percentages. A 4.8★ average can come from many shapes — 95% 5★ + 5% 1★ (polarized), 75% 5★ + 20% 4★ + 5% other (consensus), or a long tail of 3-4★ reviews (lukewarm). The distribution shape matters more than the headline average for long-term trust; a polarized listing usually has a feature gap or a setup friction that triggers occasional 1-star outliers, which compound over time into a steeper churn curve. AppRanks displays the distribution as a horizontal bar chart on the ratings & reviews section of every app page, and the audit page surfaces it under "Rating health". Compare the same shape across competitors: an app with the same average rating but cleaner distribution is usually the safer choice for new merchants — fewer angry-review surprises after install.

Pricing metrics

How AppRanks classifies an app's pricing posture — tier structure and free-plan availability.

Pricing tier: A named price level on an app's pricing page — typically Free, Starter, Pro, Business, Enterprise, or platform-specific names. Tiers map to capacity gates: number of orders processed, number of products synced, number of seats, daily API calls. AppRanks mirrors the marketplace's pricing tiers exactly as published, including any platform-specific variations (e.g., Shopify Plus surcharges, annual discount percentages, free trial durations). Tier names + prices refresh every 12-24 hours from the source marketplace; if you see a discrepancy with the live listing, the gap is one refresh cycle at most. We do not infer or extrapolate tier values when an app uses custom pricing ("Contact us") — the field reads as such and the audit penalizes opacity. For comparing apps with different tier structures, the side-by-side compare page normalizes by use-case capacity rather than tier name.
Free tier: A pricing level that costs $0 with no time limit on the marketplace listing. A free tier is distinct from a free trial (which expires after a fixed window) and from freemium gating (which restricts core functionality until a paid upgrade). AppRanks's free-tier classification looks for an explicit $0 plan in the marketplace's pricing data; ambiguous cases ("Contact for pricing", "Pricing on request") are reported as unknown rather than treated as free. Free tiers are a strong adoption signal — apps with genuine free tiers typically have 3-5x the install velocity of paid-only apps in the same category. They're also a strong audit-score factor: AppRanks's audit rubric awards points for transparent free-tier availability because it correlates with merchant trust and reduces install friction. Always confirm the free-tier specifics on the source marketplace before installing — limits and upgrade triggers vary widely.

Audit metrics

Signals from AppRanks' independent listing audit — overall score and component checks.

Audit score: An out-of-100 score AppRanks publishes for each tracked app's listing, computed against a fixed rubric covering listing completeness, rating health, review velocity, merchandising, and ranking consistency. The rubric is identical for every app on a given marketplace — we do not weight by paid relationship, traffic, or partnership tier. The exact category weightings and per-check criteria are documented inline on each audit page so a reader can verify exactly which signals moved the score. A score of 85+ generally means the listing has no critical gaps and competes well in its category; 60-85 means meaningful merchandising work is available; below 60 typically signals missing screenshots, thin descriptions, or rating-velocity issues that suppress install conversion. Audit scores refresh on demand when underlying inputs change. The audit also produces a prioritized recommendation list so a developer can see exactly which fixes would move the score most.
Listing audit: An automated, rubric-driven evaluation of a single app's marketplace listing. AppRanks's listing audit checks the icon, screenshots, description, category coverage, pricing transparency, review-base health, and ranking consistency. The audit is identical for every app on a platform — same checks, same weights — so audit scores are directly comparable. Each audit also produces a prioritized recommendation list so a developer can see exactly which fixes would move the score most. Audits refresh on demand or when underlying inputs change materially. The audit framework is calibrated by spot-checking 100+ real listings before and after a published score change; we re-publish the rubric whenever a check is added or weighted differently rather than silently adjusting and re-scoring history. Apps that disagree with a score can request a manual recheck via [email protected] and we investigate within one refresh cycle (24h max).

Developer & listing metrics

Cross-cutting signals about the app's publisher, installed base, and platform certifications.

Developer profile: The marketplace identity of the company or person publishing an app — a Shopify Partner, an Atlassian Partner, a WordPress contributor, etc. AppRanks tracks per-developer aggregates: total apps published, average rating across the portfolio, total active installs across the catalog, and response patterns to user reviews. A developer with 20 apps and a 4.8★ portfolio average has different signals than one with 1 app at 4.9★. We surface developer-level context on each app page (linked to /developers/{platform}/{slug}) so merchants evaluating an app can see whether the publisher has a track record or this is a first listing. A first-time developer isn't a red flag on its own — we treat it as a context signal, not an audit deduction. The portfolio view also surfaces sibling apps from the same publisher, which often share infrastructure and support quality patterns.
Active installs: The current number of stores that have an app installed and not uninstalled, as reported by the source marketplace. Active installs is a stronger growth signal than total downloads because it accounts for churn — an app with 50,000 downloads but 5,000 active installs has either a serious onboarding problem or a sunset use case. AppRanks displays the figure when the marketplace exposes it (Shopify shows it on most listings; Atlassian and Zendesk surface it for Cloud Fortified / Top Vendor apps only). We do not estimate when the marketplace doesn't publish the number — a missing install count is reported as unknown rather than a guess. Compare active-install velocity to review velocity to detect divergence: high installs + low reviews can signal a non-vocal user base or a friction-free workflow; the inverse usually means a churn problem.
Built for Shopify badge: A Shopify-conferred quality designation that signals an app meets Shopify's published quality and performance criteria — fast initial load, accessible UI, good admin integration, no support backlogs. The badge is granted by Shopify (not earned through AppRanks scoring) and shows up as a green checkmark on the listing. Built for Shopify apps typically have 2-3x install velocity of unbadged apps in the same category and receive priority placement in some featured rails. Losing the badge usually precedes a measurable install drop — Shopify revokes when an app falls below the quality bar (slow performance, support response times, accessibility regressions), and the revocation is publicly visible. AppRanks tracks badge state changes per app; the change date appears in the "Featured Placements" section. Equivalent designations on other platforms include Atlassian's Cloud Fortified and Zendesk's Top Vendor.

Other metrics

Spotlight badge: The Spotlight badge is Atlassian Marketplace's curated-editorial designation, awarded to apps Atlassian's marketplace team selects for visibility in the rotating featured rails on Atlassian's homepage and category browse pages. Unlike the algorithmic Bestseller and Rising Star badges, Spotlight is editorially chosen — Atlassian highlights apps for thematic reasons (a security focus, an accessibility milestone, a recent major launch) rather than pure sales velocity. The badge is publicly visible on the listing tile, on the app's detail page, and inside Atlassian's category leaderboards, and it disappears when Atlassian rotates a fresh cohort in (typically every 4-6 weeks; some thematic Spotlights run shorter). AppRanks tracks Spotlight assignments via Atlassian's `?marketingLabel=` URL parameter and surfaces gain/loss events in the app's Featured Placements section with the exact crawl date. The Shopify-side analogue is the editorial Staff Pick rail and the New & Noteworthy collection; the AppRanks data model unifies both under a single "editorial featured" event type so cross-platform comparisons stay clean.
Bestseller badge: The Bestseller badge is Atlassian Marketplace's algorithmic top-installs designation, computed from rolling install velocity within each marketplace category. The badge typically lands on apps that have accumulated 6-12+ months of sustained install momentum, often with thousands of active installs and a feedback flywheel of reviews driving more installs. Unlike Spotlight (editorial selection) or Rising Star (relative-growth percentile), Bestseller is a pure-volume award — it strongly favors mature apps with broad distribution, and it tends to be sticky: once an app has the badge, it usually keeps it for many quarters because the badge itself drives the install velocity that sustains eligibility. Zendesk Marketplace issues an analogous Bestseller badge using a similar volume-based computation, and AppRanks treats both under one unified data model. AppRanks tracks Bestseller state per app per platform and surfaces gain/loss events with crawl-date attribution; loss is rare and typically correlates with a major competitor surpassing the app's install velocity rather than with the badged app itself declining.
Rising Star badge: The Rising Star badge is Atlassian Marketplace's velocity-of-growth designation, awarded to apps showing the strongest relative install acceleration regardless of absolute volume. Unlike Bestseller (which favors mature, high-volume apps) or Spotlight (which is editorially curated), Rising Star surfaces apps in the steep portion of their growth curve — typically 6-18 months post-launch with strong week-over-week acceleration on installs and reviews. The badge rotates faster than Bestseller because growth percentages compress as install volume scales: an app that earns Rising Star at 500 installs per week will usually graduate out of the rotation within 2-3 quarters as its growth normalizes against a larger base. AppRanks tracks Rising Star assignments via Atlassian's `?marketingLabel=rising-star` endpoint and records gain/loss events with crawl-date attribution. The Shopify-side analogue is the New & Noteworthy rail and the WooCommerce Top New Extensions collection; both reward early-momentum apps with a similar visibility-vs-velocity tradeoff. Cross-platform, AppRanks unifies these into a single "emerging" event type so investor watchlists can span marketplaces.
Competitor moat: A competitor moat is the durable advantage that prevents another app from displacing yours in the same marketplace category — typically a combination of accumulated reviews, install-velocity inertia, exclusive integrations, and feature depth that newer entrants can't trivially match. AppRanks frames marketplace strategy in moat terms because category dynamics are non-linear: the top-3 apps in a mature category capture 60-80% of new installs, and the gap usually widens once an app crosses a threshold of ~500 reviews and 12+ months of consistent velocity. Watching your moat means tracking three signals together: review-count delta vs the next-closest competitor, weekly install velocity differential, and feature-parity gap measured by the AppRanks audit score. A moat narrowing on any of these three (especially review-count delta) is the earliest signal that incumbents need to invest in differentiation rather than coast.
Review burst: A review burst is an abrupt spike in an app's review-arrival rate — typically defined as a single-day or 7-day review count that exceeds the trailing-90-day daily average by 3x or more. Review bursts often signal a triggering event: a feature launch driving early adopters to leave first impressions, a press mention or marketplace newsletter feature pulling fresh visitor traffic, or — less happily — a bug or pricing change concentrating user feedback into a narrow window. AppRanks distinguishes positive bursts (rating ≥ trailing average) from negative bursts (rating < trailing average) so the same magnitude metric reads differently depending on the underlying sentiment. Tracking burst patterns over time surfaces the cadence of product investment and incident response: a developer team running 6 launches per year with positive bursts each time is in a different operating rhythm than one with two large negative bursts and slow recovery between them.
Install velocity: Install velocity is the rate at which new merchants install an app over a rolling window — typically expressed as installs per day, week, or month. On Shopify, install velocity is widely understood as the single strongest signal feeding the App Store's ranking algorithm: a sharp acceleration in the trailing 7-30 day window typically translates to category-position climbs within 1-2 ranking cycles. Atlassian, WordPress, and Zendesk apply similar velocity weighting, though with different lookback windows and smoothing functions that the marketplaces don't publish. Install velocity is distinct from total active installs — a mature app with 50,000 active installs and zero weekly velocity is stable but stagnant; a 6-month-old app at 2,000 installs adding 150 per week is gaining ground. AppRanks does not compute install velocity directly because most marketplaces don't expose per-day install counts publicly; we infer momentum from category-position trajectory and review-velocity correlation.
Search relevance: Search relevance is how closely a marketplace listing's title, description, tags, and keywords match the queries merchants type into the marketplace search bar. Every marketplace runs its own search index — Shopify's App Store, Atlassian Marketplace, WordPress.org, Zendesk Marketplace — and each weights title-match, description-match, category-match, and install-velocity-of-recent-clickers differently. The common pattern across platforms: an exact-phrase match in the title outranks a partial match in the description, and synonyms compete unless the listing explicitly enumerates them. For developers, search relevance is the highest-ROI listing lever because it determines the universe of queries the listing can rank for at all. A listing with a generic title and no tag coverage is invisible for tail queries no matter how strong its install velocity. AppRanks does not run a proprietary relevance score; we surface the title, description, tags, and category data as scraped so developers can compare their listing's keyword coverage against category competitors.
Listing health: Listing health is an aggregate read of how complete and well-maintained an app's marketplace listing is across the signals merchants and the marketplace's own quality systems look at: title length, description word count, screenshot count and quality, video presence, last-update freshness, support response rate, and pricing transparency. A listing that scores well on every completeness signal converts marketplace impressions to installs at 2-4x the rate of a listing missing screenshots or with a thin description, even when rating and review count are identical. Most marketplaces don't publish a single listing-health number — instead, each signal feeds the ranking algorithm independently — but the concept is cross-platform: Shopify, Atlassian, WordPress, and Zendesk all reward listings that present a complete, recently-updated, support-responsive picture. AppRanks computes a 0-100 audit score that aggregates these listing-health signals into one number; the audit page surfaces the per-signal breakdown so developers can see which specific gaps are dragging the headline.
Category saturation: Category saturation is how crowded a marketplace category is relative to merchant demand — typically expressed as the number of competing apps within a single category divided by the marketplace's total app count, or as the share of top-50 installs held by the top 5 apps. A saturated category (e.g., Shopify's Email marketing with 600+ apps and 70% installs concentrated in the top 10) has high entry difficulty: new apps face an entrenched moat of incumbents whose accumulated reviews and install velocity self-reinforce ranking. An under-saturated category (a niche with 20-40 apps and a flatter install distribution) has lower entry difficulty and more upside for differentiation. Cross-platform, the same pattern holds: Atlassian, WordPress, and Zendesk all show power-law install distribution per category. AppRanks surfaces per-category app counts and top-app concentration on category pages so developers picking a category to build in can read saturation directly.
App store optimization (ASO): App store optimization (ASO) is the industry-canonical acronym for the discipline of improving a marketplace listing's organic visibility — covering keyword research, title and description tuning, screenshot and video optimization, category selection, pricing presentation, review-base management, and the operational hygiene (update cadence, support responsiveness) that marketplace ranking algorithms reward. ASO originated in mobile app stores (Apple App Store, Google Play) and the same principles transfer to SaaS marketplaces like Shopify, Atlassian, WordPress, and Zendesk, with platform-specific weighting differences. Effective ASO is iterative: change one listing element, measure category-position and install-velocity shifts over the next 7-14 days, then iterate. AppRanks supports ASO workflows on every audit page (/audit/{platform}/{slug}) with a per-check rubric grading title length, description completeness, screenshot count, category fit, pricing transparency, and update freshness — the developer can see exactly which ASO lever moves their audit score the most before investing in the listing change.
Review recency: The freshness of an app's most recent reviews — measured as days since the latest review and as the share of the total review pool that landed in the last 30 days. Marketplaces increasingly weight recency in their ranking algorithms because a 4.7 average accumulated over five years is a weaker signal than the same 4.7 from the last 90 days: it tells the algorithm the listing is still being adopted and the rating reflects the current product, not a legacy version. AppRanks surfaces review recency on every audit page alongside the headline rating so an operator can see at a glance whether the rating reflects today's product or a frozen historical baseline. A common failure mode: a once-popular app holds its high average rating long after merchant adoption has stalled — recency exposes that decay months before total review count would.
Rating deltas: The signed change in an app's average rating across rolling time windows — typically 7-day, 30-day, and 90-day deltas. A rating delta of +0.03 over 7 days means the average climbed from (e.g.) 4.62 → 4.65; a delta of -0.10 means it dropped. Small numbers carry large information because a marketplace listing with 500+ reviews moves slowly under random noise: a 0.05-point drop in 7 days usually represents 20-50 negative reviews landing in concentrated time, not statistical drift — a signal worth investigating BEFORE the headline rating crosses a visible threshold or the marketplace's algorithm reweights the listing. AppRanks shows the per-window delta alongside the absolute rating on every app page so a stable 4.6 with a -0.08 v7d gets flagged differently than a stable 4.6 with a +0.02 v7d. The delta column is also where most early-warning signals first surface — a soft launch failing to convert, a competitor pulling installs away, or a quality regression triggering negative feedback.
Rank volatility: The amplitude of an app's category-position changes over a rolling window — measured as the standard deviation of daily rank across (typically) the last 30 days. A low-volatility app moves ±1-2 positions per day in a steady channel; a high-volatility app may move ±10-20 positions per day. Volatility is independent from headline rank: an app stable at #4 and an app cycling 2-15 may both have the same 30-day median rank but very different competitive positions. AppRanks surfaces volatility on the trends page and inside the per-app rank history so an operator can tell whether a #5 placement is a defended position or a churning slot. High volatility is usually a signal that the marketplace ranking algorithm is weighing a metric (e.g., very-recent install velocity, freshness of reviews) that the app's underlying signals can't sustain.

Missing a term you'd like defined? Email [email protected] and we'll add it (or correct one that's wrong).

App Marketplace Metrics Glossary

Ranking & visibility metrics

How AppRanks tracks where an app sits in the marketplace — keyword rankings, category positions, and featured placements.

Marketplace ranking

Marketplace ranking is the position an app holds on a category leaderboard — for example, #4 of 218 in Shopify's Reviews category. The marketplace itself decides the order using a multi-signal algorithm: install velocity (how fast new merchants are installing in the recent window) typically dominates, followed by average rating, review count, listing freshness (recent updates to title, description, screenshots, pricing), and category fit (how cleanly the app's tags match its leaderboard category). On Shopify specifically, recent install momentum and a sustained rating at or above 4.5 are the two strongest single levers a developer can pull. WordPress weights active install count more heavily; Atlassian weights Spotlight/badge membership; Salesforce weights the publisher's tier. Knowing which signal moves rank on your platform tells you which optimization compounds — install-velocity platforms reward acquisition pushes, rating-heavy platforms reward post-install support investment.

Where you see it on AppRanks: Every public app page (/apps/{platform}/{slug}) under "Category Rankings".

Read full definition of Marketplace ranking →

Category position

The numerical rank an app holds within a single marketplace category — for example, position #4 in "Reviews" out of 218 tracked apps in that category. Position is computed by the marketplace and mirrored exactly by AppRanks; we don't re-rank or re-weight. Each app can hold multiple positions (one per category it's listed in), and the positions move daily as the marketplace recomputes its leaderboards. AppRanks tracks position changes across 7d, 30d, and 90d windows so you can see whether an app is climbing, stable, or sliding. A drop of 5+ positions in a week typically maps to either a competitor surge or an app's own listing-quality regression (slower load, missing screenshots, support issues that triggered low reviews); correlating the position-change date with the listing-change history usually identifies the cause within a few hours of investigation.

Where you see it on AppRanks: App page "Category Rankings" section, category page leaderboards.

Read full definition of Category position →

Category leader

The top-ranked app in a marketplace category — typically the #1 position on the public category leaderboard. AppRanks computes category leadership directly from the marketplace's published leaderboard data — there's no AppRanks-invented category-leader designation. Leadership is per-category, not per-platform: an app can be #1 in "Pre-orders" while ranking #50 in "Marketing". Category leaders typically have 5-10x the install velocity of the median app in the same category, and they receive disproportionate featured-section placement (which reinforces the leadership). For new merchants, the category leader is usually a safe default — it has been validated by the largest user base — but it's not always the best fit, since leaders often skew toward feature-rich and pricier offerings. Always compare leaders against the top 3-5 alternatives before committing; the audit rubric scores both leadership and merchandising quality independently.

Where you see it on AppRanks: App page "Category Rankings" (#1 entries), category page leaderboards.

Read full definition of Category leader →

Featured placement

An editorial slot on the marketplace where an app gets surfaced beyond its organic ranking — typically a hero card on a category page, a "new and trending" rail, a Spotlight badge, or a Cloud Fortified / Top Vendor distinction. Featured placements are a strong install-velocity signal because they reach merchants who weren't searching for the app by name. AppRanks tracks featured-section memberships per platform; when an app loses a featured slot, the public app page shows the change in the "Featured Placements" section with the date of the change. On Shopify the most-watched featured rails are the App Store homepage carousel, the category Spotlights, and the Built for Shopify badge. On Atlassian the equivalent is Spotlight membership combined with Cloud Fortified status. Losing a featured slot often precedes a measurable install-velocity drop — typically visible in the next 3-10 days of velocity data.

Where you see it on AppRanks: App page "Featured placements" section.

Read full definition of Featured placement →

Review & rating metrics

User feedback signals — review counts, velocity (recent activity), and rating distributions.

Review velocity

The number of new reviews an app received over a rolling window — typically 7, 30, and 90 days. Velocity is more diagnostic than total review count for established apps: a 5-year-old listing with 10,000 reviews and a v7d of 0 is signaling stagnation, while one with v7d of 50 is signaling healthy momentum. AppRanks calculates velocity by diffing successive review-count snapshots, so it captures real new reviews rather than estimating from rating-change patterns. The diff approach also means we capture review removals (when a marketplace deletes spam) — these surface as negative-velocity blips. For a Shopify app with 100 reviews and a v30d of 12, the rule of thumb is healthy: roughly one new review every 2-3 days, putting it on the same growth curve as the category median. We display velocity as a raw count rather than a rate so it stays comparable across apps with very different rating bases.

Where you see it on AppRanks: App page "Ratings and reviews" section, audit page "Rating health" check.

Read full definition of Review velocity →

Review velocity (7-day)

The number of new reviews an app received in the trailing 7 days. The 7-day window is the most sensitive of the three velocity ranges AppRanks publishes (7d, 30d, 90d) — it surfaces the most recent momentum but also the most noise. A v7d of 0 on a previously-active app warrants attention but isn't immediately a problem (review batches arrive irregularly); a v7d of 0 sustained for two consecutive weeks is a real stagnation signal. Conversely, a v7d spike often correlates with a recent feature launch, a press mention, or a marketplace promotion — context worth checking against the app's update history. Compare v7d against v30d to read momentum: v7d × 4 ≈ v30d means flat; v7d × 4 > v30d means accelerating; v7d × 4 < v30d means decelerating from a recent peak.

Where you see it on AppRanks: App page "Ratings and reviews" section, audit page "Review velocity" check.

Read full definition of Review velocity (7-day) →

Review count

The total number of public, marketplace-published reviews an app has received over its lifetime. Review count is a coarser signal than review velocity — a 10-year-old app with 50,000 reviews may have flat current momentum, while a 6-month-old app with 200 reviews could be growing rapidly. AppRanks displays both metrics on every app page so you can disambiguate. We diff successive snapshots to track velocity, and we flag anomalous drops (which usually mean the marketplace removed reviews flagged as fake). Review count includes only reviews still visible on the source marketplace at the most recent crawl — deleted reviews drop out of the count immediately on next refresh, no hidden cache. For comparing two apps in the same category, look at both the count AND the velocity; a high-count low-velocity app may be coasting on reputation that's eroding.

Where you see it on AppRanks: App page hero (rating + count), category leaderboard rankings.

Read full definition of Review count →

Rating distribution

The breakdown of an app's reviews across the 1-5 star scale, expressed as counts or percentages. A 4.8★ average can come from many shapes — 95% 5★ + 5% 1★ (polarized), 75% 5★ + 20% 4★ + 5% other (consensus), or a long tail of 3-4★ reviews (lukewarm). The distribution shape matters more than the headline average for long-term trust; a polarized listing usually has a feature gap or a setup friction that triggers occasional 1-star outliers, which compound over time into a steeper churn curve. AppRanks displays the distribution as a horizontal bar chart on the ratings & reviews section of every app page, and the audit page surfaces it under "Rating health". Compare the same shape across competitors: an app with the same average rating but cleaner distribution is usually the safer choice for new merchants — fewer angry-review surprises after install.

Where you see it on AppRanks: App page "Ratings and reviews" section, audit page "Rating health" check.

Read full definition of Rating distribution →

Pricing metrics

How AppRanks classifies an app's pricing posture — tier structure and free-plan availability.

Pricing tier

A named price level on an app's pricing page — typically Free, Starter, Pro, Business, Enterprise, or platform-specific names. Tiers map to capacity gates: number of orders processed, number of products synced, number of seats, daily API calls. AppRanks mirrors the marketplace's pricing tiers exactly as published, including any platform-specific variations (e.g., Shopify Plus surcharges, annual discount percentages, free trial durations). Tier names + prices refresh every 12-24 hours from the source marketplace; if you see a discrepancy with the live listing, the gap is one refresh cycle at most. We do not infer or extrapolate tier values when an app uses custom pricing ("Contact us") — the field reads as such and the audit penalizes opacity. For comparing apps with different tier structures, the side-by-side compare page normalizes by use-case capacity rather than tier name.

Where you see it on AppRanks: App page "Pricing plans" section, compare page pricing matrix.

Read full definition of Pricing tier →

Free tier

A pricing level that costs $0 with no time limit on the marketplace listing. A free tier is distinct from a free trial (which expires after a fixed window) and from freemium gating (which restricts core functionality until a paid upgrade). AppRanks's free-tier classification looks for an explicit $0 plan in the marketplace's pricing data; ambiguous cases ("Contact for pricing", "Pricing on request") are reported as unknown rather than treated as free. Free tiers are a strong adoption signal — apps with genuine free tiers typically have 3-5x the install velocity of paid-only apps in the same category. They're also a strong audit-score factor: AppRanks's audit rubric awards points for transparent free-tier availability because it correlates with merchant trust and reduces install friction. Always confirm the free-tier specifics on the source marketplace before installing — limits and upgrade triggers vary widely.

Where you see it on AppRanks: App page hero ("Free plan available" pricing hint), pricing comparison.

Read full definition of Free tier →

Audit metrics

Signals from AppRanks' independent listing audit — overall score and component checks.

Audit score

An out-of-100 score AppRanks publishes for each tracked app's listing, computed against a fixed rubric covering listing completeness, rating health, review velocity, merchandising, and ranking consistency. The rubric is identical for every app on a given marketplace — we do not weight by paid relationship, traffic, or partnership tier. The exact category weightings and per-check criteria are documented inline on each audit page so a reader can verify exactly which signals moved the score. A score of 85+ generally means the listing has no critical gaps and competes well in its category; 60-85 means meaningful merchandising work is available; below 60 typically signals missing screenshots, thin descriptions, or rating-velocity issues that suppress install conversion. Audit scores refresh on demand when underlying inputs change. The audit also produces a prioritized recommendation list so a developer can see exactly which fixes would move the score most.

Where you see it on AppRanks: Every audit page (/audit/{platform}/{slug}) — score in the page title.

Read full definition of Audit score →

Listing audit

An automated, rubric-driven evaluation of a single app's marketplace listing. AppRanks's listing audit checks the icon, screenshots, description, category coverage, pricing transparency, review-base health, and ranking consistency. The audit is identical for every app on a platform — same checks, same weights — so audit scores are directly comparable. Each audit also produces a prioritized recommendation list so a developer can see exactly which fixes would move the score most. Audits refresh on demand or when underlying inputs change materially. The audit framework is calibrated by spot-checking 100+ real listings before and after a published score change; we re-publish the rubric whenever a check is added or weighted differently rather than silently adjusting and re-scoring history. Apps that disagree with a score can request a manual recheck via [email protected] and we investigate within one refresh cycle (24h max).

Where you see it on AppRanks: Audit pages (/audit/{platform}/{slug}) — every tracked app has one.

Read full definition of Listing audit →

Developer & listing metrics

Cross-cutting signals about the app's publisher, installed base, and platform certifications.

Developer profile

The marketplace identity of the company or person publishing an app — a Shopify Partner, an Atlassian Partner, a WordPress contributor, etc. AppRanks tracks per-developer aggregates: total apps published, average rating across the portfolio, total active installs across the catalog, and response patterns to user reviews. A developer with 20 apps and a 4.8★ portfolio average has different signals than one with 1 app at 4.9★. We surface developer-level context on each app page (linked to /developers/{platform}/{slug}) so merchants evaluating an app can see whether the publisher has a track record or this is a first listing. A first-time developer isn't a red flag on its own — we treat it as a context signal, not an audit deduction. The portfolio view also surfaces sibling apps from the same publisher, which often share infrastructure and support quality patterns.

Where you see it on AppRanks: App page hero ("By <developer>" link), developer profile pages.

Read full definition of Developer profile →

Active installs

The current number of stores that have an app installed and not uninstalled, as reported by the source marketplace. Active installs is a stronger growth signal than total downloads because it accounts for churn — an app with 50,000 downloads but 5,000 active installs has either a serious onboarding problem or a sunset use case. AppRanks displays the figure when the marketplace exposes it (Shopify shows it on most listings; Atlassian and Zendesk surface it for Cloud Fortified / Top Vendor apps only). We do not estimate when the marketplace doesn't publish the number — a missing install count is reported as unknown rather than a guess. Compare active-install velocity to review velocity to detect divergence: high installs + low reviews can signal a non-vocal user base or a friction-free workflow; the inverse usually means a churn problem.

Where you see it on AppRanks: App page hero (when available), audit page "Adoption" check.

Read full definition of Active installs →

Built for Shopify badge

A Shopify-conferred quality designation that signals an app meets Shopify's published quality and performance criteria — fast initial load, accessible UI, good admin integration, no support backlogs. The badge is granted by Shopify (not earned through AppRanks scoring) and shows up as a green checkmark on the listing. Built for Shopify apps typically have 2-3x install velocity of unbadged apps in the same category and receive priority placement in some featured rails. Losing the badge usually precedes a measurable install drop — Shopify revokes when an app falls below the quality bar (slow performance, support response times, accessibility regressions), and the revocation is publicly visible. AppRanks tracks badge state changes per app; the change date appears in the "Featured Placements" section. Equivalent designations on other platforms include Atlassian's Cloud Fortified and Zendesk's Top Vendor.

Where you see it on AppRanks: App page hero (when present), audit page badge check.

Read full definition of Built for Shopify badge →

Other metrics

Spotlight badge

The Spotlight badge is Atlassian Marketplace's curated-editorial designation, awarded to apps Atlassian's marketplace team selects for visibility in the rotating featured rails on Atlassian's homepage and category browse pages. Unlike the algorithmic Bestseller and Rising Star badges, Spotlight is editorially chosen — Atlassian highlights apps for thematic reasons (a security focus, an accessibility milestone, a recent major launch) rather than pure sales velocity. The badge is publicly visible on the listing tile, on the app's detail page, and inside Atlassian's category leaderboards, and it disappears when Atlassian rotates a fresh cohort in (typically every 4-6 weeks; some thematic Spotlights run shorter). AppRanks tracks Spotlight assignments via Atlassian's `?marketingLabel=` URL parameter and surfaces gain/loss events in the app's Featured Placements section with the exact crawl date. The Shopify-side analogue is the editorial Staff Pick rail and the New & Noteworthy collection; the AppRanks data model unifies both under a single "editorial featured" event type so cross-platform comparisons stay clean.

Where you see it on AppRanks: Atlassian app page "Featured Placements" section, app audit badge check.

Read full definition of Spotlight badge →

Bestseller badge

The Bestseller badge is Atlassian Marketplace's algorithmic top-installs designation, computed from rolling install velocity within each marketplace category. The badge typically lands on apps that have accumulated 6-12+ months of sustained install momentum, often with thousands of active installs and a feedback flywheel of reviews driving more installs. Unlike Spotlight (editorial selection) or Rising Star (relative-growth percentile), Bestseller is a pure-volume award — it strongly favors mature apps with broad distribution, and it tends to be sticky: once an app has the badge, it usually keeps it for many quarters because the badge itself drives the install velocity that sustains eligibility. Zendesk Marketplace issues an analogous Bestseller badge using a similar volume-based computation, and AppRanks treats both under one unified data model. AppRanks tracks Bestseller state per app per platform and surfaces gain/loss events with crawl-date attribution; loss is rare and typically correlates with a major competitor surpassing the app's install velocity rather than with the badged app itself declining.

Where you see it on AppRanks: Atlassian / Zendesk app page "Featured Placements" section, audit badge check.

Read full definition of Bestseller badge →

Rising Star badge

The Rising Star badge is Atlassian Marketplace's velocity-of-growth designation, awarded to apps showing the strongest relative install acceleration regardless of absolute volume. Unlike Bestseller (which favors mature, high-volume apps) or Spotlight (which is editorially curated), Rising Star surfaces apps in the steep portion of their growth curve — typically 6-18 months post-launch with strong week-over-week acceleration on installs and reviews. The badge rotates faster than Bestseller because growth percentages compress as install volume scales: an app that earns Rising Star at 500 installs per week will usually graduate out of the rotation within 2-3 quarters as its growth normalizes against a larger base. AppRanks tracks Rising Star assignments via Atlassian's `?marketingLabel=rising-star` endpoint and records gain/loss events with crawl-date attribution. The Shopify-side analogue is the New & Noteworthy rail and the WooCommerce Top New Extensions collection; both reward early-momentum apps with a similar visibility-vs-velocity tradeoff. Cross-platform, AppRanks unifies these into a single "emerging" event type so investor watchlists can span marketplaces.

Where you see it on AppRanks: Atlassian app page "Featured Placements" section, audit badge check.

Read full definition of Rising Star badge →

Competitor moat

A competitor moat is the durable advantage that prevents another app from displacing yours in the same marketplace category — typically a combination of accumulated reviews, install-velocity inertia, exclusive integrations, and feature depth that newer entrants can't trivially match. AppRanks frames marketplace strategy in moat terms because category dynamics are non-linear: the top-3 apps in a mature category capture 60-80% of new installs, and the gap usually widens once an app crosses a threshold of ~500 reviews and 12+ months of consistent velocity. Watching your moat means tracking three signals together: review-count delta vs the next-closest competitor, weekly install velocity differential, and feature-parity gap measured by the AppRanks audit score. A moat narrowing on any of these three (especially review-count delta) is the earliest signal that incumbents need to invest in differentiation rather than coast.

Where you see it on AppRanks: Homepage hero ("watch your moat" framing), competitors panel on app pages.

Read full definition of Competitor moat →

Review burst

A review burst is an abrupt spike in an app's review-arrival rate — typically defined as a single-day or 7-day review count that exceeds the trailing-90-day daily average by 3x or more. Review bursts often signal a triggering event: a feature launch driving early adopters to leave first impressions, a press mention or marketplace newsletter feature pulling fresh visitor traffic, or — less happily — a bug or pricing change concentrating user feedback into a narrow window. AppRanks distinguishes positive bursts (rating ≥ trailing average) from negative bursts (rating < trailing average) so the same magnitude metric reads differently depending on the underlying sentiment. Tracking burst patterns over time surfaces the cadence of product investment and incident response: a developer team running 6 launches per year with positive bursts each time is in a different operating rhythm than one with two large negative bursts and slow recovery between them.

Where you see it on AppRanks: App page "Ratings and reviews" section, audit page "Review velocity" timeline.

Read full definition of Review burst →

Install velocity

Install velocity is the rate at which new merchants install an app over a rolling window — typically expressed as installs per day, week, or month. On Shopify, install velocity is widely understood as the single strongest signal feeding the App Store's ranking algorithm: a sharp acceleration in the trailing 7-30 day window typically translates to category-position climbs within 1-2 ranking cycles. Atlassian, WordPress, and Zendesk apply similar velocity weighting, though with different lookback windows and smoothing functions that the marketplaces don't publish. Install velocity is distinct from total active installs — a mature app with 50,000 active installs and zero weekly velocity is stable but stagnant; a 6-month-old app at 2,000 installs adding 150 per week is gaining ground. AppRanks does not compute install velocity directly because most marketplaces don't expose per-day install counts publicly; we infer momentum from category-position trajectory and review-velocity correlation.

Where you see it on AppRanks: App page "Category Rankings" trajectory, audit page "Adoption" check.

Read full definition of Install velocity →

Search relevance

Search relevance is how closely a marketplace listing's title, description, tags, and keywords match the queries merchants type into the marketplace search bar. Every marketplace runs its own search index — Shopify's App Store, Atlassian Marketplace, WordPress.org, Zendesk Marketplace — and each weights title-match, description-match, category-match, and install-velocity-of-recent-clickers differently. The common pattern across platforms: an exact-phrase match in the title outranks a partial match in the description, and synonyms compete unless the listing explicitly enumerates them. For developers, search relevance is the highest-ROI listing lever because it determines the universe of queries the listing can rank for at all. A listing with a generic title and no tag coverage is invisible for tail queries no matter how strong its install velocity. AppRanks does not run a proprietary relevance score; we surface the title, description, tags, and category data as scraped so developers can compare their listing's keyword coverage against category competitors.

Where you see it on AppRanks: Audit page "Title & description" check, compare page side-by-side listing fields.

Read full definition of Search relevance →

Listing health

Listing health is an aggregate read of how complete and well-maintained an app's marketplace listing is across the signals merchants and the marketplace's own quality systems look at: title length, description word count, screenshot count and quality, video presence, last-update freshness, support response rate, and pricing transparency. A listing that scores well on every completeness signal converts marketplace impressions to installs at 2-4x the rate of a listing missing screenshots or with a thin description, even when rating and review count are identical. Most marketplaces don't publish a single listing-health number — instead, each signal feeds the ranking algorithm independently — but the concept is cross-platform: Shopify, Atlassian, WordPress, and Zendesk all reward listings that present a complete, recently-updated, support-responsive picture. AppRanks computes a 0-100 audit score that aggregates these listing-health signals into one number; the audit page surfaces the per-signal breakdown so developers can see which specific gaps are dragging the headline.

Where you see it on AppRanks: Audit page (/audit/{platform}/{slug}) — every check is a listing-health signal.

Read full definition of Listing health →

Category saturation

Category saturation is how crowded a marketplace category is relative to merchant demand — typically expressed as the number of competing apps within a single category divided by the marketplace's total app count, or as the share of top-50 installs held by the top 5 apps. A saturated category (e.g., Shopify's Email marketing with 600+ apps and 70% installs concentrated in the top 10) has high entry difficulty: new apps face an entrenched moat of incumbents whose accumulated reviews and install velocity self-reinforce ranking. An under-saturated category (a niche with 20-40 apps and a flatter install distribution) has lower entry difficulty and more upside for differentiation. Cross-platform, the same pattern holds: Atlassian, WordPress, and Zendesk all show power-law install distribution per category. AppRanks surfaces per-category app counts and top-app concentration on category pages so developers picking a category to build in can read saturation directly.

Where you see it on AppRanks: Category pages (/apps/{platform}/categories/{slug}) — per-category app count and top-app concentration.

Read full definition of Category saturation →

App store optimization (ASO)

App store optimization (ASO) is the industry-canonical acronym for the discipline of improving a marketplace listing's organic visibility — covering keyword research, title and description tuning, screenshot and video optimization, category selection, pricing presentation, review-base management, and the operational hygiene (update cadence, support responsiveness) that marketplace ranking algorithms reward. ASO originated in mobile app stores (Apple App Store, Google Play) and the same principles transfer to SaaS marketplaces like Shopify, Atlassian, WordPress, and Zendesk, with platform-specific weighting differences. Effective ASO is iterative: change one listing element, measure category-position and install-velocity shifts over the next 7-14 days, then iterate. AppRanks supports ASO workflows on every audit page (/audit/{platform}/{slug}) with a per-check rubric grading title length, description completeness, screenshot count, category fit, pricing transparency, and update freshness — the developer can see exactly which ASO lever moves their audit score the most before investing in the listing change.

Where you see it on AppRanks: Audit page (/audit/{platform}/{slug}) — every check grades an ASO signal.

Read full definition of App store optimization (ASO) →

Review recency

The freshness of an app's most recent reviews — measured as days since the latest review and as the share of the total review pool that landed in the last 30 days. Marketplaces increasingly weight recency in their ranking algorithms because a 4.7 average accumulated over five years is a weaker signal than the same 4.7 from the last 90 days: it tells the algorithm the listing is still being adopted and the rating reflects the current product, not a legacy version. AppRanks surfaces review recency on every audit page alongside the headline rating so an operator can see at a glance whether the rating reflects today's product or a frozen historical baseline. A common failure mode: a once-popular app holds its high average rating long after merchant adoption has stalled — recency exposes that decay months before total review count would.

Where you see it on AppRanks: Audit page "Rating health" check; app page "Reviews" timeline.

Read full definition of Review recency →

Rating deltas

The signed change in an app's average rating across rolling time windows — typically 7-day, 30-day, and 90-day deltas. A rating delta of +0.03 over 7 days means the average climbed from (e.g.) 4.62 → 4.65; a delta of -0.10 means it dropped. Small numbers carry large information because a marketplace listing with 500+ reviews moves slowly under random noise: a 0.05-point drop in 7 days usually represents 20-50 negative reviews landing in concentrated time, not statistical drift — a signal worth investigating BEFORE the headline rating crosses a visible threshold or the marketplace's algorithm reweights the listing. AppRanks shows the per-window delta alongside the absolute rating on every app page so a stable 4.6 with a -0.08 v7d gets flagged differently than a stable 4.6 with a +0.02 v7d. The delta column is also where most early-warning signals first surface — a soft launch failing to convert, a competitor pulling installs away, or a quality regression triggering negative feedback.

Where you see it on AppRanks: App page "Ratings and reviews" section; audit page "Rating health" check.

Read full definition of Rating deltas →

Rank volatility

The amplitude of an app's category-position changes over a rolling window — measured as the standard deviation of daily rank across (typically) the last 30 days. A low-volatility app moves ±1-2 positions per day in a steady channel; a high-volatility app may move ±10-20 positions per day. Volatility is independent from headline rank: an app stable at #4 and an app cycling 2-15 may both have the same 30-day median rank but very different competitive positions. AppRanks surfaces volatility on the trends page and inside the per-app rank history so an operator can tell whether a #5 placement is a defended position or a churning slot. High volatility is usually a signal that the marketplace ranking algorithm is weighing a metric (e.g., very-recent install velocity, freshness of reviews) that the app's underlying signals can't sustain.

Where you see it on AppRanks: App page rank-history chart; trends page volatility column.

Read full definition of Rank volatility →