RecipeGoogle Analytics 4
Read GA4 performance by geography
Geographic cuts from GA4, the neutral side of every market debate.
IntentThe site's own market map: sessions, engagement, conversions by country.
- 2
- Steps
- 1
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Market prioritisation.
- Cross-checking ad platform geo claims.
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.
Run the geo report.
Compare against ad platforms' geo claims where relevant.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A market converts well organically but ads underperform there
Conclude
The market works, the media does not: targeting or creative finding, not a market finding.
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.
- IP geography lies at the margins: VPNs and roaming blur small-market reads.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.