Thanks Akdashboard. I am familiar with language codes. What I am trying to discover is how to RESEND an invitation WITHOUT uploading the mailing a second time. I don't see anywhere in the distribution process where I can set the "Language" attribute that is mapped when the contacts are uploaded to the mailing list.
Thanks TomG. I guess I didn't understand how to use the Browser Meta Info question. I thought that the values captured would show up in the response data immediately (mine are all blank). So I will have to create embedded data elements for the attributes I want to capture and pipe-in information from the Browser Meta Info question? Still being a newbie to this platform, how (and where) exactly would I go about installing my own JavaScript?
I too am transitioning from another survey tool (where I had no trouble determining the device type and language) to Qualtrics and am interested in capturing the device type and browser language. Based on the online documentation I have seen, my understanding is that Q_Language represents the language in which we are viewing the survey. What I am trying to determine is the default language the survey-taker's browser is configured for. Also, since my organization is running on the JFE survey engine, I'm not able to get anything from the Browser Meta Info question (I'm certain what "pipe the Operating System and Screen Resolution from a MetaInfo question into a JavaScript and parse" means) and have to rely on the built-in UserAgent embedded data element. My problem however, is that I cannot find any information explaining how to parse the resultant text string. Does anyone have some insight to this?
Since posting the original question I have discovered that "Question Export Tag" can be used to dictate the "question ID" of a row in a matrix table. This is primarily for export files when you expect specific text in the column header. I am still wondering how I can establish a specific question label for a row of a matrix table. This is reduce the burden on dashboard authors having to modify the labeling of survey data elements when the survey data is brought into a dashboard. The idea being that they would have to always make the same exact edit to the field name in order to have consistency across numerous dashboards.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
