Track your rankings
Find your next growth opportunity

Analytics shows your app’s App Store and Google Play search visibility across the keywords you track. Follow keyword rankings, ranked-keyword counts, top-10 positions and competitor share of voice for your selected markets. These describe search presence, not downloads, revenue or conversion data. Use the keyword table and market context to understand a summary trend. If you also need install or revenue reporting, keep the source of those business metrics separate when sharing the analysis with your team.

Spek collects daily store ranking observations for the tracked keywords in your target markets. Analytics builds its trends from those observations. While a new observation is arriving, it keeps the latest measured value visible; a metric that has not been measured yet shows a waiting state. Check the available date range and latest observation before drawing a conclusion from a short-term change. A new daily observation does not start an Agent proposal run or publish new metadata on your behalf.

Share of voice helps you compare your app’s search presence with tracked competitors in the same market and keyword set. Choose a competitor to view its trend alongside yours. This comparison covers the keywords you track, not a competitor’s entire business or worldwide audience. Keep the selected competitors and storefront visible when presenting the result to colleagues. If the comparison context changes, explain it alongside the chart instead of describing every difference as movement in your own app.

Analytics follows the target markets saved in your Agent setup. After a market’s first run creates its tracked keyword set, its daily ranking history starts building. Use the storefront picker to view a market’s own rankings and competitors. Spek remembers your last selected storefront for that app across visits and devices. The same app can face different search habits and competitors in another country. Review each market on its own terms and avoid substituting one storefront's values when another has not yet collected enough observations.

Switch between 30-day and 90-day windows to explore the observations Spek has collected. History starts with the first recorded rankings, so a newly tracked market needs daily observations before a trend appears. Spek does not backfill dates before tracking began, and the keyword table shows the available standings while history builds. A longer chart does not create observations that were never collected. State the available period when comparing a newly tracked market with an established one, and do not treat missing dates as a series of measured zeros.

Use the same app, store, storefront and relevant keyword set, and note when the listing change actually reached the provider or public store. Read several observations in context rather than treating one day's position as a verdict. Changes in competitors and search results can affect rankings alongside your own edits. Analytics helps you review search presence over the selected period, while your store or business analytics supplies installs, conversion and revenue. Keep those measurements separate when presenting an update to the team.

A missing or waiting value means the relevant observation is not yet available; it should not be read as a measured zero. A newly tracked market needs time to build history, and an existing view can retain the latest observation while another one is being collected. Check the market and available dates before comparing charts. If the expected data remains absent, report the app, storefront, keyword and approximate time to support instead of filling the gap with a value from another country or another tool.

A single keyword describes one search result, while a visibility view summarizes the tracked set in that market. One term can improve while other terms change in the opposite direction or remain stable. Review the underlying keywords to understand the context instead of assuming the summary must follow whichever term you checked first. Also confirm that you are comparing the same market and available dates. These views help prioritize investigation, but neither is a direct measure of all searches, store impressions or the app's complete audience.

State which apps, storefront, tracked keywords and observation period the comparison covers. Share of voice describes relative search presence within that scope; it is not a statement about a competitor's total downloads, revenue or worldwide market share. If you change the competitor list or review a different market, explain that context before comparing the results. A clearly scoped report is more useful than a broad claim that an app is winning everywhere based on a small set of local keyword observations.

Use App Store Connect for Apple's product-page test results. Spek's ranking and visibility views can provide search context during the same period, but they do not ingest the treatment-level conversion outcome of a store-run test. Record the dates and scope of each source when reviewing the experiment. This lets your team discuss whether search presence changed without confusing that observation with proof that a particular screenshot treatment or custom page converted more visitors.

Check the exact keyword, market and observation date, then review whether the pattern affects one term or a broader part of the tracked set. Compare the relevant listing history and available competitor context. A single movement can be worth watching without requiring an immediate metadata rewrite. If a value appears inconsistent or remains unavailable, report the specific example to support. Use the evidence to decide whether another review is useful rather than treating every daily change as a command to publish a new listing.