The Email Domain Exclusion List is designed for personal email domains (ie @gmail.com, @yahoo.com, etc) as well as other email domains that you do not want Leads matching against.

By default, when you install Align.ly Lead-to-Account, the Email Domain Exclusion List is pre-populated with an extensive list of personal email domains.

However, you may want to add/remove email domains from the list. To do so, go to Setup -> Develop -> Custom Settings -> then click "Manage" next to the Email Domain Exclusion List.

Lock Lead is a checkbox field on the Lead object.

If set to TRUE, Lock Lead does the following:

• Prevents Matched Account from being updated automatically by Align.ly
• Prevents the Lead from being converted automatically by Align.ly

It is common for this field to automatically be updated using workflows or process builder based on business requirements.

Lock Contact is a checkbox field on the Contact object.

If set to TRUE, Lock Contact does the following:

• Prevents the email domain of that Contact from being summarized into the Email Domain(s) field on Account

It is common for this field to be used to prevent an email domain from being summarized into the Email Domain(s) field on Account.

Lock Account is a checkbox field on the Account object.

If set to TRUE, Lock Account does the following:

• "Locks" or "Freezes" the current values in the Email Domain(s) field on Account. Values can be manually updated, but Align.ly will no longer update the values automatically.

It is common for this field to be used to a.) clear values in the Email Domain(s) field, so Leads never match that specific Account, or b.) set the exact values in the Email Domain(s) field and ensure they never get overwritten.

Geography Match is a picklist field on Account.

Use Case

Geography Match is typically used when you have multiple Accounts using the same email domain, but the Accounts are in different geographic regions.

Example

Let's say you have an Account for "General Electric - US" and an Account for "General Electric - UK" and both use @ge.com as the domain name. On both Accounts, you'll want to set Geography Match to "Exact Match on Country".

Geography Match Options

The following options are available for Geography Match:

• Exact Match on Country
• Exact Match on Country and State
• Exact Match on Country, State, and City
• Exact Match on Postal Code

Which Lead and Account fields are used for Geography Match?

By default, Align.ly uses the standard Country, State, City, and Postal Code fields on Lead and the standard Billing Country, Billing State, Billing City, and Billing Postal Code fields on Account.

However, you can use any fields on Lead or Account. This is configurable in Setup -> Develop -> Custom Settings -> then click "Manage" next to Align.ly Lead-to-Account Settings

You can update the following fields with the API name of the Lead/Account field you want to use:

• Lead Field for Country Match
• Lead Field for State Match
• Lead Field for City Match
• Lead Field for Postal Code Match
• Account Field for Country Match
• Account Field for State Match
• Account Field for City Match
• Account Field for Postal Code Match

Real-Time Lead-to-Account Matching is a configurable feature that enables the ability to match a net new Lead to an Account before the Lead is saved to the Salesforce database. When turned on and a Lead is successfully matched to an Account, the Matched Account field on Lead will be updated. The Matched Account field is an Account Lookup field.

When does it execute?

Real-Time Lead-to-Account Matching executes in a Before Insert trigger. This means that Matched Account will be updated before the Lead is saved to the database. It also means that if you have Set Lead Owner to Account Owner turned on then the Lead Owner will also be updated before the Lead is saved to the database.

It is important to note that this may impact your Lead Assignment Rules in Salesforce (see Related Articles).

Configuration

Go to Setup -> Develop -> Custom Settings then click "Manage" next to Align.ly Lead-to-Account

Set Lead Owner to Account Owner enables the ability to update the Lead Owner on Lead to the Account Owner of the Matched Account.

This setting applies to real-time, on-demand, and scheduled lead-to-account matching.

This feature is typically used to route Leads to the proper owner based on the user that owns the Account relationship.

Note that by default, Align.ly Lead-to-Account will use the standard Account Owner (OwnerId) field, but this is configurable using the Account Owner API Name in Setup -> Develop -> Custom Settings -> then click "Manage" next to Align.ly Lead-to-Account Settings.

Set Contact Owner to Account Owner enables the ability to update the Contact Owner on Contact to match the Account Owner when Align.ly is auto-converting a Lead to a Contact.

This setting applies to on-demand and scheduled auto-conversion.

