Review velocity (7-day) is one of the 28 app marketplace metrics and concepts defined in the AppRanks glossary. This page gives you a clear, plain-language explanation of what Review velocity (7-day) means, why it matters when you evaluate an app, how AppRanks calculates and verifies it, and exactly where you will see it across our public app, audit, and comparison pages. Read on for the full definition, practical use cases, and links to related terms so you can interpret Review velocity (7-day) with confidence.
Also known as: v7d, weekly review velocity, 7-day review rate, trailing week reviews, last-7-days reviews
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.
v7d is the earliest signal an app's momentum is changing — useful for tracking the immediate impact of a release, marketing push, or sudden negative event before it shows up in 30-day or 90-day windows. The trade-off is noise: review batches arrive irregularly, so a single low v7d isn't a problem but two consecutive zero weeks usually is. For developers running merchandising experiments, comparing v7d before vs after the change attribution period is the cleanest read on whether the experiment moved real user behavior or just install attempts.