nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Limit a Public Survey to one response?

MattCobb

I have a client that is concerned about his constituents potentially skewing a survey by adding multiple survey responses from the same user. Is there a good way to limit a survey response to one submission, say per IP address (when using the web survey)?

Find more posts tagged with

Accepted answers

All comments

Anonymous User

Hi Matt,

It is not currently possible to limit public survey submission via IP address or other user identifiable attributes.

Phil.

SunnyWisher

Why not? Is there any possible workaround so that it can be used to get usable results? This should be an enhancement request. At the very least use cookies, although there are ways to get around that at least it's something.

JamesTedrick

Hi Sunny,

As you point out, a cookie can be easily worked around by the use of multiple browsers or clearing cookie settings. IP restrictions cannot work because it is very common for an internal network (say from one company) to be aggregated into a single public IP; this would restrict users from submitting if another person in their organization submitted previously. We are researching this topic to consider other methodologies of creating unique survey entries.

SunnyWisher

Thank you for your reply and apologies for not replying back to you sooner. I did see your reply in email when you posted it.

I think that a cookie option would at least be a relatively simple start. IMHO, it's creates at least an obstacle that people would have to go around in order to skew results, and doing something is better than doing nothing at all. Survey Monkey and others implement the cookie strategy to prevent this problem, so why not do the same? I would assume most respondents would not care to take the time to respond multiple times, and for those who might want to their level of technological intellect may not enable them to expose the workaround.

So, why not do something (use cookies) instead of doing nothing? Just curious...

JamesTedrick

Hi Sunny,

We are considering implanting this method of submission prevention. Part of our concern before implementing is ensuring that the solution, while not perfect, would be acceptable to users and that when it's released, we can appropriately describe the scenarios in which it will and won't work.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.