A hint saying only “customers in Uppsala” leaves two questions unanswered. Which offer is relevant, and is the writer describing a situation or trying to restrict ad delivery? Resolve those questions separately before using the wording. A place name may matter to a local offer, but it can also conceal the absence of a useful use case.
OpenAI states that geographic targeting is configured on the campaign and that context hints do not replace it. Check supported options for the account and campaign type in the targeting documentation. The examples here are editorial illustrations, not statements about advertising availability in a particular Swedish city.
Put each location fact in the right column
Three geographic facts may appear in one brief: where the business is based, where the customer uses the offer and where the business can actually provide the service. They are not necessarily the same place.
A fictional company may have an office in one city while providing remote advice elsewhere. Another may receive visitors at a specific address. A third may perform work within a limited service area. Begin by writing which relationship with place applies.
| Fact | What it describes | What needs checking |
|---|---|---|
| Business address | Where the business is based or registered | Whether the address matters to the customer’s task |
| Service location | Where the customer receives the offer | The actual delivery arrangement |
| Service area | Where the business accepts work | Current boundary and relevant exceptions |
This is an internal working distinction, not a set of new platform fields. It keeps business facts clear before anyone chooses wording or settings.
Explain what place changes for the customer
Consider a fictional studio renting workspace for photography at a specific location. Location is part of the offer because the customer must travel there. A useful contextual description might concern a bookable studio environment for a defined photography project, provided that is what the business supplies.
Compare a digital service developed in the same city. If customers receive the same offer regardless of the company’s address, the city may contribute little to the use-case explanation. It does not need to appear in every hint simply because the business is locally based.
Ask what the sentence loses when the place name disappears. Does it remove necessary information about where the service happens, or simply shorten a generic audience label? The hint specificity guide helps assess whether the detail carries meaning.
Record the service boundary as a business fact
If the business only accepts work within a certain area, that boundary needs to be known and current. Ask the service owner what it means in practice. Does it apply to every engagement, selected types of work or a case-by-case assessment?
Do not use “near you” as a substitute for checking. The phrase can imply proximity to the reader without support from either the offer or the advertising arrangement. Describe the real delivery method and use verified location information where necessary.
A practical requirement, such as work needing to happen on site, may provide relevant context. The constraint-led hints guide explains how to connect it to the offer. Geographic reach remains a separate question.
Also distinguish where the service will be used from where the customer is while planning a purchase. Someone might book the fictional studio ahead of a trip. That does not establish their location during planning. Describe “photography at the bookable studio” as the offer’s relationship with place, and record the campaign owner’s intended geographic selection separately. A need involving a location is not evidence of the person’s current presence there. Resolve that distinction in the brief before passing a geographic requirement to the person configuring the campaign.
Three geographic questions to separate
- The offer
The customer books a physical workspace.
Checkpoint - Service fact
Confirm where the service is actually provided.
- Campaign requirement
Handle geographic selection separately from hints.
Reconsider
Do not let the city replace the need
A list repeating one service term beside several city names may appear extensive while explaining little about the customer’s task. Return to the work. Does the customer need premises to use, a technician to visit or assistance delivered remotely? These are different situations.
If the task and offer are identical across locations, the brief does not need a separate editorial story for each name. Where conditions differ, document the difference concretely. Otherwise the location variants become repetition that is difficult to maintain accurately.
Also inspect the visible promise. A hint describing a specific local service should not accompany an ad implying nationwide physical provision without support. Use the hint-to-ad promise comparison to locate such contradictions.
Leave two separate instructions in the brief
The editorial instruction should explain the offer’s relationship with place, such as a bookable workspace at a stated location. The configuration instruction should record the geographic requirement that needs investigation using the functions actually available. Do not combine these into one sentence in the hint list.
Do not try to compensate for an unavailable geographic option by repeating the place name more forcefully. That makes the description more categorical without establishing the intended restriction. Refer the question to the person responsible for the account’s actual configuration.
A completed review should show what the location means to the customer, which service facts are confirmed and which separate setting needs verification. Place then has a clear role in the ChatGPT advertising plan without a language choice being mistaken for a technical control.
Sources and scope
Separate place information into the offer’s actual context, the business’s service area and independent geographic campaign configuration.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.