# Resolve geo targets for a Google Ads launch

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Geo target suggestion turned into the launch's location list, homonyms caught.

**Intent.** The exact geo target constants for the market brief, ambiguities resolved.

## When to use

- Campaign builds targeting specific cities or regions.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Google Ads

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. Suggest geo targets from the brief's place names. — tools: `google_ads_suggest_geo_targets`
2. Confirm each match's type and parent before it enters the build.

## Decision rules

- **When** A place name matches several constants → **conclude** Resolve by parent region explicitly: the wrong Paris is a classic launch bug.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- City targeting excludes nearby intent: 'people in X' misses 'people searching for X from elsewhere'.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [campaign-launch-qa](https://www.getmcpads.com/skills/campaign-launch-qa.md)