Before we discuss your options, there are a couple important items you should know about how Align.ly summarizes "Email Domain(s)" on Account.

1. Each time Align.ly runs, it scans all the Contacts on each account and summarizes unique email domains into the "Email Domain(s)" field.
2. Each time Align.ly runs, it will overwrite the "Email Domain(s)" field unless "Lock Account" is set to TRUE.
3. Email domains in the Email Domain Exclusion List will not be summarized in the "Email Domain(s)" field on Account.
4. Contacts with "Lock Contact" set to TRUE will not have their email domain summarized into the "Email Domain(s)" field on Account.

With that context, there are four options to prevent the wrong email domain from being summarized on Account:

1. Re-parent the Contact into a new Account. As long as "Lock Account" is set to FALSE, the next time Align.ly runs the "Email Domain(s)" field will be updated.
2. Set "Lock Contact" to TRUE on the Contact with the email domain that you do not want summarized on Account. As long as "Lock Account" is set to FALSE, the next time Align.ly runs the "Email Domain(s)" field will be updated.
3. Manually update the "Email Domain(s)" field with the proper email domains and then set "Lock Account" to TRUE. This will lock the value of the "Email Domain(s)" field. The next time Align.ly runs, the "Email Domain(s)" value will not be overwritten.
4. Add the email domain to the Email Domain Exclusion List.

There are several reasons why a Lead won't match an Account. Here is a list of the most common reasons:

1.) No Contacts on the Account

If there are no Contacts on the Account, Align.ly will not be able to automatically update the Email Domain(s) field on the Account. With no email domains in the Email Domain(s) field, Align.ly is unable to match a Lead to the Account.

2.) All Contacts on the Account have email domains that are in the Email Domain Exclusion List

If you have Contacts on the Account, but their email domains (ie @walmart.com) are in the Email Domain Exclusion List then Align.ly will ignore the email domains and not update the Email Domain(s) field on Account. With no email domains in the Email Domain(s) field, Align.ly is unable to match a Lead to the Account.

3.) Account is locked and "Email Domain(s)" field is blank

On Account there is a checkbox field called Lock Account. If Lock Account is checked, the Email Domain(s) field gets locked with the current values in the field. If the field is blank, Leads will not match to the Account even if the Account has Contacts with valid email domains. Uncheck Lock Account and click the "Update Align.ly Data" button to resolve.

4.) Account has Geography Match option selected and all leads do not qualify to match

On Account there is a picklist field called Geography Match. If one of the options is selected, Align.ly requires the geography fields (configured in Align.ly Lead-to-Account Settings) to match before a Lead will match to an Account.

5.) All leads are locked

On Lead there is a field called Lock Lead. If Lock Lead is checked, the Lead is not eligible to match an Account.

There are a few reasons that we've seen that cause a Lead with a Matched Account to fail to convert.

1.) Account Owner is an Inactive User

If the Account Owner of the Matched Account is an inactive Salesforce user, then the conversion will fail. Make sure all your Accounts are owned by active Salesforce users.

2.) A Valid Lead is Part of a Batch Job with a Failing Lead

By default, Align.ly will convert Leads in batches of 200 Leads at a time. If one of the 200 Leads fails to convert, all 200 Leads in the batch will also fail to convert. To troubleshoot, go to Setup -> Develop -> Custom Settings then click "Manage" next to Align.ly Lead-to-Account. Temporarily change the "Batch Size Convert Matched Leads" setting to 1 and then run the job to convert matched leads again. You should be left with only the failing Leads while all valid Leads should have successfully converted.

In order to edit Custom Settings, a user needs the "Customize Application" permission.

Refer to the following Salesforce Help Doc for more information:https://help.salesforce.com/articleView?id=cs_manage_data.htm&type=5