Some CRMs do not support individual customers or personal accounts (for Business to Consumer). As a result, CRM users often create a CRM account (organization) and a matching CRM contact. For example, with the contact email@example.com, the corresponding CRM account could end up being
If this sort of account creation is used for multiple users, there might be multiple accounts (organizations) that SmartConvert could match for an email domain.
For SmartConvert recipient matching to CRM contacts, if there is no matching CRM contact or lead, Riva starts the process to create a new CRM contact, which includes locating a CRM account with a matching email domain name (in the website field or primary email address field). Riva then creates the new contact and links it to the first account (organization) that it matches by email domain. If there are more than one, Riva may link the new contact to the wrong account.
Enforcing Unique Account Matches by Email Domain
Riva 2.4.34 or higher includes an advanced option to prevent linking a new contact to the wrong account.
To enforce unique account (organization) match for new CRM contacts that are created by SmartConvert:
Sync.Crm.OrgMatchesMustBeUniqueForEmailDomain = True (Enforces a unique account match for new CRM contacts that are created by SmartConvert.)
How SmartConvert creates contacts when the Enforce Unique Account option Is enabled
When Riva cannot find a matching CRM contact or lead for an email or appointment recipient, it looks for any CRM accounts (organizations) that can be matched by email domain (for example, example.com).