# Build a client ASO report with traceable evidence

URL: https://storelift.net/guide/client-aso-report-evidence/
Language: en
Updated: 2026-10-03

A client report needs to distinguish completed work, observed results and the interpretation connecting them. Those are separate claims. A defensible report makes the scope and source of each result visible and explains what the evidence cannot yet establish.

## Investigation steps

1. List the agreed app, country and platform scope with the reporting period. Record additions to tracking separately so broader measurement is not presented as a visibility gain.
2. Pair each completed task with its publication or completion date and the relevant observations. Link a metadata edit to its actual fields rather than a vague optimization label.
3. Show positive, negative and inconclusive outcomes using the same comparison rules. Include data gaps and distinguish rank movement from attributed installs or revenue.

## Worked interpretation

Illustrative item: a localized listing was published, five relevant terms gained observed positions and acquisition data is still incomplete. Report all three facts; do not turn the rank gains into an unsupported claim of additional customers.

## Decision and next check

End with decisions the client can approve or evaluate: retain an edit, investigate a decline or prepare a specific experiment. Keep the underlying export and definitions available so the summary can be checked without rebuilding the analysis.

## Related Storelift feature

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

## Worked example and blank template

The values below are synthetic, not customer or product results. Open the example, replace its scope with your own data and keep the source export alongside it.

- Printable worksheet and short walkthrough
- Worked CSV example
- Blank CSV template