Duplicates, verification and standardization
The Clean section of the Tomba Data Quality tab finds duplicate Leads, Contacts and Accounts for you to merge, opens ready-made verification runs, and standardizes names, websites, countries and states. Finding duplicates and standardizing use no Tomba credits; verifying does.
Before you start
- You need the Tomba Admin permission set, and Tomba must be connected to a Tomba Enterprise account.
- Merging needs edit access to the record you keep and delete access to the others. Tomba checks this before it merges and tells you when you don't have it.
- Everything runs as you: Tomba finds, merges and changes only the records you can see and edit.
Find duplicates
Open Tomba Data Quality › Clean › Duplicates and click Find duplicates. Tomba compares each object with these rules:
| Rule | Records | Match | Confidence |
|---|---|---|---|
| Same email | Leads, Contacts | The same email; placeholders (noemail@, @example.com) and role addresses are skipped | 100 |
| Lead already a Contact | Leads | A Lead, not converted, whose email belongs to a Contact | 100 |
| Same person at the Account | Contacts | The same Account and last name, and first names that match: the same, a nickname (Bill and William), an initial, or one typo | 80 to 95 |
| Same company domain | Accounts | The same domain from the website, except webmail; 100 when the names match too | 90 or 100 |
| Same company name | Accounts | The same name, ignoring case and spacing | 80 |
A search reads records only and changes none. Converted Leads and person accounts are left out, and a value shared by more than 100 records, such as a shared mailbox, is skipped.
To search on a schedule, choose Every day or Every week under Find duplicates automatically and click Save. Tomba's hourly job then searches Leads, Contacts and Accounts one after the other, as the user who scheduled it.
Review and merge
Groups to review are listed per object, most certain first. You can filter them by rule, status and confidence.
- Review and merge opens the records side by side. Pick the record to keep, then for each field that differs the value to keep. Tomba suggests both: by default it keeps the oldest record, and for each field that record's value, or the most recently changed value when it has none. An address or a name moves as a whole, and the Tomba email status and verified date follow the email you keep.
- Merge merges up to 10 records. The other records are deleted, and their related records, such as activities and opportunities, move to the record kept. Taking another record's email doesn't queue a new verification.
- Not duplicates closes the group. Tomba shows it again only if another record joins it.
- Select several groups of the same object and click Merge … groups to merge them with the suggested values. This runs as a job you can follow in Tomba Jobs.
To keep a different record by default, change Record kept in a merge to The most recently changed or The most complete.
A Lead whose email belongs to a Contact can't be merged into it. Review and convert converts the Lead into that Contact and its Account instead, without creating an Opportunity. The Contact needs an Account.
Duplicates on a record page
The Tomba Insights component on Lead, Contact and Account pages shows a Data quality section:
- the record's issues, such as a name in all caps, with a Fix that saves the corrected value;
- possible duplicates among the records you can see, with Not a duplicate when a search grouped them, and Review and merge for Tomba admins;
- for a Lead, the Contacts that already have its email, with Convert into this Contact.
Verify CRM data
Verify lists ready-made runs with the number of records each would take. Each one opens Tomba Bulk with its object, run and filter, where you see the credits before you start.
| Records | Run |
|---|---|
| Emails never verified | Verify email |
| Emails verified more than N days ago | Verify email |
| Invalid or disposable emails | Re-verify bounced email |
| Phones never validated | Validate phone |
| Accounts with a website but no domain | Index Account domains |
N is the Re-verify emails older than N days setting in Automation, or 180 days.
Standardize fields
Standardize fixes, in bulk:
- names in all caps or all lower case (Leads and Contacts);
- extra spaces;
- websites with capitals or a trailing slash, and, if you choose, websites without
https://; - countries and states that aren't in a standard form.
For countries and states, choose Keep any standard form, which only fixes spellings such as Deutschland or usa,
Names, or Codes. When State and Country/Territory Picklists are on, Salesforce already keeps them standard and
Tomba skips them.
- Choose the object, what to fix and, optionally, a filter for the records.
- Click Preview to see how many records match and the changes Tomba would make to the first 200.
- Click Standardize. The job saves only the fields that change, in your name, and attaches a CSV change log (record, field, old value, new value) to the job in Tomba Jobs. Use it to review the changes or to restore values with a data loader.
Credits and limits
- Finding duplicates, merging and standardizing use no Tomba credits. Runs started from Verify use credits like any bulk run.
- The merge job takes up to 500 groups at a time.
- After a search, the data health score counts the records in open duplicate groups in its uniqueness part, and a monitor on Records in duplicate groups (%) can alert you when the share grows.
- The Tomba Open Duplicate Groups by Object report and its chart on the Tomba Data Health dashboard count the groups waiting for review.