@mattab opened this Issue on May 23rd 2013 Member

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

@anonymous-piwik-user commented on March 23rd 2014

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?

@mattab commented on March 24th 2014 Member

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"

@mattab commented on May 6th 2014 Member

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'
@mattab commented on June 19th 2014 Member

Created ticket: #5365 do not store Accept-language full string, only store detected language

@oussjarrousse commented on March 18th 2015

I believe it is a very important feature to have and I hope it will be included in your next release

@fnagel commented on June 2nd 2015


@mattab commented on June 10th 2015 Member

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

This Issue was closed on June 15th 2015
Powered by GitHub Issue Mirror