Prompt locations

A prompt location lets you run one tracked question as if it were asked from a specific country — overriding your monitor's default region for that prompt only. It is available on every plan, and it changes only where the question runs, never what language it runs in.

What it does

By default every prompt collects from its monitor's region. A prompt location overrides that for a single prompt: point a question at Germany, France, or Brazil and, from the next collection cycle, the location-capable engines answer it from there. Answers already collected keep the region they really ran in — a location is a setting going forward, never a retroactive relabelling of history.

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 its language is also changed.

Who it's for

• Multi-market brands who want the same question tracked from several countries to compare how AI answers differ by market.
• Agencies running local campaigns who need a handful of prompts pinned to a client's target country without spinning up a whole separate monitor.

Which engines honor a location

This is the honest part worth reading before you rely on it. 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 — and MentionFlow records them under the region they really ran in, so the data never pretends otherwise.

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 region) 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 (turn it on from the columns menu if hidden). A prompt with an override shows a pin and the country code; a prompt without one shows your project's region code, muted, with no pin.
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 a curated catalog of 57 markets — countries both collection providers support for consumer-surface targeting. It is deliberately not the full list of every country: an unverified market would silently fall back to the project region and fake coverage. The catalog is append-only, so new markets are added on customer request as simple, verified additions. Your monitor's nine region options are a subset of it.
• How a run is split. When a prompt has a location, the engines that support it run from that country while the model-API engines run — and are recorded — from the monitor's region. Every answer is stored under the region it truly executed in.
• No warning pop-up. There is no per-engine warning banner; the capability note above is shown 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 consumes 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.
• Monitors — the default region a prompt inherits.