RecipeGoogle Ads
Resolve geo targets for a Google Ads launch
Geo target suggestion turned into the launch's location list, homonyms caught.
IntentThe exact geo target constants for the market brief, ambiguities resolved.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Campaign builds targeting specific cities or regions.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Suggest geo targets from the brief's place names.
Confirm each match's type and parent before it enters the build.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A place name matches several constants
Conclude
Resolve by parent region explicitly: the wrong Paris is a classic launch bug.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- City targeting excludes nearby intent: 'people in X' misses 'people searching for X from elsewhere'.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.