Allow only one submission by respondent

Hello, Great feature. I had one feedback. The feature "Prevent duplicate submissions" is not compatible with partial submissions, it's problematic. Ideally the check should be done as soon as the survey begins or when the ID that prevents duplicate submissions is known. Or at least, partial submissions should be flagged as partial when submissions are exported.

Prevent duplicate submissions is here! ✨ You can now accept only one submission per respondent. Go to your form's settings and turn on the "Prevent duplicate submissions" toggle, then select a unique identifier field (e.g., email address, phone number, IP address) to detect and block duplicate submissions. https://tally.so/changelog

This feature is now planned on our roadmap: https://tally.so/roadmap

I have implemented this feature in my website. It was real pain task. If I was able to integrate JavaScript in the form, it might be super easy but tally do not support it. I am waiting for stable solution.

This is the #1 requested feature and the team is absolutely silent...worrying to say the least.

I would really like this to be included!

Supertokens can probably help with this. Authentication + add a counter per form, so it just limits each of them to the amount set.

I was going to come here just to write this, very useful against troll responses 😭😭

This can probably help too with inspiration: https://makeforms.io/features/otp-verification/

Give us a Christmas gift) We will be very happy, but for now it’s pain((((((( I sent you an example where 1 client completes a survey 6-8 times

YES

An entreprise or partnership integration with: https://www.otpless.com Or similar might help with this tbh

we regularly have untrue data when 1 customer sends a reply more than 1 time, this is a problem that needs to be solved

I think this can only be done by adding some sorta authentication before the user accesses the form so the system knows the count or uses allowed for that user. OR you can make the form "only" accessible via hidden fields so the users does not remove the parameters in the URL.

I made this suggestion to the development team many months ago, and to this day it has never been put into operation, it is frustrating not being able to use such a cool platform due to this single problem.

Just did a survey and got so many responses.. only to find out that they were bots or someone kept filling out the survey and pasting the same answers on every question. It would be REALLY nice if we could add some type of control to filter out people so they can only respond 1x or a Capta thing to filter out bots.

My suggestion is to do this with the "hidden fields" feature. Tally need to make a check if a value in hidden-fields match with a previous value then the new respondent won't be able to take the form again.

This is absolutely vital to use Tally as a survey tool!

Yes! This would be so much more useful than manually pruning the CSV for matching cookies.

Agree this is crucial to avoid skewed results if people can send multiple responses

This is a must-have feature to avoid messy data

Yes pleaseeeeeeeee

This is a critical features to be honest!

How is this basic feature taking so long!

it would be extremely interesting and useful. To do absolutely

I came here to suggest this and alas! It was here. When are we having this feature!

Yes please!!!!!

Jotform allows you to select the property / field that should have unique values. For instance it could be some sort of identifier you're passing through as a URL parameter. This kind of flexibility would be great.

I need!!!

This one is VERY important ! With email and/or IP

YES!