Customer-built analysis
ChatGPT: locale variance
Compare country-routed collections with your own study design.
Collection target: chatgpt. This is customer-built analysis, not a computed API response field.
Build this analysis in your application
Submit separate jobs with options.country when investigating country effects. Record prompt language and requested country alongside the results and keep other study conditions comparable.
Customer-built analysis
The chatgpt target collects responses through the web interface. Each successful run carries its run identity, capture time, text, markdown, pageUrl and sources. Text, markdown and pageUrl can be null; sources can be empty. Answers and sources vary by run. Country routing is a request option, not a guarantee of a particular language or provider location. Build your own analysis from the collected responses.
Collected input for your analysis
These are illustrative successful run excerpts, not full result files or calculated metrics. Submit POST /v1/crawl-jobs, track completion, then download the authenticated result. Outputs depend on the target; a chatbot has no news articles or Google position fields.
{
"runNumber": 1,
"runTaskId": "9a7536e7-b610-420a-a34c-5f829956f4d3",
"status": "completed",
"capturedAt": "2026-10-09T10:01:00.000Z",
"text": "Illustrative captured answer text.",
"markdown": null,
"pageUrl": "https://chatgpt.com/",
"sources": []
}Locale variance FAQ
- Does the API calculate locale variance?
- No. Compare country-routed collections with your own study design. The API supplies collected provider outputs; this analysis belongs in your application.
- How should failed or empty collections be handled?
- Inspect per-target failedRuns and each successful run identity. Empty sources or null fields are valid output; a missing failed run is not an empty successful answer. A completed job can contain failed collections.
Use collected data to build your own reporting and analysis. Our team arranges API access and follows up with next steps.