What to know
Apple provides relative search-term popularity data through its Apple Ads Platform API. The data is not a promise of exact monthly searches. It helps compare demand across terms, countries, genres, and time periods.
Use the signal to rank research questions, not to replace judgment. For example, compare two relevant phrases for the same storefront, then decide which one better matches the app’s main task and current listing. A lower relative signal can still be the better choice when the product fit is clearer.
Treat popularity as a relative signal with a scope, not as a monthly traffic promise. Store the country, genre, period, retrieval date, and API response or export with the research note. A score without its market and time window is easy to misread.
Choose a country or region, a genre, and a monthly or weekly time range. Keep the response date with your research notes. A popular term may also have strong competition, so pair demand with relevance and the strength of the current results.
Pair demand with product fit. A popular phrase is not useful if the app does not solve that problem or if the listing makes a different promise. Compare the phrase with the current build, screenshots, support questions, and the words users actually use.
Use the shortlist to form a testable hypothesis, not a guarantee. Change one storefront or one field when possible, record the before state and date, and review the available App Store signals later. Do not claim a traffic or conversion lift without comparable first-party data.
A useful research row can read: term, country, genre, period, retrieval date, popularity signal, source endpoint or export, product-fit note, competing-result note, selected field, reviewer, and next action. Keeping these columns together prevents a popularity value from being copied into a brief without its scope.
Interpret comparisons within the same slice first. A term ranked in one country or genre is not directly comparable with a term from another slice. If the API response changes shape or coverage, preserve the raw response and write down the limitation before updating a shortlist or calling a trend.
Run a same-slice check before making a comparison: same country or region, genre, period, retrieval method, and data definition. If one of those changes, label the rows as separate observations. This simple discipline prevents a relative signal from becoming a false trend line.
Add an interpretation note beside every selected term. Explain why the term fits the product, what the popularity signal can and cannot say, which field or test it informs, and what evidence would change the decision. Keep the raw export or API response available for later review.
Use the popularity signal to prioritize research, not to promise traffic. Pair it with product fit, storefront language, current metadata, and comparable first-party results. If the signal is missing, delayed, or scoped differently, keep the limitation visible instead of filling the gap with a guessed number.
Run a data-slice validation before comparing terms: confirm country or region, genre, period, retrieval date, endpoint or export version, and the definition of the returned signal. If one field differs, keep the rows separate and explain why the comparison is limited.
Write a decision row for every selected term: relative signal, product-fit evidence, competing-result note, proposed field, reviewer, next check, and reason not to treat the signal as monthly volume. This turns a popularity observation into a bounded research choice.
Reopen the shortlist when Apple changes the endpoint, data coverage, scope labels, storefront language, or the product promise. Keep the original response and interpretation note so a later update does not silently convert a relative signal into a stronger claim.
ASOgenic can help keep the country, date, source, and decision attached to a draft. Your team still decides whether a term is truthful and whether Apple’s current data supports the next review. Never paste private API credentials into a writing workflow.