# Measure ASO changes around an app release

URL: https://storelift.net/guide/measure-aso-release-impact/
Language: en
Updated: 2026-10-02

A release creates a useful marker in rank history, but several things may change around it: metadata, product behavior, reviews and acquisition campaigns. A release review should state what changed and what stayed comparable before claiming an ASO effect.

## Investigation steps

1. Save the previous listing and record when the new version and metadata became available in each relevant storefront. Submission time and public availability may differ.
2. Choose a fixed set of terms and comparable before-and-after windows. Keep newly added tracking terms in a separate group because they lack the same baseline.
3. Annotate campaign launches, pricing changes and collection gaps. Compare the affected terms with terms whose metadata was left unchanged, while recognizing that this is observational evidence.

## Worked interpretation

Illustrative case: a subtitle changed on Thursday and paid acquisition doubled on Friday. A download increase that weekend cannot be assigned entirely to the subtitle. Report the rank pattern and the campaign change together.

## Decision and next check

Keep the release assessment as a dated hypothesis: affected fields, observed ranks, acquisition context and remaining uncertainty. Define the next observation window before making another edit. Use a controlled store experiment for supported assets when a causal comparison is needed.

## Related Storelift feature

Read App rank tracker for the available product data and its scope. Keep the app, storefront, period and measurement status with the observations used in your report.