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:

• simply add the segment to metadata, and user will be able to choose "Contains" condition, as well as "Is" (eg. language contains 'it' will match 'it,en')
• if user manually set the language via the &lang= parameter (see tracking api reference), then they could simply create segments with 'Is' condition: language is 'it'

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

+1

now that we store only one language in the DB field (#5365) this can be done quite easily I think 👍
@sgiehl maybe you want to take a crack at it