PromptSpark.ai Docs
Sign in
Browse documentation
Docs Markets

Markets

Read and maintain every field on Markets without mistaking configuration counts for performance metrics.

What you see on Markets

Markets lists the geographic and language contexts configured for the current project. Each row is a reusable setup record that prompts can reference. New Market creates another context; edit changes the record; removal is a setup action and may be blocked or require reassignment when prompts use the market.

Market names, country codes, cities, and languages describe audience scope. They are not inferred visibility statistics. A list of three markets means three configured contexts, not that the brand is visible in three countries and not that every prompt runs in all three.

How the fields are used

Field Meaning How to interpret it
Name Human-readable reporting label. Use a label stakeholders will recognize.
Country or country code National context attached to prompts and filters. It narrows scope; it does not geolocate the provider response independently.
City Optional local context for city-sensitive demand. Leave blank when city-level wording is not part of the research design.
Language or locale Language context expected for prompts and reporting. Compare like with like when language changes answer behavior.
Prompt count where shown Prompts currently assigned to that market. A configuration count not completed answers.

Markets in reports

Selecting a market filter limits reportable executions to prompts assigned to that market. All downstream numerators and denominators are then recalculated from that filtered evidence. For example, Visibility becomes mentioned completed responses divided by completed responses in the chosen market, not the project-wide value.

A market with few active prompts can move sharply because one answer represents a large share of its denominator. Always read market results with the completed response count, providers, date range, topic, and tag filters. Do not compare a city-specific market with a national market as though their prompt designs were identical.

Maintain comparable market evidence

  • Create separate markets when language, availability, regulation, competitors, or customer intent materially differs.
  • Avoid duplicate labels for the same scope; they fragment filters and make counts harder to reconcile.
  • Review prompt assignments after editing a market definition.
  • Record when a market changes so trend readers can separate measurement changes from market movement.
  • Use the exact same provider and prompt scope before claiming one market outperforms another.