Country, region, and city describe an approximate network exit location, not GPS or a person's residence. VPNs, mobile networks, proxies, and IP database coverage affect the result.
Evumi resolves trusted proxy information and local GeoIP data at ingestion, before enqueueing. Raw IP addresses and User-Agent strings are not stored in analytics queues or tables. Consequently, unavailable historical geography cannot be reconstructed later from a retained visitor IP. Coordinates are approximate and rounded; they should not be presented as a street address.
Query and display
- Use
visit:country,visit:region, andvisit:cityseparately. Country codes are ISO-style two-letter codes such asCN; translate them for display. - An empty country value means Unknown. Keep it as its own row; do not turn it into a country, discard it, or label it as bot traffic.
- A region should retain its country context; a city should retain country/region context when available. Do not merge identically named cities across countries.
- Geographic session dimensions use first-touch attribution; moving networks during a session does not relabel its starting location.
- The longest ranking bar represents the largest row, not 100% of all traffic. For a share, use the report's total visitor denominator and expose unavailable denominators as
—. - Missing imported dimensions are a coverage limitation, not a measured zero. Geography imported from another provider retains that provider's methodology.
Check a deployment
Send a controlled request through the same public ingress as the tracker. Verify the report contains the expected country and inspect the matching event receipt. A healthy Worker or a loaded MMDB file alone does not prove end-to-end attribution. Do not trust client-supplied geo headers from arbitrary direct connections.
See the deployment skill for trusted proxy configuration, MMDB replacement, and troubleshooting without retaining raw visitor IPs.