So we have a contact who had one email (non-free domain) and he was associated to a company with that domain.
Then a different email converted on a form, with the same name. This email was added to the contact, but the company was not associated with them. This messed with our lead flow.
I would have expected a new conact to be created when a form submission with an email address not in our database was submitted, I assume that this didn’t happen because of some sort of tracking. But if this is going to happen, I would like them to be associated to the new account (prefferably as a primary, as this is presumabely why the email changed).
Can someone explain this behavior to me? Also possibly how I can stop it from happening like this?
In the settings for each form, there is a toggle “Always create contact for new email address”. Create forms (legacy) Once you enable this, HubSpot will not attempt to associate a form submissions with an existing contact when a new submission with a new email address comes in.
Hi Karsten,
Thanks for the response! Is it the case that checking the “Always create
contact for new email address” option disables the pre-populate fields
option? If this is the case then I would prefer to keep
pre-populated fields, but want to know if it is possible to add an account
association when new email addresses are submitted.
@WBrown2 yes, this will disable the pre-populated fields.
Out of the box, no, as far as I know there isn’t any setting which would create or associate a company record matching the new email domain. You could achieve this with the “Create record” workflow action and the “Create association” workflow action (based on the contact email domain and company domain name) – I can’t think of a way that would not result in at least a few duplicates, however, unless you’re willing to custom code a solution (with custom code actions in Operations Hub Professional or Enterprise).
My recommendation would be to enable the “Always create contact for new email address” option.