We have noticed that on some browsers, data users enter into a survey will save automatically upon closing or reloading the browser. On other browsers, users must hit the "next" button at the bottom of the screen in order for data to be saved. After a bit of poking around with developer tools, we have determined that there is a "saveProgress" function function that runs on some browsers and not on others. When this function is running, it saves progress anytime a browser reloads (i.e., either by hitting the reload button on your browser or by closing your browser tab and opening again). When the function is not running, data is lost.
From our testing:
- The function does seem to be running on Windows/Chrome, Windows/Firefox, Windows/Edge, MacOS/Firefox, MacOS/Safari.
- The function does not seem to be running on MacOS/Chrome or any of the mobile OS/browser combinations we’ve tried. We tested across both iOS and Android.
This raises a few questions:
- Does anyone have a full list of the operating systems/browsers where this function is active?
- Does Qualtrics have a plan to make this function active (and maintain this function) across all browsers?
- How are administrators successfully messaging to survey takers that in order to guarantee that survey progress is saved, they must hit the "next" button. We are using personal links which enable users to being their survey, exit, and come back later. We are having a lot of issues where a user will answer the question on the survey screen, but then closes their browser without hitting the "next" button. All data up to that screen is saved because they have hit the "next" button on all prior screens, but the data they entered on the screen they were on when they exited the survey is lost. In these users' defense, it is a bit unnatural to ask them to hit the "next" button before they plan to continue with the survey. If there was a "save" button, that would be a little more natural, but I understand Qualtrics doesn't use "save" buttons. Has anybody successfully messaged this to users? If so, how? Or have you found any workable solutions for cases where users commonly do not finish surveys in a single sitting?
Very curious to hear the community's thoughts on these issues because we are struggling with them.