The ASO weekly review: leave with one decision, not a bigger dashboard

Check whether there is enough comparable evidence

Open the review by confirming app identifiers, storefronts, query wording, and collection dates. Back My Side's tracker history comes only from collected snapshots. A blank period is missing evidence, not zero visibility or a failed app. Record coverage before interpreting a graph so a sparse week does not masquerade as a dramatic performance change.

Separate an uncollected snapshot from a collected response in which the app was absent. The service samples positions from up to 200 Apple public search results, not device rankings. An absent app has no known rank of 201. Keep these states distinct in any spreadsheet or meeting summary you create outside the tool.

Compare a stable group of queries before exploring new ones

Maintain a core group for current positioning and review exploratory phrases separately. Adding difficult terms can lower an average without existing queries declining; removing missing terms can create the opposite illusion. Disclose membership changes and preserve an original-group comparison.

For a hypothetical language-learning app, the core group might cover vocabulary practice while pronunciation coaching remains exploratory until that feature ships. Compare like-for-like observations and show how many queries contributed to a summary. A single average obscures differing intent, so inspect the important individual phrases before recommending a metadata revision.

Connect visibility to acquisition without merging the evidence

Review App Store Connect acquisition, conversion, and relevant downstream behavior separately from public search positions. Back My Side does not integrate with App Store Connect, so bring your first-party findings into your own review notes. Match periods and storefronts where the available dimensions permit, and avoid inventing precision when privacy thresholds or reporting coverage limit the comparison.

Check campaign activity before calling a search-source change organic: Apple Ads performance may appear in App Analytics. A new promotion can alter the mix of visitors even when listing assets remain unchanged. Likewise, improved sampled positions with weaker activation can indicate an audience mismatch rather than a successful growth outcome. Write competing explanations beside the favored one.

Write the next decision and its stopping condition

Prioritize an evidence-supported issue: clarify a screenshot, correct an inaccurate subtitle, investigate release quality, or collect more observations. Do not change metadata merely to demonstrate activity. Stable positioning can be right when evidence is thin or another bottleneck matters more.

Keep the decision log outside the tool in a document your team owns. Record what would justify continuing, reversing, or escalating the action. If you compare periods after changing metadata, label the result observational. Apple's randomized product page optimization is available for icons, screenshots, and previews, not titles or keyword fields; use it for an eligible visual question.

• Evidence: name the observations, period, storefront, and coverage limits.
• Hypothesis: explain the user problem and plausible alternative causes.
• Action: assign one owner and define the smallest useful change.
• Review: set a date and state what evidence would change the decision.

Frequently asked questions