Skip to content
Book a Demo Open a Case

Salesforce apps by To A Finish

Four managed packages that run inside your own Salesforce org.

Simple Signature

Document creation and e-signatures in Salesforce

Address Verification

Clean, verify, and geocode Salesforce addresses

Highlighter

Colors, renames, or hides Salesforce fields

List Browse

Go from record to record without a trip back to the list

Get started

Install a TAF package, set it up, and give it to your users.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Book a demo

See a package in a live org

Compatibility

Editions and releases we support

Get help

Open a case. Our support team answers by email.

Open a support case

Our support team answers by email

Give us access

Let us sign in and see the problem

Support home

Guides, release notes, and the case form

Troubleshooting

Search by the error text you see

Documentation

We write these pages for Salesforce admins.

Implementation guides

Guides for all four apps are ready.

How-to articles

One article for each task

Change log

What changed in each release

Compatibility

Editions and seasonal releases

Simple Signature Address Verification Highlighter List Browse Support Book a Demo Staff
Address Verification · How-to

Verify records in the background

This article shows each step of the task in Address Verification.

Last updated 11 Oct 2026

Optional. For records that come in through imports, integrations, or other automation.

Address Verification can check a record each time someone makes it or changes its address. Accounts, Contacts, and Leads use the triggers that come with the app. Each check uses a lookup.

Test with a few records first

A data import with background checks on uses a lookup for each address of each record.

  1. On the setup page, click the Automation tab. Click Edit beside the object.

  2. Tick Verify Addresses.

    To check emails and phone numbers too, tick Verify Emails or Verify Phones. Keep Active ticked. The table below explains the other options.

    The edit window of an object on the Automation tab, with Active and Verify Addresses turned on.
  3. Click Save.

    The window may stay open with the message Go to Monitor Deployment to see the status of this record. The change still saves. Reload the setup page to check it.

  4. Test with one record.

    Change the street of a test record. Save. Wait a few seconds, then reload the page. The fields show the result of the check.

The options of an object

OptionWhat it does
LabelAny name for the object.
ActiveTurns on the trigger of the object. It unticks Verified when an address, email, or phone number changes. It does not verify anything by itself.
API NameThe API name of the object.
Active Job ID FieldThe API name of a Text field with a length of at least 18. Batch jobs need it. See Verify records with a batch job.
Layout Section NameThe name of the section of the record page that holds the address fields. When it is empty, Address Information is used.
Verify Addresses, Verify Emails, Verify PhonesTurn on the background checks for that kind of data.
Skip Completion CheckFor the autocomplete components only. Lets a user save a blank or incomplete address.
Large DatabaseFor an object with more than 200,000 records. It helps to stay under the Salesforce limits, but it slows a small object down.
Check for Existing AddressesPhysical addresses only. See Reuse earlier checks of the same address.

Show background checks on the record page

A background check finishes a few seconds after the save. The Background Verification Tracker then reloads the record page, so the user sees the result. It works for physical addresses only, and it misses some checks.

  1. Open a record of the object. Click the gear icon. Click Edit Page.

  2. Add BackgroundVerificationTracker at the bottom of a column.

    BackgroundVerificationTracker

    Search for it in the Components list. It sits under Custom - Managed. If the drag does not work, click the + at the bottom of the column. Then click the component.

    It shows as an empty box in the builder.

    The Lightning App Builder with BackgroundVerificationTracker at the bottom of a column.
  3. Click Save. Activate the page, if Salesforce asks.

    To activate it, follow step 4 of Add the Verify and Confirm button.

  4. Click the back arrow at the top left.

Reuse earlier checks of the same address

Check for Existing Addresses reuses the result of a verified record with the same address, which saves a lookup. Each check runs a little slower, so use it only with a small Smarty plan.

  • It looks only at records of the same object. A new Lead does not find a verified Account.
  • Above about 200,000 records in the object, it can fail. Open a case before you turn it on.
  1. Map a Clean Street field in each address entry.

    On the Data Mapping tab, click Edit beside the entry. Pick a field for Clean Street. If the object has none, make a Text(255) field first.

    Tick Clean Address Prior to Verification too, or Clean Street stays empty. Click Save.

  2. On the Automation tab, edit the object. Tick Active, Verify Addresses, and Check for Existing Addresses. Click Save.

  3. Optional: fill Clean Street on older records.

    Without this step, only records saved from now on can match. To fill older records, verify them again, which uses lookups. Or a developer runs this Apex sample in the Developer Console. It cleans 100 Leads.

    List<Lead> leadlist = [select Id, Street, CleanStreet__c
                           from Lead
                           where Street != null
                           and CleanStreet__c = null
                           and isConverted = false
                           limit 100];
    for(Lead l:leadlist) {
        l.CleanStreet__c = SmartyStreets.Clean.AddressCleanse(l.Street);
    }
    update leadlist;

    Replace CleanStreet__c with the API name of your Clean Street field.

Background checks on a custom object

A custom object needs its own Apex trigger. Copy TAF's sample, verifyTrigger.java, from the trigger folder of the Address Verification repository on GitHub. Replace each Object_Name__c with the API name of your object.

trigger verifyTrigger on Object_Name__c (before insert, before update, after insert, after update) {
    new smartystreets.AutoVerificationServices().HandleAutoVerify('Object_Name__c'); // for PHYSICAL ADDRESSES
    //new smartystreets.AutoVerificationServicesEmails().HandleAutoVerify('Object_Name__c'); // for EMAIL ADDRESSES
    //new smartystreets.AutoVerificationServicesPhone().HandleAutoVerify('Object_Name__c'); // for PHONE NUMBERS
}

To check email addresses or phone numbers too, remove the // at the start of the EMAIL ADDRESSES or PHONE NUMBERS line.

Only an admin who writes Apex should build the trigger. Build it in a sandbox. Deploy it to production with a test class, for example verifyTriggerTests.java from the same folder. Then tick Active and Verify Addresses for the object on the Automation tab.

With no code, a record-triggered Flow does the same job. See Verify records with a Flow.

Turn off all background checks

Do this to find a problem, or before a large data load. On the Options tab, tick Turn OFF All Triggers. Click Save Settings. The triggers on Account, Contact, and Lead stop. Flows still run.

To keep checks without the triggers, use Flows: Mark changed addresses on a custom object and Verify records with a Flow.

Keep a log of each check

On the Options tab, tick Log Responses. Click Save Settings. Each call to Smarty then saves in the √ Verification Log object. Without it, only errors save. The object can grow very large.

To see the logs, make a tab. Open Setup. In the Quick Find box, type Tabs. Click Tabs. Under Custom Object Tabs, click New. Pick √ Verification Log and any Tab Style. Click Next twice. Click Save.

Users also need access to the object and its fields. On the tab, pick the list view All to see every log.

Applies to

Address Verification 7.3.x. These steps come from the tested Address Verification implementation guide, where they sit with the steps before and after them.

Was this helpful?

Related

Support

Still stuck?

Open a case, and paste the exact error text into it. Our support team answers by email.