Continent and subcontinent dimensions
Continent and subcontinent are GA4's two broadest geography dimensions, sitting above country, region, and city. Both are derived from coarse IP-based geolocation, so they inherit its imprecision. Subcontinent uses regional groupings (such as Northern Europe or South-Eastern Asia) that do not always match colloquial expectations, which is the most common source of confusion when reading these reports.
What this means
Continent and subcontinent are the top two rungs of GA4's geographic hierarchy: continent (Europe, Asia, Americas) and the finer subcontinent grouping beneath it. Both are inferred from the visitor's approximate IP location, the same source that feeds country and city.
They are useful for executive-level 'where in the world' summaries that country detail would clutter.
Why groupings surprise
Subcontinent uses defined regional buckets — Northern Europe, Western Asia, South-Eastern Asia and so on — that may place a country differently from everyday usage. Because the underlying signal is IP geolocation, VPNs, corporate egress, and carrier routing can also misplace visitors at this coarse level.
Treat both as approximate regional indicators, and drop to country only when the question genuinely needs it.
- Top two levels of the geo hierarchy
- Derived from coarse IP geolocation
- Subcontinent groupings are defined, not colloquial
How it appears in analytics and logs
A continent/subcontinent value is an IP-derived region. A country that lands in an unexpected subcontinent reflects GA4's grouping definitions, not an error in your data.
Diagnostic use case
Use continent and subcontinent for the highest-level geographic split — global regions — while remembering both come from coarse IP geolocation.
What WebmasterID can help detect
WebmasterID can report coarse continent-level geography first-party from edge signals, without storing raw IP addresses or precise location.
Common mistakes
- Expecting subcontinent groupings to match everyday usage.
- Treating IP-derived region as precise location.
- Ignoring VPN and routing effects at the continental level.
Privacy and accuracy notes
These dimensions describe coarse regions, not individuals, and GA4 derives them without exposing precise location. WebmasterID infers only coarse geography first-party.
Related pages
- Country dimension (coarse, edge-derived)
The country dimension assigns each visit a country, derived by looking up the visitor's IP address in a geolocation database — often at the CDN edge. It is intentionally coarse: country-level, not address-level. VPNs, proxies, mobile carrier routing, and corporate egress can all place a visit in the wrong country, so it is a strong aggregate signal and a weak per-visit one.
- Metro dimension
Metro is the geography dimension that maps a visitor to a designated market area (DMA) — the media-market regions used in the United States. GA4 derives it from coarse IP geolocation. Because DMAs are a US construct, metro is populated mainly for US traffic and frequently reads '(not set)' elsewhere, which is expected behaviour rather than missing data.
- Geo-IP database limitations
Geo-IP databases map IP ranges to locations, but those mappings lag reality: allocations change, addresses are reassigned, and ranges can span wide areas. This page explains the structural reasons geo estimates drift and why country is always an estimate, not a fact.
- Privacy-first analytics
Coarse geography without storing raw IPs.
Sources and verification notes
- Google Analytics Help — [GA4] Dimensions, metrics, and other termsLists continent and subcontinent geography dimensions.
- Google Analytics Help — [GA4] How geolocation is derivedExplains IP-based geolocation feeding geo dimensions.
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.