When someone fills out one of your forms, they're always required to provide their name and email address. We’ve moved those fields to the top of the form to improve the experience and reduce confusion.
Forms don’t require people to log in, but still try to match people with existing profiles to prevent duplicates. To do that, they collected names and emails in a confusing, two-step process. Names and emails were collected as the last step to submitting the form, which seemed backwards. In addition, there were some user privacy concerns.
Over time, and with your feedback, we've decided that better privacy and a more obviously laid out form are more important than doing everything possible to prevent duplicates.
With those concerns in mind, we've redesigned the flow of forms. Now, at the top of every form there are required fields for first name, last name, and email address. Users will never have to confirm their name, or select from a list of matching profiles.
If the first name, last name, and email address exactly match an existing profile in your account, the form submission will be matched to that profile. (Changes to the profile will still need to be verified by email.) If there aren't any exact matches, a new profile will be created.
With this change, forms might create more duplicate profiles. If John Smith fills out your form, but he's in your database as "Johnathan Smith", a new profile will be created for him. However, our duplicate detector will find this duplicate for you to merge. And if Johnathan actually goes by John (since that's how he filled out his form), we recommend storing his profile in your database with the first name of "John" and given name of "Johnathan."
All in all, we think that the more obvious form layouts, combined with improved privacy, outweighs any increase in duplicate profiles that may be created.