Geo-targeted capture
also known as: regional capture
Running the identical query from a specific country (and optionally a city) so the answer reflects what that market actually sees, AI answers, AI Overviews and SERPs vary by region, sometimes sharply, and a single-market capture cannot reveal that. Regions are a request parameter, not a separate product: the same Envelope shape returns, stamped with which market produced it.
In AI Search API
Any ISO-3166-1 alpha-2 country, with optional state, city and language, is supported, passed as structured { country, state?, city?, language? } objects, up to ten regions per request; each region in a request fans out into its own independent child capture. Omitting regions entirely defaults to a single untargeted, global capture. provenance.region records both the requested and effective country, so a claim like "the AI Overview didn’t mention us in Germany" is a specific, queryable Envelope rather than an assumption. Naming a city biases the capture toward that metro on a best-effort, surface-dependent basis. Diffing the same prompt’s Envelopes across regions is the core workflow behind every cross-market visibility and share-of-voice comparison this API supports.
"provenance": {
"region": { "requested": "DE", "effective": "DE" }
}Related terms
See it in the product
Every definition here is enforced in the Envelope contract. Run a capture and read the fields yourself.