Geographic and map reports
GA4's demographics and tech reports include geography — country, region, city — shown in tables and on a geo map. Location is inferred from IP address (with IP not stored), so it is approximate, coarser at city level, and affected by VPNs, mobile networks, and IP anonymization. Read it as a regional signal, not precise location.
What this means
GA4 reports geography under user attributes — Country, Region, City — and offers a geo map visualization that shades or sizes locations by a metric. It lets you see where your audience is concentrated and compare regions on engagement or conversions.
Why geo is approximate
Location is inferred by mapping the visitor's IP address to a place; GA4 uses the IP for this but does not store it. IP geolocation is reliable at country level and progressively coarser at region and city, and it is skewed by VPNs, corporate proxies, and mobile carriers that route through distant gateways. IP anonymization and consent can also leave a '(not set)' bucket. Use country and region confidently; treat city as indicative, and expect a residual unattributed share.
- Country, region, city dimensions plus a geo map
- Inferred from IP; the IP itself is not stored
- City level is coarse; VPNs and carriers skew it
How it appears in analytics and logs
Geo dimensions are IP-derived estimates. A surprising city or a large '(not set)' share reflects the limits of IP geolocation — carrier routing, VPNs, anonymization — not necessarily a tracking fault.
Diagnostic use case
Understand roughly where an audience is — which countries and regions drive traffic and conversions — to inform localization and targeting, without over-trusting city precision.
What WebmasterID can help detect
WebmasterID derives coarse first-party geography without retaining raw IPs, so regional signals come from owned data privacy-safely.
Common mistakes
- Trusting city-level geo as precise location.
- Reading '(not set)' geo as a bug rather than a limit.
- Ignoring VPN and carrier routing when interpreting regions.
Privacy and accuracy notes
GA4 infers location from IP and does not log or retain the IP address itself. Geolocation is coarse by design; treat it as regional, not as pinpointing individuals.
Related pages
- Secondary dimensions in reports
Adding a secondary dimension cross-tabulates a report by a second attribute — channel by device, page by country. It is the fastest way to add context to a table, but it multiplies row cardinality, which can push rare combinations into an (other) row and increase the chance of thresholding.
- GA4 standard reports overview
Standard reports are GA4's fixed, pre-aggregated reports — grouped into collections like Life cycle and User — that load fast because they read from aggregate tables. Unlike explorations they are not generally sampled, but they apply (other) row grouping and can differ from exploration numbers, which query event-level data with their own scope.
- Comparisons in GA4 reports
Comparisons let you split a standard report into side-by-side subsets defined by dimension conditions — for example, mobile vs desktop. They are the standard-report counterpart to explorations' segments, but they are simpler, evaluated inline, and limited to dimensions available in that report.
- Website observability
Coarse first-party geography without storing IPs.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.