Keyword research and metadata course · Lesson 3 of 10 · 60 minutes with practice

App Review Analysis for ASO: Find Customer Language

Turn a documented review sample into customer-language themes while retaining the original evidence and its limitations.

A close editorial view of ivory review cards, a magnifying glass over abstract sentence lines and small vermilion annotation tabs connecting repeated ideas.

Download your lesson workbook · Open the assignment tool →

Your ASO learning objective

Turn a documented review sample into customer-language themes while retaining the original evidence and its limitations.

  1. Step 1Document the review sample
  2. Step 2Connect quotation to interpretation
  3. Step 3Turn a theme into a research question
The lesson workflow

Describe the sample before counting themes

Record how reviews were collected, the app, store, locale, period, version coverage and selection rule. Recent negative reviews answer a different question from all reviews in a fixed period. A sample selected because it mentions navigation cannot tell you how common navigation confusion is among all users. Keep the selection rule beside your findings.

Import review text plus any available rating, date, locale, version, dataset and source. Use separate dataset names for your app and competitor samples. Leave unknown values blank instead of manufacturing dates or assigning a neutral rating. Dates need the explicit YYYY-MM-DD format so date filters do not silently interpret ambiguous regional formats.

Separate the quotation, interpretation and action

Read the full review before assigning a theme. “I expected maps” is an observation about an expectation; “our listing is misleading” is a possible interpretation that still needs investigation. The action might be to compare the opening promise with the product, and the measurement plan might be a comprehension review. Keep those layers in separate fields.

Use a small vocabulary of themes and consistent inclusion rules. For example, “Remembering walks” can include revisiting photos and notes, while “Navigation expectation” covers requests for directions. Merge labels when they describe the same concept. A review can contain several ideas; the current desk uses one primary theme and classification per record, so preserve secondary ideas in interpretation notes.

Report counts with a denominator and restraint

Suppose 6 of 30 imported reviews mention remembering walks. The observed share is 20% of that sample, not 20% of customers. If another sample has 3 of 10, its 30% does not establish a larger market need: selection, dates and app versions may differ. Use counts to organize investigation and inspect the original reviews behind a theme before making a listing decision.

Worked example: Trail Notes

This fictional hiking-journal app and its review samples are the teaching project. Treat the example as a reasoning exercise you can adapt to your own evidence.

  1. Original draft“Users want navigation” based on two selected low-star reviews.
  2. Revised proposal“Two reviews in our selected complaint sample expected directions. Review the listing promise and determine whether the audience is mismatched.”
  3. Why it changesThe revised finding identifies the sample and the observation without generalizing to every user or immediately adding an unsupported product promise.
From a weak draft to a defensible proposal

Your ASO assignment

  1. Import a small review CSV and map its columns. Filter by dataset, period and rating; document what the filter excludes.
  2. Assign primary themes to at least ten reviews, or all available reviews if fewer. Write interpretation, action and measurement notes for two important findings.
  3. Send one exact customer phrase to the Keyword Workbench. Keep it pending until its intent and product relevance have been assessed.

Work on your app project

Your handover and assessment criteria

Your work is ready for review when each deliverable below can be understood without a verbal explanation. Include the source or product reference, the decision owner and any unresolved evidence gap. If a reviewer cannot verify a claim, record the missing evidence before treating the proposal as approved.

  1. Deliverable 1Original review evidence and sample definition
  2. Deliverable 2Theme rules, counts and denominators
  3. Deliverable 3Research actions linked to specific review IDs
Three deliverables to include in your handover

Check your understanding

A filtered sample shows three navigation complaints out of five reviews. Can you say 60% of users need navigation?

Read the interpretation

No. You can report three of five reviews in that defined sample. The sample and its filter do not establish the proportion of all users with the same need.

Record your progress

Mark this lesson complete after checking your assignment against the handover criteria. Progress stays in this browser, separately from your tool project.

Sources and further reading

Platform references checked 30 September 2026.

App Store keyword research guide · Check final metadata fields