Language

The Language report shows which languages your visitors' browsers are set to. It lives in the Locations panel, next to Countries, because it answers the question countries only pretend to answer: not where your visitors are, but what they read.

Click any language and the dashboard filters by it, and the same list drills into its variants: click English and you see British, US, and Australian English. Click the filter off and you are back to the overview.

Where this comes in handy

Multilingual countries

Switzerland has four official languages. A Swiss visitor row tells you nothing about whether to write in German, French, or Italian, and the same problem holds for Belgium, Canada, Luxembourg, and South Africa. The Language report splits your Swiss traffic into its real audiences: if 39% of your visitors read German and 25% read French, you know exactly which localization carries the most weight. It composes with every other filter, so filter by country is Switzerland first and the report shows the language split of Swiss visitors alone.

Should we translate?

Translation is a budget decision, and this report gives it a number. A US site that discovers 18% of its visitors browse in Spanish has a concrete case for a Spanish version, and one that finds 2% has a concrete case for skipping it. Combine with a filter: filter by language, then check bounce and engagement to see how visitors who can't read your content actually behave.

Locals or tourists?

Location says Spain; language says German and English. For tourism, real estate, and hospitality sites, that gap is the finding: your "Spanish" traffic is not Spaniards, it is foreign buyers and travelers researching in their own language. Country reports hide this completely.

Which English? Which Spanish? Which Portuguese?

The drill answers the variant question: en-US vs en-GB decides your spelling and currency defaults, es-ES vs es-419 decides between European and Latin American Spanish, pt-BR vs pt-PT is practically two different markets. If you are going to write one variant, write the one your visitors actually use.

How it works, and what we don't collect

Every browser sends an Accept-Language header with every request. Clickport reads only the first entry, the visitor's preferred language, and discards the rest. The full ordered list of a visitor's languages is a fingerprinting vector, so we never store it. One coarse value, no cookies, nothing to consent to. Visitors whose browsers send no language are left out, and shares are computed over identified visitors.

Filters, exports, API

Language and locale are full filter dimensions: use them from the report by clicking a row, or from the filter editor under Location, and combine them with anything else, like "language is German and country is not Germany". The languages breakdown is included in the CSV export and available in the API.