ChatGPT ads for local business.

Use supported location targeting, then qualify the exact service area

ChatGPT Ads Manager Beta supports campaign level country targeting, and in the United States it supports state, designated market area, and ZIP code targeting where those locations are available. OpenAI also documents that supported states or regions, cities, DMAs, and postal codes may be available depending on the country. Availability is not uniform across countries or accounts, so the practical first step is to search your locations in the campaign location picker and confirm what you can actually select today.

Confirmed support still leaves an operating gap. A supported ZIP code selection sits much closer to a dispatch map than a whole metro, but radius targeting around a single address is not currently documented, availability can change, and any selected area can still contain streets, travel corridors, and property types your crews cannot serve promptly or economically. Close the remaining distance in three places: state the coverage clearly in the ad, confirm it on the landing page, and ask for location at the start of the phone or form journey.

Location choices use location IDs obtained through a geo lookup API, and OpenAI publishes a downloadable location catalog as CSV alongside the in product picker. The Advertiser API targeting reference and the Ads Manager Help Center do not always describe location capabilities in the same detail, so treat the picker inside your own account as the practical answer about what is selectable. If no location targeting is supplied, a campaign can target all available locations, which is too broad for most local operators.

Make the ad perform the first geography check

The ad unit includes the advertiser name, favicon, title, copy, landing page, and image asset. Use the title and copy to name the practical footprint before a person clicks. A town cluster, a named side of a metro, or a concise coverage statement is more useful than a broad city claim. This may reduce clicks from people you cannot serve, which is a feature when the campaign pays per valid click.

Keep every coverage phrase operationally precise. If crews serve selected northern suburbs, do not shorten that into the entire metro merely because a broader area was easier to select. If availability changes by service, branch, day, or licensing boundary, separate the campaign structure and creative where practical. A truthful narrower promise protects the caller’s time and gives intake staff a claim they can consistently honor.

Illustrative example: a title could say “Drain assessment for North Metro towns,” while the description names the principal towns and asks homeowners to check coverage. This is not a template to publish unchanged. Replace it with the business’s real service, actual locations, and current availability, then have dispatch approve the language before launch.

• Name useful places

  Prefer recognizable towns, districts, or a clearly defined portion of the metro over vague phrases such as locally owned and nearby.

• State important exclusions

  When a boundary commonly causes confusion, clarify the covered side or invite a service area check before promising an appointment.

• Match the schedule

  Review time sensitive copy against crew calendars, branch hours, and intake coverage so the advertised next step remains available.

• Keep the destination aligned

  Send the click to a page that repeats the service and geographic promise rather than a general homepage with broader claims.

Turn the landing page into a service area filter

The landing page should answer “Do you come to my address?” before asking for a long form. Put a visible service area list near the primary action, grouped in a way residents recognize. An honest coverage map can support the list, but it should not imply that every point inside a decorative outline receives identical service. Explain border areas, services with narrower coverage, and any requirement to confirm availability.

For businesses with branches, route visitors toward the nearest appropriate location using the location they intentionally provide. Explain which branch handles the enquiry and preserve a manual choice when automatic logic could be wrong. Do not infer certainty from a rough device location. The operational question is not which branch is closest in a straight line, but which qualified team can accept that service at that address.

Keep the page consistent with dispatch reality. If some towns receive scheduled work but not urgent visits, say so plainly. If a service is available only from one branch, avoid presenting every branch as equivalent. Forms should capture town or postcode early enough to route correctly, while phone calls need a comparable verbal check. The page can reduce wasted contacts, but it cannot replace intake rules for ambiguous boundaries.

1. 1

   Repeat the exact coverage promise

   Carry the town cluster, district, or metro portion from the ad into the page heading and nearby explanatory copy.

2. 2

   Show the service area visibly

   Provide a readable place list and an honest map where useful, with clear notes for border areas and service specific exceptions.

3. 3

   Collect location early

   Ask for the minimum location detail needed to check coverage and send the enquiry to the correct branch or dispatch queue.

4. 4

   Confirm the next step

   Tell eligible visitors what happens next, and give out of area visitors a respectful answer instead of allowing an impossible booking request.

Use context hints for situations, not as a location control

Context hints are set at the ad group level. They describe conversations, topics, or keywords that may help the platform understand relevant situations, but they are not exact match keywords and do not guarantee delivery in a particular conversation. Treat them as supporting context for the service and local need, while the campaign’s location selection controls which supported countries, states or regions, DMAs, or postal codes are eligible.

