Measuring per-market performance in GSC and GA4
Every lesson in this phase created per-market surface: URLs, translations, hreflang clusters, market-specific data. The closing discipline is seeing per market - because aggregate numbers hide exactly what internationalization needs you to know. A store "growing 15%" may be one thriving market masking two stalled ones; a "successful" German launch may be ranking on brand terms only. Segmentation is where expansion strategy meets evidence.
GSC per market: coverage, queries, routing
The subfolder architecture pays its measurement dividend: market URLs share your domain property, segmentable by page-path filter (/de-de/). The practical setup: your domain property as truth, plus the page-filter views (or separate URL-prefix properties per market subfolder, which some teams prefer for clean per-market dashboards - both work; pick one and standardize). The per-market reading, monthly, mirroring Phase 3's rhythm: coverage (indexed pages per market subfolder against what should exist - the first place partial-translation problems and market-launch indexing lag show, per the sitemap thread from Phase 5); query mix (brand versus non-brand per market - a market living on brand queries hasn't actually penetrated its search market; non-brand growth is the internationalization success metric); routing health (last lesson's check: impressions for German queries landing on the right market's pages); and market-specific demand patterns (the query language per market feeding back into the translation-keyword work from lesson three - per-market GSC is your per-market keyword research, free).
GA4 per market: behavior and the money
GSC shows the search market; GA4 shows what markets do with the traffic. Segmentation handles: page-path (same subfolder logic), user geography, and - cleanest for Markets setups - a custom dimension carrying the market/locale context if your implementation sends it (worth the small setup; path-based segmentation breaks on the pages markets share). The per-market metrics that earn review time: conversion rate per market (the single most diagnostic number - a market with healthy traffic and half the conversion rate of home has a localization problem: pricing, payment methods, delivery promise, or trust furniture from last lesson); AOV and product mix per market (markets buy differently; this feeds per-market merchandising and the market-specific collection decisions from lesson two); funnel drop-off comparison (where each market's funnel leaks against your home baseline - checkout-stage divergence points at payment/shipping localization, product-page divergence at translation quality); and channel mix per market (young markets lean paid; the organic share growing is the market maturing).
The rhythm and the honest questions
Per-market review joins the standing calendar: monthly light (coverage, clicks, conversion per market - fifteen minutes across markets on a dashboard built once), quarterly deep (the full reading above, plus the native-speaker walk from last lesson). And twice a year, the strategic pass this data exists to enable - per market: is it growing into its potential or plateaued? Does its unit economics justify its operational cost (the Phase 1 warning - "two well-run markets beat six neglected ones" - now answerable with numbers)? What's the next constraint: coverage, translation depth, local authority, or demand itself? Internationalization done right is a portfolio you actively manage, and this measurement layer is what makes it management rather than hope. That closes the loop this phase opened: architecture, data, translation, routing, compliance - and now the instruments to see whether it's all working, market by market.
Next phase: Data Operations at Scale