On this page
XXtrusioDocs

DocsMonitoring and insights

How Xtrusio Collects AI Answers and Keeps Comparisons Meaningful

Use the collection specification for each engine in your account when comparing answers.

Availability and responsibility

Use the collection specification for each engine in your account when comparing answers. Two answers can be compared meaningfully only when their collection conditions are understood. A browser search, a consumer chat session and a model API request may not represent the same experience, even when the brand name on the service is similar.

Xtrusio scan history showing retained AI answer observations
Xtrusio scan history

Keep an observation record

The minimum useful record contains the exact input, engine or mode, collection time, outcome and returned answer. Add country, language, account context and repeat number where known. Do not fill unknown context with assumptions. An explicit unknown is easier to interpret than false precision.

Check whether a comparison is fair

  1. Match the exact question wording.
  2. Confirm the engine and mode.
  3. Identify the collection method for each record.
  4. Compare relevant market and language settings.
  5. Separate failed collection from a successful answer that omits the brand.
  6. Note changes in method before interpreting a trend. Use the method recorded for the relevant engine rather than assuming that every result comes from the same interface.

Example

An illustrative baseline collected from a model API and a follow-up collected from a consumer search interface may show different citations. The difference could arise from retrieval behavior or other collection conditions. It cannot safely be attributed only to a new article.

If methodology changes

Keep the old records and mark the break in comparability. Where practical, establish a new baseline using the updated process instead of joining unlike observations into an unexplained trend. Request the collection specification for the engines in your account before making strong before-and-after claims.

Collection routes and saved records

Claude uses Anthropic messages with web search; Gemini uses search-grounded generation; ChatGPT and Grok use their providers' Responses APIs with web search; Perplexity uses search-backed chat completions. Google AI Overviews and AI Mode use DataForSEO endpoints. These observations can differ from a person's authenticated consumer-app experience. Saved attempts include the question, persona and stage, engine, collection time, raw answer, citations, available search queries and model/extraction metadata. They support comparison, not perfectly reproducible experiments: models, prompts and retrieval behavior can change.

Supported routes and comparison limits

The supported routes are ChatGPT, Claude, Gemini, Perplexity, Grok, Google AI Overviews and Google AI Mode. Scans use a neutral prompt without naming the client. A scan captures one answer per approved question and selected engine, not a repeated sample of what every buyer sees. Administrators and staff launch scans when needed. The client-facing Report and Executive Summary update after an administrator publishes the completed scan; they are not live dashboards.

The ChatGPT API route uses gpt-6-astra, selected through a comparison with the consumer ChatGPT experience because it was the closest match tested. That does not mean the API answer is identical to what a buyer receives in the ChatGPT app. Google AI Overviews and AI Mode use US English desktop search-data endpoints in the present implementation. State the selected engine, route and market when interpreting a result.

The system stores answer text, cited URLs with their titles and excerpts, unique cited domains, search queries supplied by the engine, search count, cost and model. Search-query fan-out is available from ChatGPT, Claude, Gemini and Grok only. A missing fan-out for Perplexity or either Google mode is not evidence that the provider made no searches.

Scheduled recurring scans and repeat sampling are not available. Do not describe a two-scan change as daily tracking, or a citation observed after publication as proof that the publication caused it.