Write hints around legitimate customer situations your operation wants to handle, then keep the geography claim in creative and on the destination. A hint might describe a homeowner comparing local providers or planning a permitted service, but it should not be treated as a hidden list of precise places. Relevance also considers the current conversation, landing page, ad title and copy, advertiser targeting selections, and other documented signals.

Review ad groups by operational coherence. One ad group should not combine different branches, service boundaries, and promises if a single piece of copy cannot describe them truthfully. Separating materially different coverage patterns makes context, creative, routing, and measurement easier to interpret. It also gives operators a cleaner way to pause an area when capacity changes without removing coverage that another branch can still honor.

Decide whether partial area coverage is worth testing

A wide selection such as a state or DMA is not automatically attractive because it contains towns you serve. Where supported ZIP codes already cover your footprint, prefer that tighter selection and confirm each one in the picker. Where they do not, start with the share of the selected area that fits your dispatch map, where eligible households are concentrated, and whether copy can explain the footprint without becoming confusing. Then examine actual drive times, licensing, crew starting points, return trip burden, appointment windows, and the specific service capacity available during the proposed campaign.

Next, define how the business will classify enquiries from inside the selected locations but outside the service area. Those contacts are a foreseeable cost of any selection wider than the dispatch map, not proof that the channel has failed. Record them separately from wrong service requests, spam, missed calls, and qualified opportunities. A campaign can only be judged fairly when media selection limits and the company’s own qualification rules are visible in the same review.

Enter the metro only if the likely learning is useful and the operation can respond consistently. The right decision may be a focused test, a later launch after routing improves, or no launch while coverage remains too fragmented. Avoid expanding the claimed area merely to make the platform geography appear to fit. Advertising should reflect the territory the business serves, not pressure dispatch into accepting unworkable journeys.

Close the final geography gap on the phone

Ask location near the beginning of every new customer call, before a long diagnosis or an implied commitment. A simple town and postcode check lets intake select the correct branch, confirm the requested service, and explain any border rule. Put the routing logic in the call taker’s workflow rather than relying on memory, especially when nearby towns have similar names or branches overlap.

Prepare an out of area script that is brief, respectful, and accurate. Staff should acknowledge the request, explain that the address falls outside current coverage for that service, and avoid promising a referral unless a vetted process exists. Record the call as out of area with the town, campaign source, and requested service. Do not hide it as an unqualified lead with no reason, because that erases evidence needed for geographic decisions.

Audit the handoff between marketing and dispatch. If the ad names a town but call takers reject it, determine whether the copy, map, routing table, or schedule is wrong. If callers repeatedly arrive from one unsupported pocket, sharpen the ad qualification and page language before assuming targeting can exclude it. Repeated patterns can also reveal a future expansion question, but demand alone does not establish that expansion is operationally sensible.

Measure booked work by area and branch

Multi-location businesses and franchises need one agreed territory source before campaign setup. Document branch boundaries, overlap rules, licensing constraints, service exceptions, and who owns a lead when the nearest branch lacks capacity. Creative should identify the serving business accurately, and the landing experience should not imply that one franchise can accept work assigned to another. Escalation rules are essential for addresses close to a boundary.

Use static UTM parameters to encode durable campaign information such as source, campaign, service area, promoted service, creative variant, and intended branch. OpenAI documents that static tracking parameters persist on ad clicks and can be read in existing analytics tools. Capture those values with calls and forms, preserve the original source in the CRM, and join them to the address eligibility decision, branch assignment, appointment, and booked work.

Ads Manager Beta reporting includes impressions, clicks, spend, click through rate, average CPC, average CPM, and conversions. Those measures explain delivery, but local operators also need their own area outcome view: qualified enquiries, out of area contacts, appointments, booked work, cancellations, and branch reassignments by town or service zone. Review counts as well as rates, and annotate changes to boundaries, schedules, scripts, or landing page logic.

Use the review to make geographic decisions, not merely produce a dashboard. If one town generates suitable booked work and another repeatedly falls outside coverage, refine copy and routing where possible. If a branch is full, pause or change the promise rather than continuing to invite work it cannot accept. Good local measurement connects platform delivery to the dispatch board and preserves the reasons behind every rejected enquiry.