← DocumentationSetting up a client
Markets and languages
What a market configures, and why it is an object rather than a locale string.
A market is a configuration object that carries everything about *where and how* a question gets asked. Brands attach to a market; they do not configure geography themselves.
What a market carries
| Field | Example (South Africa) | Why it matters |
|---|---|---|
| Engine mix | Six engines, weighted by local usage | The aggregate score is a weighted roll-up, not a flat average of engines nobody in the market uses |
| Geo parameters | Country ZA, city, timezone, hl=en | Passed to each adapter that accepts location; recorded on the capture either way |
| Languages | English, Afrikaans (isiZulu following) | The largest single driver of answer variance |
| AI Overview profile | Tri-state: present / absent / not detected | Vendors miss roughly a third of genuinely-present AI Overviews; “absent” and “we could not tell” are different facts |
| Device | Desktop and mobile treated separately | AI surface rollouts have been desktop-first and the two disagree |
| Intent rules | Local intent → map-pack expectation | Stops a map-pack query being scored as an AI Overview miss |
Adding a country
Adding a market is a configuration exercise plus a validation pass: confirm each adapter resolves for the new geography, confirm AI Overview availability, set the engine mix from local usage data, and add the languages. It is not a rebuild, and that is the whole point of the abstraction.
→Next step
See it against your own client list
A working demo runs your prompts, in your market, on live engines — not a sandbox with seeded data. Bring one client brand and three competitors.