Skip to main content
Jef Vanlaer
Jef Vanlaer
Helper ⭐️⭐️⭐️
February 4, 2021
Current Behaviour

Browser language as standard user attribute

Related products:PX Engagements
  • February 4, 2021
  • 3 replies
  • 80 views

For our scalability initiatives, it would be tremendously valuable to have browser language as a standard user attribute in Gainsight PX (and exportable to S3 and Gansight CS). We are creating Gainsight CS contacts based on user data from Gainsight PX, which we leverage in the Journey Orchestrator. However, as browser language is not available in the export (although used in Localization), we are not able to address our users in their own language (which is very important for our German customers, for example).

    3 replies

    link_black
    link_black
    Gainsight Employee ⭐️⭐️
    February 4, 2021

    Thanks for posting @Jef Vanlaer !

    PX does capture last browser details, but not last browser language details.  In the near term, you can create a new custom User Attribute and have your development team pass the browser language details within the PX Identify call. 

    I believe the proper JavaScript to retrieve these value to be as follows:

    navigator.languages → ordered list of preferred browser language

    navigator.language → preferred browser language

     

     

    -- Link
      Jef Vanlaer
      Jef VanlaerAuthor
      Helper ⭐️⭐️⭐️
      February 4, 2021

      @link_black Thanks for the reply. I'm not sure if having our development team implement it will go faster (but I'll discuss it for sure) and figured it would probably be useful for more customers, so I posted it as a feature idea.

        Ashton
        Ashton
        Contributor ⭐️⭐️⭐️⭐️
        May 22, 2024

        Gainsight has added Browser Language in a limited capacity. It is available when checking to load an engagement or set a user into a segment. I believe this is due to the fact that these checks happen on the user’s end (in their browser) and the Identify call is not sending the actual navigator.language value back to Gainsight to store. 

        This is why we are not able to create reports or group by language which would be my enhancement. But seeing that Language is not actually passed to Gainsight and it can only limited do comparisons while in the user’s browser this makes sense that the workaround is still to send a value in the Identify Call that specifies the browser language. 

        Terms & ConditionsAccessibility statement