-
Notifications
You must be signed in to change notification settings - Fork 36
Expiry
If you want to limit the time frame your participants can access and edit a survey, go to Surveys → Survey settings → Survey access window and change the settings of Access window and Inactivity Expiration (snooze).
- Start editing within: time until which users have to have accessed the survey.
If this time passed (relative to when the survey was made available for this user), users cannot access the survey anymore, but will automatically be sent to the next position in your run. If you set this to 0, users are kept at this position forever (unless you included a skip forward module before your survey in your run (see here) or an inactivity expiration time, see below).
- Finish editing within: time users get on top of the "start editing" time if they accessed the study.
This setting is only relevant for users that accessed the study during the time period you defined at "start editing within" (the access window). For them, the access window applies (i.e. they have at least as much time to participate as defined by the access window), but you may want to give users that accessed your survey close to the end of the access window some extra time to finish. If you set this to 0, users that accessed your survey but did not finish participation within the access window, will automatically be sent to the next position in your run. If you set "start editing" to X and "finish editing" to Y minutes, users that accessed your survey have at most X+Y minutes to fill out the survey.
- Inactivity Expiration: time for how long somebody has to have been inactive before survey expires (after starting).
This value does not matter as long as the access window (in case you set one) is still open. If you did not define a access window (or it closed) and a user is inactive for Z minutes, the run will automatically move on. Beware: much like with the snooze button on your alarm clock, a user can theoretically snooze indefinitely. If you set a finish-editing-within time and an inactivity expiration, users will be sent to the next position in your run as soon as one of the conditions is met.
-
Invitation should be open for 7 hours (7*60 = 420 minutes), people should be able to edit for at most 7.5 hours.
- Start editing within: 420 / finish editing within: 30 / inactivity expiration: 0
- Can result in people loading a page at 7:29, submitting a page at 7:31 and having data lost
- Results:
- User never reacts → run moves to next position 7 hours after survey was first available
- User accesses survey 2:30 hours after invitation → user has 5 hours to answer the survey (4:30 until the access window is closed + 30 mins extra finish editing time)
- User accesses survey 6:50 hours after invitation, then is inactive → run moves to next position 7:30 hours after survey was first available
- User accesses survey 6:50 hours after invitation, then waits 5 minutes, then fills out within 20 minutes → user finishes 7:15 hours after survey was first available
- User accesses survey 6:50 hours after invitation, then waits 20 minutes, then fills out 1 item every 10 min → user is interrupted 7:30 hours after survey was first available because run moves to next position
-
Invitation should be open for 7 hours (7*60 = 420 minutes). Once started, people should not be locked out unless they are inactive for more than 30 minutes.
- Start editing within: 420 / finish editing within: 0 / inactivity expiration: 30
- Can result in people stringing out a session for hours (but unlikely user behaviour)
- Results:
- User never reacts → run moves to next position 7 hours after survey was first available
- User accesses survey 6:50 hours after invitation, then is inactive → run moves to next position 7:20 hours after survey was first available.
- User accesses survey 6:50 hours after invitation, then waits 5 minutes, then fills out within 20 minutes → user finishes 7:15 hours after survey was first available
- User accesses survey at 6:50, then waits 20 minutes, then fills out 1 item every 10 min → user finishes unpredictably late
-
Invitation should be open for 7 hours (7*60 = 420 minutes), users should be able to edit for at most 10 hours, but only if they stay active.
- Start editing within: 420 / finish editing within: 180 / inactivity expiration: 30
- Results:
- User never reacts → run moves to next position 7 hours after survey was first available
- User accesses survey at 6:50 hours after invitation, then is inactive → run moves to next position 7:20 hours after survey was first available
- User accesses survey at 6:50, then waits 5 minutes, then fills out within 20 minutes → user finishes 7:15 hours after survey was first available
- User accesses survey at 6:50, then waits 20 minutes, then fills out 1 item every 10 min → user is interrupted 10:00 hours after survey was first available because run moves to next position
- User accesses survey at 6:50, then waits 40 minutes, then would fill out 1 item every 10 min → run moves to next position 7:20 hours after survey was first available
-
Invitation should be open for 7 hours (7*60 = 420 minutes), as soon as people react, they have unlimited time to fill out.
- Start editing within: 420 / finish editing within: 0 / inactivity expiration: 0
- Results:
- User never reacts → run moves to next position 7 hours after survey was first available
- User accesses survey 6:50 hours after invitation, then is inactive → user stays at this position of the run until the end of time (or the end of formr), i.e. s/he would miss subsequent invitations
- User accesses survey 6:50 hours after invitation, then waits 5 minutes, then fills out within 20 minutes → user finishes 7:15 hours after survey was first available
- User accesses survey at 6:50, then waits 20 minutes, then fills out 1 item every 10 min → user finishes unpredictably late
-
Invitation should be open forever. Once started, people should not be locked out unless they are inactive for more than 30 minutes.
- Start editing within: 0 / finish editing within: 0 / inactivity expiration: 30
- Results:
- User never reacts → user stays at this position of the run until the end of time , i.e. s/he would miss subsequent invitations
- User accesses survey 6:50 hours after invitation, then is inactive → run moves to next position 7:20 hours after survey was first available
- User accesses survey 6:50 hours after invitation, then waits 5 minutes, then fills out within 20 minutes → user finishes 7:15 hours after survey was first available
- User accesses survey at 6:50 hours after invitation, then waits 20 minutes, then fills out 1 item every 10 min → user finishes unpredictably late