This feature is typically used to route Contacts to the proper owner based on the user that owns the Account relationship.

Note that by default, Align.ly Lead-to-Account will use the standard Account Owner (OwnerId) field, but this is configurable using the Account Owner API Name in Setup -> Develop -> Custom Settings -> then click "Manage" next to Align.ly Lead-to-Account Settings.

In Align.ly Lead-to-Account Custom Settings you will see the following settings:

• WHERE Clause for Matched Lead Realign
• WHERE Clause for Unmatched Lead Realign
• WHERE Clause for Contact Realign

These settings are used with Align.ly Lead-to-Account's "Realign" feature. To limit the Leads and Contacts that are eligible to have their ownership update, write a WHERE Clause using SOQL.

Examples

• LastActivityDate < LAST_N_DAYS:30
• Only Leads/Contacts with an Activity logged more than 30 days ago will be eligible to be updated.
• CreatedDate < LAST_N_DAYS:90
• Only Leads/Contacts Created more than 90 days ago will be eligible to be updated
• CreatedDate < LAST_N_DAYS:30 AND Actively_being_Sequenced__c = False
• Only Lead/Contacts Created more than 90 days ago and are not actively being sequenced (in Outreach/SalesLoft) will be eligible to be updated

Configuration

Go to Setup -> Develop -> Custom Settings then click "Manage" next to Align.ly Lead-to-Account

Account Owner API Name is used with the following features:

• Set Lead Owner to Account Owner
• Set Contact Owner to Account Owner

By default, Account Owner API Name is the standard Account Owner (OwnerId) field. However, you have the ability to update this custom setting to the API name of any User lookup field on Account.

For example, let's say you don't want to use the standard Account Owner field, but instead want to add a User lookup field to Account called "Inside Sales Owner". When you create the "Inside Sales Owner" field on Account, the API name will be something similar to "Inside_Sales_Owner__c". This is the value you will want to use for Account Owner API Name in Setup -> Develop -> Custom Settings -> then click "Manage" next to Align.ly Lead-to-Account Settings.

Converted Status is required to configure if you choose to use Align.ly to auto-convert Leads to Contacts/Accounts.

When converting a Lead to a Contact/Account, Salesforce requires that you set a Converted Status value. Since Align.ly is converting Leads automatically "behind-the-scenes", we need to configure the value to be set when auto-converted.

By default, Align.ly sets the Converted Status value to "Auto-Converted", but there is configuration necessary within Salesforce.

To configure...

• Go to Setup -> Customize -> Leads -> Fields -> then click on "Lead Status"
• Under Lead Status Pick Values click "New"
• For Label use "Auto-Converted" and for API Name also use "Auto-Converted"
• Set "Converted" to TRUE
• Click "Save"

It should now look something similar to the following:

You can use a custom value for Converted Status. If you choose to use a custom value, you'll need to update the Converted Status field in Setup -> Develop -> Custom Settings -> then click "Manage" next to Align.ly Lead-to-Account Settings.

Important Note

If you are using a Lead Process, you will need to make sure your new converted value for Lead Status is selected for your Lead Process.

Configuring batch scope sizes is an advanced feature that is typically used to help troubleshoot issues. If you are unfamiliar with Salesforce batch jobs, they are used to process large numbers of records in Salesforce. To process records more efficiently, Salesforce breaks up a batch job into smaller, more manageable chunks of records. The batch job scope size refers to the number of Salesforce records processed in a single "chunk" within the overall batch job.

There are 6 configurable options in Custom Settings:

• Batch Scope Size Update Email Domains
• Batch Scope Size Match Leads to Accounts
• Batch Scope Size Convert Matched Leads
• Batch Scope Size Matched Lead Realign
• Batch Scope Size Unmatched Lead Realign
• Batch Scope Size Contact Realign

The default value for all 6 configurable settings is "200", which means 200 records will be processed in each batch "chunk".

In some cases, it might be necessary to reduce the batch scope size for a specific batch job. For example, if a Lead is failing to convert, you might reduce the batch scope size for Batch Scope Size Convert Matched Leads down to "1" to help identify the specific Leads that are failing to convert.

Configuration

Go to Setup -> Develop -> Custom Settings then click "Manage" next to Align.ly Lead-to-Account