Translate automations based on browser language

Hi @alexweber 

An alternative approach to the suggestion by @Omar is to use a custom event for the browser language detected.

The script for that, which I’ve tested, is below. Also what I’m seeing in Klaviyo for that event. The script would be on all pages. 

Note that I am not a pro coder so, even though this works for me, I suggest you run it by someone who is a coder or maybe a forum member will comment. 

Here’s an idea on how you could use this event for your use-case:

1. Create a flow triggered using this custom event for each of the 3 languages you support. In the flow add a custom property with the contact’s browser language. These should be one-time flows so contacts enter it only once on their first site visit. Example below for one such flow for en-GB OR en-US. The custom property ‘browser_lang’ is set to English in this example.
2. For campaigns and flows, you’d need to add a definition or filter to select those with a specific value in their custom property ‘browser_lang’
3. Update ‘browser_lang’ with user input for their language preference on any forms you have too.

Note some considerations

• If a visitor uses multiple devices/browsers with different language settings: they could enter multiple flows stated in 1). 
• You will be generating lots of events in Klaviyo!

Just another solution for you to explore though!

Regards

Andy 

<script>
(function() {
  // FGet the browser's language
  function getBrowserLanguage() {
    return navigator.language || navigator.userLanguage;
  }

  // define _learnq
  window._learnq = window._learnq || [];

  // Push custom event to Klaviyo - BrowserLanguage
  var item = {
    "BrowserLanguage": getBrowserLanguage()
  };

  window._learnq.push(["track", "BrowserLanguage", item]);
})();
</script>