We should have a segment for "user language". Maybe this involves rewriting the data and storing only one language, instead of storing the whole string as we do now in location_browser_lang
I'm really surprised that particularly "browser language" is not available for segmenting.
Was it just forgotten, or it is hard to add, as suggested here?
not trivial to add, since we don't store the language in the database, but we store the Accept-language string (which can contain several languages).
So to provide an accurate browser language feature we should first store only one language in the field "log_visit.location_browser_lang"
Forget about previous comment,
an easier solution is:
Created ticket: #5365 do not store Accept-language full string, only store detected language
I believe it is a very important feature to have and I hope it will be included in your next release