How Kinsho collects data
A transparent look at what happens behind the scenes when Kinsho runs your prompts.
Kinsho is a daily pipeline. Every day, every prompt you created is asked to every AI model you selected. We capture the raw response, extract brand mentions, compute metrics, and store the full answer so you can go back and inspect it at any time.
- 01Prompt execution
- 02Response capture
- 03Brand extraction
- 04Sentiment & position
- 05Source attribution
- 06Aggregation
The daily pipeline
- 01Prompt executionYour prompts are sent to each selected AI model through the same interface a real user would see.
- 02Response captureThe full text, citations, and timestamps are stored so you can audit any score later.
- 03Brand & competitor extractionA multi-pass extractor (including CJK-aware matching) identifies every brand mention and its context.
- 04Sentiment & position scoringEach mention is classified as positive / neutral / negative and ranked within the response.
- 05Source attributionCitations are normalized and mapped to the domains and pages AI models actually referenced.
- 06AggregationScores are aggregated into the visibility, sentiment, and position you see on the dashboard.
Why daily, and why multiple runs?
AI responses are probabilistic — the same question can produce different answers on different days. A single run is noisy. Running every day across multiple models lets Kinsho produce stable, trend-aware metrics you can act on.
Multi-region simulation for accurate results
AI answers are not the same everywhere. A question asked from Tokyo produces different brand mentions than the same question asked from New York or Berlin — because AI models weight locally relevant sources, regional product availability, and language-specific training data differently.
Kinsho runs each prompt from multiple geographic regions simultaneously, using an advanced simulation layer that replicates how a real user in that region would interact with the AI. This means your visibility scores reflect actual regional variation rather than a single US-centric viewpoint.
Why we use UI interactions, not APIs
Most analytics tools call official APIs, but API responses often differ from what real users see: different models get selected, different sources get cited, and sometimes web search is silently disabled.
Kinsho interacts with AI models through their real product surfaces. That means your data matches what the average logged-out user actually experiences.