Limit how often someone can respond
Choose how often the same person can respond to your survey.
- You need admin access to do this. About roles
The Response frequency setting controls how often the same person can respond. It is available on link streams and website widget streams. ExpressPod and ExpressTab streams do not have it.
Where to find it
Open your link stream or website widget stream and go to the Settings tab. The setting is in the Distribution card.
Set the frequency
- Under Response frequency, choose one of three options:
Option What it does Unlimited No limit. The same person can respond as many times as they like. Only one time The same person can respond once. Every The same person can respond again after the time you set. - If you chose Every, set the time with the four lists: weeks (0 to 52), days (0 to 6), hours (0 to 23) and minutes (0 to 59). The total must be more than zero.
- Choose your unique identifiers (see below).
A new stream starts on Unlimited.
Choose your identifiers
When you choose Only one time or Every, the Unique identifiers section appears. The identifiers are used to check whether a response has already been submitted.
Under Identifiers, pick one or more:
- Browser history
- Phone
- Custom ID
Browser history is picked by default. It is a random ID that the survey stores in the browser's local storage. Another browser or device gets a new ID, so it is not recognized. If you only want to discourage repeat responses, that is usually fine.
Email, Phone and Custom ID match the email, phone and cid survey parameters. See Customize your survey link. On a link stream, the values come from the survey link. On a website widget stream, they come from the widget script on your website. The respondent does not type them in.
Custom ID is useful when you already have an ID for your respondents, for example a membership number.
At least one identifier must stay picked. If you remove the last one, it stays.
Set the identifier order
When you pick more than one identifier, the Identifier order section appears. Drag the identifiers to set which one is checked first. The identifier at the top has the highest priority.
Put your most reliable identifier at the top. Keep Browser history last in the list.
How the limit works
When Yump recognizes an earlier response to the same stream from your identifiers, it blocks the new response. If a response has none of your identifiers, it is not limited.
With Every, the time counts from the earlier response. For example, with every 1 week, someone who responds on Monday at 10:00 can respond again from the next Monday at 10:00.