-
Re: Form Error Handling for Who Already Registered.
1 of 1 people found this helpfulFirst, let's not use the term "form error" for this. Form errors are either at the network level or during validation of form values, while what you describe is a valid condition, just a form reality more than an error.
Anyway, I gave the answer in this recent thread on the same topic:
-
Re: Form Error Handling for Who Already Registered.
Hi Sanford,
The link you gave me helps a lot.
Thank you!
-
Re: Form Error Handling for Who Already Registered.
Hello Sanford,
Sorry to bother you, I have a follow-up question,
The solution you gave helpful thank you for that.
The question is what if the lead clear his/her cache? The solution is for cookied lead who registered on the form.
Do we have an alternative solution or back up like IP detection?
Thank you!
-
Re: Form Error Handling for Who Already Registered.
The question is what if the lead clear his/her cache? The solution is for cookied lead who registered on the form.
No, it's not only for cookied leads. That wouldn't make sense, because it would mean any new device/browser/session wouldn't be covered. The solution I described works for a brand-new browser session where they've never been seen before.
Do we have an alternative solution or back up like IP detection?
IP addresses have no relevance for detecting individual users. Tens of thousands of people can share the same IP address.
-
-
Re: Form Error Handling for Who Already Registered.
I'm saying the solution I described in the other thread (and pictured in the animated GIF) does work for all sessions whether or not the person was previously known in the session.
-
-
-
-
-
