Customer-built analysis

Perplexity: locale variance

Compare country-routed collections with your own study design.

Collection target: perplexity. 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

Country routing is a request option, not guaranteed output language or provider location. There is no language request field or returned locale-variance score. Country availability depends on deployment configuration.

The perplexity target returns text, markdown, pageUrl and sources with the successful run identity and capture time. Source lists may be empty and response fields may be null. Perplexity may use operator-configured sessions. Availability depends on deployment configuration and provider behavior; no response or citation count is guaranteed.

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://www.perplexity.ai/",
  "sources": []
}
Illustrative provider output. Empty lists and null fields are valid; inspect failedRuns in the result file.
Full result format and failed-run handling →

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.