Rarely. Piano Analytics reads the language directly from the visitor's browser, so a language shouldn't go unrecognized. In very rare cases the browser doesn't provide it, for example when it blocks JavaScript. Those visits show the value "Undefined" in the Browser language property.
Browser language and page language
If you see missing or unexpected values in a language analysis, check which property you're using:
|
Property |
What it shows |
How it's filled |
|---|---|---|
|
Browser language |
The language set in the visitor's browser |
Automatically, by Piano Analytics |
|
Language
|
The language of the page, which may differ from the browser's |
By your own tagging |
For example, a French speaker whose browser is set to French can read your English page. Browser language shows French, and a page language property shows English.
If your page language property shows "N/A", the cause is usually your tagging, not the browser. It may not be sent on every event, such as click events, and custom properties are only collected for opted-in visitors unless you add them to your consent exemption. Check your implementation and your consent settings.
Language of the interface
Piano Analytics shows some values, such as sources and geolocation, in English whatever your interface language. If a browser tool translates the interface, it can change how values appear, so turn off automatic translation when you use Piano Analytics.