Prompt locations

An AI assistant answers a shopper in Berlin differently from one in New York. Different products, different recommendations, a different you. A prompt location lets you run one tracked question as if it were asked from a specific country, so you can see those differences instead of guessing.

What it does

By default every prompt collects from each market in your project's Collection settings — one pass per market, up to five. A prompt location overrides that for one prompt, on every plan. Point a question at Germany, France, or Brazil, and from the next collection cycle the location-capable engines answer it from that country instead of from the project's markets. Answers already collected keep the region they really ran in.

Location and language are independent. Moving a prompt to Brazil does not translate it. A US-English prompt pointed at Brazil still asks in English unless you change its language too.

Who it's for

• Multi-market brands who want the same question tracked from several countries, to compare how AI answers differ by market. For the markets you follow all the time, put them in the project's market set (up to five) so every prompt runs in each of them. A prompt location is for pinning one question to a country outside that set. Track a market as its own project only when you want a wholly separate report, with every metric scoped to that one market.
• Agencies running local campaigns who need a handful of prompts pinned to a client's target country, without spinning up a whole separate project.

Which engines honor a location

Read this part before you rely on the feature. Only engines collected through location-capable providers honor a per-prompt location. The rest have no location control and keep collecting from your project's region.

The same note appears in the app wherever you set a location: "Location targeting applies to engines collected through location-capable providers (ChatGPT, Gemini, Google AI Overviews & AI Mode, Perplexity, Copilot). Claude, DeepSeek, Grok and Mistral answer via APIs with no location control. Their answers keep the project's region."

Try it

1. Open Prompts on a live workspace and find the prompt you want to relocate.
2. Open the row's … menu and choose Location. Pick a country, or Auto (project markets) to clear an override.
3. To relocate many prompts at once, select them and use the Location action in the bulk toolbar. See Batch actions.
4. Check the Location column, turning it on from the columns menu if it is hidden. A prompt with an override shows a pin and the country code. A prompt without one shows your project's markets instead, muted and with no pin: their flags, plus the code when there is only one market and +N when there are more than three.
5. Wait for the next collection cycle. New answers collect from the chosen country on the engines that support it. Existing answers are unchanged.

How it's computed

• The market catalog. Locations come from the same catalog your project's markets are picked from: 241 countries, every officially assigned ISO 3166-1 country except the uninhabited territories with no civilian market. A project holds up to five of them at once; a prompt location can point at any one of the 241. The providers do not target all 241 with equal precision — the scraper path routes a country it has no infrastructure in through the nearest one it does — so read the major markets as exact and the long tail as best effort. What is never faked is the label: an answer is only ever recorded under the country it was actually targeted at.
• How a run is split. A prompt with a location collects once, at that country, instead of once per project market — re-running the same pinned country for every market would only buy duplicates. The engines that support it run from the chosen country. The model-API engines run from the project's primary market, and are recorded that way.
• No warning pop-up. There is no per-engine warning banner. The capability note above appears in the location menu, the column header, and each cell's tooltip, so you always know which engines will and won't honor the setting.
• It's a setting, not a backfill. A location takes effect from the next cycle. History keeps its real region.

Limits

• Un-gated: available on every plan, with no separate location quota. Running a prompt from more countries still uses your normal prompt quota like any prompt.
• Editor rights and a live workspace are required to change a location.
• Not every engine honors it. See the table above.

Related

• Prompts: the portfolio where prompts and their locations live.
• Batch actions: set a location on many prompts at once.
• Workspace and members: the Settings surface where the project's market set is chosen.