Home > DemandTools for AppExchange Modules > DemandTools - Verification Module > Address Verification - Verify US and Canadian Address data
Address Verification - Verify US and Canadian Address data
Capabilities & Features:
The Address Verification tool provides 4 key areas of validation and enrichment that not only solve the issues of nonmailable addresses but also ensure that address data is as rich as possible and provides some geographical enrichment for use in ownership assignment or object mapping.
|
| |
|
| |
| Address Enrichment |
|
| Object Enrichment |
|
|
Benefits of Address Verification: | |
|
The valid addresses from the Address Verification tool are in CASS or SERP standards so you will benefit from the least expensive bulk mailing rates. You will be able to mark the addresses that are invalid and even provide an open task for the object owner in order to fix the invalid addresses. With enrichment data like County and Congressional district you can use this information for account reassignment. Many organizations separate Account ownership in populous areas by county. With the advent of Google Maps and other mapping tools you can view your Leads, Contacts an Accounts in relation to each other in order to find specific trends or find Leads close to existing Accounts. The image on the left shows Salesforce data displayed in Google Maps.
|
![]() |
![]() |
| The above image shows the first step of the Address Verification process |
| Step 1. Select Object to Verify | |
| Your first step is to select what type of object you want to verify addresses for. Your choice is Account, Contact or Leads. You can only check one object at a time and one type of address (i.e. Billing or Shipping) at a time. | ![]() |
| Step 2. What Object to Check |
|
|
You must now determine if you are going to verify the addresses of all of your selected objects (i.e. Accounts in the example) or just a subset. We recommend that you do not attempt to validate more than 10,000 records at a time. The tool has been tested in validating 10x this number but it could reach the limits of your available memory or be too much information to review in a single session. The best way to limit the number of attempted verifications is by the first letter of the object name. If you are verifying Accounts and have 50,000 Accounts in your database you could search just the Accounts where the name "Starts With" "a,b,c,d,e". This way you will only look at a subset of your Accounts. If you select "Use Conditions" the "Add Conditions" section will become active and you can add in the condition. |
![]() |
| Step 3. Address Mapping |
|
|
This is the most vital part in the verification process as you will determine what fields you are checking and what fields you would like enriched. The top section of the mapping for all fields is mandatory (except for Company). The default (for Accounts) is to verify the billing address. If you want to verify the shipping address simply select the Account fields and change them to the shipping address fields. The lower section is optional and allows you to map your standard and custom Salesforce fields to available enrichment data. If you would like to geocode you address information or add in County names you would map your custom fields to the enrichment fields in this area. The Verification Date field will put the current date into a custom date field in Salesforce. We recommend that you first create a custom date field in Salesforce for verification date and then map this field to it so that future address verifications can be done only on those objects where the custom verification date field is not populated. |
![]() |
| Step 4. Default Country Names |
|
| Enter the default name that you would like for the country that you are doing address verification for. The default value for the United States is US by many organizations prefer USA, U.S.A. or United States. When addresses are verified the tool will ensure that this is the standard country name. | ![]() |
| Step 5. Set Address Type and Format |
|
|
Select the country that your are validating addresses for and also the case for the address you are verifying. In most cases CRM data is stored in "Proper Case" (i.e. 123 Main St). You also have the option to use Upper and Lower case. We recommend using Proper case as you can always export the data to XLS and convert to Upper or Lower case. When the comparison of addresses is performed the tool will by default consider the case of your address. For example, if you address is 123 MAIN ST and the recommended address is 123 Main St the tool will recommend changing this address. If you select the "Ignore Case on comparison" checkbox these two values will be considered equal and no changes will be recommended. |
![]() |
| Step 6. Task Creation | |
|
You have the option to create 3 separate types of tasks based on how addresses are verified or enriched.
|
![]() |
| Step 7. Confirm Verification | |
|
When you select the "Process" button the tool will download the required objects based on your conditions of the objects to download. Once the information has been accessed and initially analyzed by the address verification module you will see a confirmation screen as shown on the right. At this point you have several options before you proceed with the full verification.
When you are ready to perform the verification select the "Verify Addresses button. |
![]() |
| Step 8. Accepting Address Enrichments | |
| Once the initial verification is completed the required tasks will be added to Salesforce for the fixed, confirmed and invalid addresses (if requested). After this process you will have the opportunity to accept the address enrichments recommended by the application. By checking the checkbox by the address components you will update that component to it's recommended value. A sample of the final screen is shown below. | |
![]() | |
|
Once you have agreed with the proposed changes you simply select the "Update Records" button and the information on the address values will be updated. After this is completed you will be presented with the status of the update, the location of the error log and the location of the enrichment file. The enrichment file contains all the information on what addresses where valid or not plus all of the recommended enrichments for the addresses. If you missed updating the geographical position of the address or the county name you could use MassEffect and this file to update the address information after the fact. | |
See also