Investigation steps
- Record the source, country, observation date and count behind the headline rating. Determine whether the recent view contains written reviews, ratings or a limited sample.
- Group recent comments by version and recurring issue where the data allows. Compare like periods and note collection gaps before calling a change a trend.
- Inspect the severity and reproducibility of reported problems. A serious reproducible defect deserves investigation even when the sample is too small for a reliable percentage.
Worked interpretation
Illustrative case: a large lifetime rating total barely moves while recent reviews repeatedly mention a release-specific login issue. The stable headline score does not invalidate those reports, but the sample cannot establish the percentage of all users affected.
Decision and next check
Report the lifetime summary and recent evidence separately, with an action owner for recurring issues. Follow the affected version after a fix. Avoid converting a capped review sample into an app-wide rating distribution or a churn estimate.
Related Storelift feature
Read App review monitoring for the available product data and its scope. Keep the app, storefront, period and measurement status with the observations used in your report.
See this for your own app
Paste your store link, add your keywords. Rank, the apps above you and demand are measured every day.
Free plan: 1 app, 25 keywords in each of 2 storefronts, 30 days of history, no card, no end date. Pro is $20/mo.
Start free →
