App Store and markets
| Term | What it means here |
|---|---|
| Storefront | One country's App Store or Google Play storefront. Rankings are observed within that store and market, which is why all the work is scoped to one. |
| Locale | One language version of a listing. A storefront can carry several. |
| Market | A storefront and a locale together. This is the unit the agent works in. |
| Workspace | Your team's space in Spek. Store credentials, apps and members all belong to one. |
Keywords
| Term | What it means here |
|---|---|
| Volume | How much a term is searched in one storefront. An estimate for comparing keywords, not a forecast of installs. |
| Difficulty | How contested a term is, and how strong the apps already ranking for it are. |
| Chance | An estimate of ranking opportunity for your app on that term. |
| Match | How closely a keyword fits what your app offers. |
| Rank | Your position in that storefront's results for a term. |
| Visibility | A summary of search presence across tracked keywords. Not impressions, and not downloads. |
| SERP | The list of apps a store returns for a search term. |
The agent
| Term | What it means here |
|---|---|
| Run | One pass over your selected markets: research each market, then draft proposals. |
| Scope | A permission you granted the agent, such as metadata or screenshots. It works only inside them. |
| Proposal | A suggested change waiting for you in the review inbox. Never live. |
| Review inbox | Where proposals wait. The human gate in the workflow. |
Publishing
| Term | What it means here |
|---|---|
| Draft | Your edited listing inside Spek. Accepting a proposal updates this, and only this. |
| Publish | The deliberate action that sends a draft to the store. Always yours to take. |
| Custom product page | An alternate App Store page for a specific audience. iOS only, and Apple has to make your app eligible. |
| In-app event | A timed, discoverable event on your App Store page. iOS only. |
Terms are defined the way Spek uses them, which is not always how another tool uses the same word.
Common questions
Why does Spek say market where other tools say country?
Because a country's store can carry several languages, and the agent works on one storefront and one language at a time. That pair is the unit, so it needs its own word.
Include the store as well when describing a task or metric. This prevents a teammate from comparing an App Store observation with a Google Play result, or from reviewing the wrong language version of a listing that is available in the same country.
Is visibility the same as impressions?
No. Visibility here describes your app's search presence across tracked keywords. Spek does not receive store impression data.
How do I use these definitions when comparing reports?
First check what each report means by the metric name, then align the app, store, market, keyword set and observation period. Two products can use the same label for values with different coverage or definitions. Spek's visibility describes search presence across tracked keywords; it should not be substituted for store impressions or installed users. Including the definition and scope beside a metric makes a report more useful to teammates who did not collect the data and reduces accidental comparisons between unrelated numbers.
Why do draft and publish need separate names?
They identify different states with different consequences. A draft is editable work in Spek, while publishing is the action that sends an approved change to the store provider. The provider's review and public release can introduce further stages. Using the exact term in a task or support report helps everyone know whether the issue concerns saved text, a rejected operation or a public listing that has not updated yet. It also prevents a teammate from assuming a draft review has already changed customer-facing content.
What is the difference between an observation and an estimate?
A ranking observation records the position seen for a keyword in a storefront at a particular time. An estimate helps interpret an opportunity or compare candidates and should be read with its stated scope. Neither should be relabeled as downloads, revenue or a guaranteed future position. When presenting a result, say which kind of value it is and where it belongs. That simple distinction keeps a useful research signal from turning into a claim that the underlying data cannot support.
How should I describe a multilingual task to another person?
Name the workspace and app, then specify the store, storefront and locale rather than saying only a language. Identify whether you mean research, a proposal, a saved draft, a provider update or a public release. For a metric, add the keyword and observation period when relevant. These terms make a task concrete enough for another reviewer to find the same context and make the intended decision, especially when a team manages several apps with similar names across multiple markets.