# Read GA4 performance by geography

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

Geographic cuts from GA4, the neutral side of every market debate.

**Intent.** The site's own market map: sessions, engagement, conversions by country.

## When to use

- Market prioritisation.
- Cross-checking ad platform geo claims.

## When not to use

- No specific contraindication beyond the preconditions below.

## Sources

Required: Google Analytics 4

## Preconditions

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

## Inputs

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

## Procedure

1. Run the geo report. — tools: `ga4_run_report`
2. Compare against ad platforms' geo claims where relevant.

## Decision rules

- **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 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

- IP geography lies at the margins: VPNs and roaming blur small-market reads.

## Output

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