# Lesson 54: ASO troubleshooting: download and conversion drops

Investigate a decline through data validity, segmentation and competing explanations before making changes.

Prerequisite: A metric dictionary, publication log and access to the relevant report owners.

Teaching examples are fictional unless explicitly identified as platform definitions.

## Foundations

### Verify that the decline is real

Check reporting delays, date completeness, changed definitions and filters before acting. Compare counts and rates separately. A lower number of downloads may reflect fewer visitors even if conversion is stable; a lower aggregate rate may reflect source mix. Document the observation precisely so the investigation does not begin with an assumed cause such as “the algorithm changed.”

### Localize the problem

Break the result into meaningful sources, markets, devices or versions where evidence allows. Review availability, publication errors, technical incidents, campaigns and known seasonal context. A decline confined to one locale suggests a different investigation from a global acquisition fall. Keep the number of comparisons focused on plausible explanations rather than searching indefinitely for an interesting correlation.

### Choose the next discriminating check

List competing hypotheses and the observation that would support or weaken each. Fix a confirmed operational error promptly, but avoid making several unrelated changes that erase the evidence trail. If no cause is established, report the uncertainty and the next check. A professional investigation can conclude “not yet resolved” while still giving the team a clear sequence of work.

## Apply the method

### Validate the signal before changing the listing

Check reporting availability, date completeness, metric definitions and filters. A partial day, delayed export or switch from acquisitions to clicks can create an apparent drop. Compare absolute counts and rates so a denominator change is visible. Confirm the affected store, market, source and version. Preserve the original observation and the corrected interpretation if a reporting issue is found. The first response should reduce uncertainty, not add several untracked changes that make the diagnosis harder.

### Locate the change in the journey

Separate exposure, store decision, first use and useful product outcomes using compatible measures. A traffic decline with stable rates differs from stable traffic with weaker conversion. Segment by source, market and version where data supports it. Review recent releases, campaigns, pricing, availability and competitor context. Build competing explanations and identify the fastest check that could rule each out. Avoid treating a timing coincidence as proof that the latest metadata edit caused the problem.

### Choose a proportionate intervention

Correct verified errors promptly, such as an unavailable offer or broken destination. If a product defect is confirmed, coordinate its repair and log rollout timing. For uncertain message effects, use the evidence and experiment process rather than repeatedly swapping assets. Define recovery in terms of the affected population and outcome, and keep a review date. After resolution, write the incident learning so the same measurement or release mistake is less likely to recur.

## Procedure

1. Validate report completeness, definitions and comparison periods.
2. Separate traffic volume from within-segment response rates.
3. Review the change log and localize the affected population.
4. Rank competing explanations by evidence and perform the next discriminating check.

## Worked example

Trail Notes’ downloads fall 25% in an illustrative report. The matched visitor-to-outcome rate is unchanged, while a referral campaign has stopped. The first explanation is reduced incoming traffic, not a sudden screenshot failure. In another market, the listing is unavailable due to a publication issue; that requires an operational correction. The team treats these as separate problems instead of applying one global title rewrite.

| Pattern | First hypothesis family | Initial check |
| --- | --- | --- |
| Traffic down, rate stable | Discovery or campaign change | Source and visibility context |
| Traffic stable, rate down | Audience mix or listing decision | Segments and recent promises |
| Downloads stable, activation down | Product or expectation issue | Release and first-use validation |
| All reports suddenly empty | Reporting or availability issue | Data freshness and status |

The patterns direct investigation; they are not diagnoses by themselves. Several mechanisms can produce the same pattern, and multiple changes can occur together. Start with data validity and the narrowest affected population. A careful incident note should state what is known, what is suspected and what the next check will resolve. This is more useful than an immediate claim that an algorithm update caused the decline.

## Your ASO assignment

1. Create a diagnostic tree for volume, rate and product-quality changes.
2. Investigate a hypothetical decline with three competing explanations.
3. Write an incident memo with confirmed facts, unknowns and next checks.

A 30% decline appears in a report exported halfway through the day. Explain the validation sequence before comparing it with yesterday's full-day total or changing metadata.

## Handover

### Incident statement

Record the exact metric, population, timing and magnitude of the observed change.

### Validation

Confirm complete data, stable definitions and correct filters before interpreting performance.

### Hypothesis table

List plausible causes, evidence for each and disconfirming checks.

### Action log

Assign corrections or investigations with owners and record every intervention.

### Recovery review

Define the outcome to monitor and preserve the final learning with remaining uncertainty.

## Check your work

- Report and filter problems are checked before strategic changes.
- Traffic, conversion and product outcomes are distinguished.
- Actions follow evidence and preserve a useful change history.

## Common mistakes

- Blaming an unspecified algorithm change before checking availability or reporting.
- Changing title, screenshots and targeting simultaneously during an unresolved incident.

## Knowledge check

Downloads fall while comparable conversion is stable. Where should the first investigation focus?

Examine incoming traffic volume and its sources, along with availability and reporting completeness. Stable conversion does not prove the listing is perfect, but it weakens the claim that a conversion failure alone explains the decline. Use the evidence to sequence the investigation rather than defaulting to a rewrite.

## Sources

- [Google Play — Understand and grow your user base](https://support.google.com/googleplay/android-developer/answer/9859173?hl=en) — Current listing-click reporting, completed acquisitions and segmentation.
- [Android Developers — Android vitals](https://developer.android.com/google/play/vitals) — Product-quality monitoring and Android performance signals.

Platform references reviewed 29 September 2026.
www.asoagency.com