# ASO Agency — Lesson 46: How to launch and measure an ASO localization pilot

Outcome: Release a bounded localization and evaluate it without confusing market growth with translation impact.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Write a pilot monitoring sheet with store and product outcomes.

Your response:

2. Create a change timeline that includes non-ASO activity.

Your response:

3. Prepare expansion decisions for positive, mixed and low-data outcomes.

Your response:

## Scenario challenge

A localization launch includes new screenshots and a paid campaign. Write a result statement that acknowledges the package and audience change instead of claiming the translation alone caused the download increase.

Your reasoning:

## Handover

### Rollout record

Specify locales, versions, changed components and observed-live dates.

Your evidence and decision:

### Baseline and results

Keep counts, definitions, source mix and mature observation windows.

Your evidence and decision:

### Local feedback

Record language, support and product issues with verification status.

Your evidence and decision:

### Decision

Explain expand, revise, continue learning or pause using the combined evidence.

Your evidence and decision:

### Ownership

Assign the next iteration, unresolved dependencies and review date.

Your evidence and decision:

## Submission check

- [ ] The conclusion matches the changes and comparison design.
- [ ] Source mix and sample size remain visible.
- [ ] Expansion depends on product and operational readiness, not traffic alone.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com