Baidu ERNIE locale variance tracking
Baidu is mainland-focused, so locale variance here is mostly about region and language settings within China rather than across countries.
How it renders
Controlled by domestic egress and Baidu's own regional parameters.
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 Baidu ERNIE for the locale variance field, sampled n times and returned as one object per prompt.
{
"engine": "baidu_ernie",
"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 →Baidu ERNIE locale variance FAQ
- Do you use domestic egress?
- Yes, always, for Baidu. Anything else misreports the surface.
- Is there regional variation within China?
- Some, on local-intent prompts. We can split it if your prompts warrant it.
Collect Baidu the way a domestic user sees it
We will confirm egress and regional settings against your prompt set before quoting.
Other Baidu ERNIE data
Across every engine
Compare how locale variance behaves on every engine we track.
Locale variance across all engines →