Skip to main content
A first monitoring run is a snapshot of the selected prompts and models. Treat it as an initial observation, not as a trend.

​
Check the scope first

Before interpreting a percentage, confirm:
  • the expected prompts generated answers;
  • the intended providers, country, and language were selected;
  • topics, tags, and funnel stages are assigned correctly;
  • direct competitors are classified as DIRECT rather than INDIRECT or IGNORED;
  • the date range includes the run you want to review.

​
Read the Overview

Open Cockpit > Overview. The five cards summarize different parts of the selected dataset:
  • Mention Rate and Citation Rate use only answers with a SELF or DIRECT denominator;
  • Share of Voice counts mention occurrences, not distinct answers;
  • Average Sentiment summarizes scored mentions;
  • Coverage works at the distinct-prompt level.
See Core Concepts before comparing these values with an export or API response.

​
Inspect the evidence

Open Monitor > Response Analysis to read individual answers. Use prompt, answer, funnel, competitor, source, and insight filters to narrow the table. Then use:
  • Monitor > Competitor Mentions to verify brand relationships;
  • Monitor > Source Explorer to inspect cited domains and pages;
  • Cockpit > GEO Matrix to compare a metric across providers and prompt groupings.

​
When data is sparse

An empty chart can mean that no answer matches the current filters, that a provider did not return data, or that the relevant signal was not detected. Widen the date range and clear filters before changing the prompt set. If answers exist but do not address the intended question, revise ambiguous prompts in Workspace > Prompts. Keep the old and new wording separate if you need to preserve historical comparability.

​
Build a trend

Use repeated runs with a stable prompt set, provider selection, and market to build a comparable time series. Document configuration changes when interpreting a break in the trend.