Qwen locale variance tracking
Qwen is a mainland-China surface first. Locale work here is mostly about language and about whether your commerce presence exists in the market at all.
How it renders
Controlled by prompt language and egress country.
Sampling
Each locale is its own sample set. A cross-market comparison at n=30 per market costs what it says on the tin, which is why we surface the arithmetic before you commit.
Gotcha
What the API returns
A single collection call against Qwen for the locale variance field, sampled n times and returned as one object per prompt.
{
"engine": "qwen",
"field": "locale_variance",
"prompt": "best ai visibility tracking tool",
"country": "GB",
"language": "en",
"n": 30,
"locales": [
{
"country": "GB",
"language": "en",
"share": 0.34,
"divergence": 0.02,
"unique_domains": 4
},
{
"country": "DE",
"language": "de",
"share": 0.19,
"divergence": 0.15,
"unique_domains": 11
}
]
}Response fields
| Key | Type | Notes |
|---|---|---|
| country | string | ISO 3166-1 alpha-2 country of the egress used. |
| language | string | ISO 639-1 language the prompt was issued in. |
| share | float | Brand share within that locale. |
| divergence | float | Distance from the global mean for this prompt. |
| unique_domains | integer | Domains cited in this locale and nowhere else. |
What it costs
Each locale multiplies the collection count. Two markets at n=30 is 60 credits per prompt.
See credit pricing →Qwen locale variance FAQ
- Can you run Qwen outside China?
- We can, but we will tell you when the result is not representative rather than selling you the credits.
- Which markets are worth running?
- Mainland China primarily. We will advise honestly on the rest.
Run Qwen the way a Chinese customer would
Tell us your markets and we will flag the ones where Qwen is genuinely representative.
Other Qwen data
Across every engine
Compare how locale variance behaves on every engine we track.
Locale variance across all engines →