Review an ASO portfolio across several apps

Investigation steps

1. Create an app-level scope table with platforms, storefronts, tracked terms and successful measurement coverage. Keep paused or newly added tracking separate from established history.
2. Summarize changes within each app's fixed groups. Show outside-range and missing observations alongside numerical positions; do not hide a poorly measured app in an aggregate average.
3. Prioritize investigations by relevance, magnitude and available evidence. Add acquisition outcomes only at the scope the source supports, keeping account-level figures outside app-level comparisons.

Worked interpretation

Illustrative case: one app has hundreds of tracked terms and another has twenty. A portfolio-wide mean mostly reflects the larger set. Separate app summaries can reveal a significant decline in the smaller app that the overall mean barely shows.

Decision and next check

Assign the next action at app and country level, with a named owner and evidence to collect. Keep the portfolio view as navigation into those decisions. Do not rank apps by incompatible averages or divide shared account revenue among them by assumption.

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.

Read next