Please help us help you and fill where relevant:
Your LimeSurvey version:  Version 3.18.0+190923
Own server or LimeSurvey hosting: Self Hosted CentOS / WHM / Cpanel
Theme: Vanilla / Fruity
==================

We are developing surveys using Token based persistence and resume later. When testing the survey, and clicking "Resume later", there is a response that the responses have been saved.

However, our participants have not yet entered an email address and do not get the screen asking for email address / password to save their responses. So, while the responses may be saved, there is no way for the participant to return to the survey. Unless they copy the url with the token.

Could I be missing a configuration option? Any help greatly appreciated!

Not a solution to your problem, because I never even thought of doing what you are trying to do, but what I don't get: Why using these to features together?

If you have tokens with token based response persistence, you do not need "resume later", because clicking on the link again, they will get back to where they have left off. So I am not quite sure what "resume later" should do in this scenario? What does it add?

So do I.
No idea what it should be used for in a token based survey.
Therefore this link is removed from the used theme.

But an idea to investigate.

Joffm 

holch wrote:

If you have tokens with token based response persistence, you do not need "resume later", because clicking on the link again, they will get back to where they have left off. So I am not quite sure what "resume later" should do in this scenario? What does it add?
 

If you nuse a token based survey + persistence + allow save : user can save current page without move next. Save but stay on current page.

Else
>However, our participants have not yet entered an email address and do not get the screen asking for email address

They have a token , then no need to a save system.
If they don't know the token : maybe best is to show it inside the survey.

Your issue is unclear here …

We are using tokens to store values that allow us to track a participant through a series of surveys, passing values from one survey to the next. However, we don't have an email address for these participants until they finish the second survey.

The user does not initially get a token based url. Our initial survey is a non token based screener Survey. If they pass the screener, we redirect them to our self hosted survey dashboard, which creates a token in the second survey and redirects them there automatically.

But also, it's a wide audience, and as we know, people can be lacking in motivation, attention span and/or ability to follow logic. If something is not easy, they tend to just skip it.

It's more likely that a person will come back to finish a survey if they have a link in their email they can come back to find the url.

If you nuse a token based survey + persistence + allow save : user can save current page without move next. Save but stay on current page.

Makes sense, for surveys where there are many questions on one page the "allow save" can actually make sense.

@Joe: Understood. Within your scenario, I can understand why you want to use both, token based response persistence AND the save for later option. But I have no solution for your "problem".

holch wrote:

@Joe: Understood. Within your scenario, I can understand why you want to use both, token based response persistence AND the save for later option. But I have no solution for your "problem".

 

Why not use
- Token based
- No response persistence ?
 

I am also looking for same solution
- Token based
- response persistence
- Save response for later