Hi all,
I am still awaiting a response for the following issue I am having. If any one can offer support, please do so.
I have a potentially complex coding question that I would like some support with. The two points below are for context of the information and current setup we have:
(1) For a number of our projects we have custom code set-up to measure specific timestamps - this is done through JS and uses a hidden text-entry box to automatically insert a timestamp when a participant clicks onto the next page.
(2) We also have set up a workflow for participants to complete Part 2 of our project after 7 days (done by the usual workflow mechanics).
However, we have experienced issues with participants having 99% completions in which they have finished everything, get to the final page, but do not submit their responses. We have data to be recorded set around 48 hours, but this adds to the time in which part 2 is sent (so more than 7 days).
So, my question is:
Is it possible to convert the text-entry data that is automatically generated from the JS into date/time data, which is then automatically activates the Part 2 e-mail being sent so that Part 2 arrives exactly 7 days after the timestamp is generated?
Overall, this should stop those at 99% having problems in receiving their Part 2 e-mail at the correct time (and reduces our e-mails from them) and so does not increase the delay from 7-days.
Please let me know there is a solution to this.
Happy to provide any additional details if necessary.
Thank you in advance.
Help still needed!! Is it possible to have custom code to send 'Part 2' e-mails based on timestamps?
Best answer by Tom_1842
Hi there, I do not think it is possible to base the workflow that distributes Survey 2 on timestamps collected within Survey 1.
That is interesting about respondents getting through everything and not submitting their surveys. Does your 'Next' button for this final page read 'SUBMIT' ? Maybe a Text/Graphic question that includes instructions to respondents about needing to click the SUBMIT button in order to receive Survey 2 would help. You could also implement an auto-advance on this last page by using the Timing question or the below JavaScript:
setTimeout(function() {
jQuery("#NextButton").click();
}, 5000);
Another approach might be to have 2 separate workflows that distribute Survey 2, each with a condition based on an Embedded Data field that only gets updated at the bottom of the Survey Flow. In the below example, a workflow could distribute Survey 2 with a 7 day delay for respondents where IsFinished=yes, and another workflow could distribute Survey 2 with a 5 day delay for respondents where IsFinished=no. With 48 hour response recording, the incomplete responses should receive Survey 2 on the 7th day, similar to those that submitted the survey.
+28Hi there, I do not think it is possible to base the workflow that distributes Survey 2 on timestamps collected within Survey 1.
That is interesting about respondents getting through everything and not submitting their surveys. Does your 'Next' button for this final page read 'SUBMIT' ? Maybe a Text/Graphic question that includes instructions to respondents about needing to click the SUBMIT button in order to receive Survey 2 would help. You could also implement an auto-advance on this last page by using the Timing question or the below JavaScript:
setTimeout(function() {
jQuery("#NextButton").click();
}, 5000);
Another approach might be to have 2 separate workflows that distribute Survey 2, each with a condition based on an Embedded Data field that only gets updated at the bottom of the Survey Flow. In the below example, a workflow could distribute Survey 2 with a 7 day delay for respondents where IsFinished=yes, and another workflow could distribute Survey 2 with a 5 day delay for respondents where IsFinished=no. With 48 hour response recording, the incomplete responses should receive Survey 2 on the 7th day, similar to those that submitted the survey.
https://community.qualtrics.com/XMcommunity/discussion/comment/48862#Comment_48862Thanks Tom, for your response. Apologies for the delay in my own response to this.
For context, because our research is not typical surveys and involves a number of tasks, participants sometimes get to the end and just close the browser when they read the debrief form (despite attempts to get them to submit).
Your second approach sounds like a great and very simple solution to the issue. Thank you for providing me with an answer.
Can I just ask one more question about the "IsFinished" embedded data:
Am I correct in thinking by the survey flow you have produced here, that all participants have a "IsFinished = No" at the beginning, until they reach a point in the survey that changes to "IsFinished = Yes"? This will be where they will either submit their response (100%) and be sent Part 2 after 7 days, or may stop (99% complete) and be sent Part 2 after 5 days (following the 48 hour recorded response timeout).
Thanks.
+28Super_Recognisers Sure thing! Correct, in the above, all participants will be assigned an IsFinished value of "no" which will only change to "yes" when the respondent reaches that element in the Survey Flow. You might even set it up so that your debrief text is in its own block and set the IsFinished = "no" element right before that block, like in the below. This way, only those that stopped the survey on the debrief text block would have the "no" value and meet the condition of the workflow that sends the survey out 5 days later upon response recording (not those that stopped halfway through).
Leave a Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.