TombaTomba
Start free
  • Documentation
  • API reference
  • SDKs & CLI
  • AI & MCP
  • Integrations
  • Enterprise
  • Migration guides

Find, verify and enrich B2B contacts from public sources, in the app, your spreadsheet or through the API.

GDPR & CCPA

// docs

  • API changelog
  • Support options
  • Security

// platform

  • Dashboard
  • Pricing
  • API status

// resources

  • Help center
  • Product updates
  • TombaBot crawler

// company

  • Website
  • Contact us
  • Edit or remove your data

© 2021–2026 Tomba.io

  • Terms of service
  • Privacy policy
  • Cookie policy
  • Security policy
  • GDPR
  • CCPA
Overview
Salesforce (coming soon)
    Getting Started
    Guides
      Record actionsList views and bulk runsAutomationFlow actionsAgentforceTomba SearchAccount matchingBuying committeeReports, dashboard and record panelUsage, limits and alertsThe Tomba API tabSingle sign-onSandboxesField mappingData healthClean dataPrevent bad dataKeep Your Salesforce Contact Data DeliverableSecurity and Data ProtectionFAQ and troubleshooting
Snowflake (coming soon)
Guides

Data health, monitors and field documentation

The Tomba Data Quality tab scores the health of your Leads, Contacts and Accounts, alerts Tomba admins when it slips, and documents the fields of any object. Checks read records without changing them and use no Tomba credits.

Before you start

  • You need the Tomba Admin permission set. Tomba Users don't see the tab, but they see the health chart on the Tomba Data Health dashboard.
  • Tomba must be connected to a Tomba Enterprise account in Tomba Setup.

Check data health

Open Tomba Data Quality › Health and click Check now. The check runs in the background, and the page updates by itself when it's done, usually within a minute or two.

For each object, the page shows:

  • the health score out of 100, the change since the previous check and the trend over the last 30 checks;
  • the parts of the score;
  • what to fix, with the number of records and a Fix link for each issue;
  • the result of the last format check.

A check counts the records you can see. Converted Leads and person accounts are left out.

How the score is calculated

The score is a weighted average of these parts, each from 0 to 100:

PartWeightLeads and ContactsAccounts
Completeness30Average share of records with each key field filledThe same
Deliverability30Share of emails Tomba found valid or accept-all; unknown and never verified count half, invalid and disposable count zeroShare of websites with a valid domain
Freshness15Share of emails verified within the re-verify periodNot measured
Uniqueness15Share of records not in an open duplicate group, once a duplicate search ranThe same
Consistency10Share of records with no issue in the last format checkThe same

A part with no data is left out, and the weights of the other parts are scaled up. For example, Accounts have no freshness part, consistency appears only after a format check, and uniqueness only after a duplicate search. The re-verify period is the Re-verify emails older than N days setting in Automation, or 180 days when it isn't set.

Key fields

Completeness uses each object's key fields:

ObjectDefault key fields
LeadEmail, Phone, Company, Title, Country
ContactEmail, Business Phone, Account ID, Title, Mailing Country
AccountWebsite, Account Phone, Industry, Billing Country, Employees

To change them, open Monitors, choose up to 20 fields per object under Key fields and click Save. The lists offer the fields people or integrations fill in, not formulas or system fields such as Created By.

Format check

Click Check formats under an object to read every record and count the values that need fixing. The check runs as a job you can follow in Tomba Jobs, and it changes no records. It counts:

  • emails with an invalid format, role addresses (info@, sales@) and free mailboxes;
  • phones and websites with an invalid format, and websites with capitals or a trailing slash (a website without https://, such as www.acme.com, is fine);
  • unknown countries, and countries and states written other than their name or code: United States, US, USA, Ohio and OH are fine, Deutschland, usa and ohio are counted;
  • names in all caps or all lower case, and extra spaces.

When State and Country/Territory Picklists are on, Salesforce already enforces countries and states, and the check skips them.

Fix what the check found

Each Fix link opens Tomba Bulk with the object, the run and a filter for the records concerned. Bulk counts the records and shows the credits the run can use before you start it.

IssueRunNotes
Invalid or disposable emailsRe-verify bounced emailSuggests a replacement, never overwrites it
Emails never verifiedVerify email
Emails verified more than N days agoVerify emailIncludes records Tomba already verified
A key field is emptyFind email, Find phone, Enrich or Enrich company, by fieldFields Tomba can't fill have no Fix link
Websites without an indexed domainIndex Account domainsFree; see below

Accounts saved before Tomba was installed have no indexed domain until you run Index Account domains once, and until then deliverability counts their websites as invalid. Websites still without a domain after that are not valid websites.

Check every day and get alerts

Open Monitors, turn on Check data health every day and click Save. Tomba's hourly job then starts a check once a day. The scores are kept for 400 days.

The first time you turn it on, Tomba adds suggested monitors:

  • health score below 70, for each object;
  • invalid or disposable emails above 5 %, for Leads and Contacts.

Monitors

A monitor compares one value of one object with a threshold after each check, daily or Check now. Click New monitor and choose:

SettingChoices
ObjectLead, Contact or Account
MetricHealth score, Invalid or disposable emails (%), Emails never verified (%), Verifications out of date (%), Records with format issues (%), Records in duplicate groups (%), Field filled (%)
Alert when the value isAbove or Below a threshold from 0 to 100
Also send an emailSends an email with the bell notification

When a monitor crosses its threshold, it turns Alerting, and every user with the Tomba Admin permission set gets one bell notification listing the monitors that started alerting, plus an email when one of them has Also send an email on. The notification opens Monitors. A monitor alerts once: it returns to OK when the value is back within the threshold, and alerts again the next time it crosses.

Who runs the daily check

The daily check runs as the user who scheduled Tomba's hourly job (Tomba hourly maintenance in Setup › Scheduled Jobs) and counts the records that user can see. If that user can't see every Lead, Contact and Account, the score covers only part of your data.

Document fields

Open Field documentation, choose an object and click Document fields. You can document Lead, Contact, Account, Opportunity, Case, Campaign, Product, Asset, Contract, Order, Quote and your custom objects.

About a minute later, the document lists the number of fields and records, the unused fields (under 1 % filled) and the least filled fields. CSV opens a Salesforce File with one row per field:

  • label, API name and type;
  • custom, package (the namespace of a managed package field), required, unique and external ID;
  • help text;
  • records filled and filled (%);
  • the 10 most used values, for the first 30 picklists.

The File is private to you: share it from Files. Other Tomba admins see the document's summary but can't open the CSV until you share it. Fill counts cover the records you can see. Fields Salesforce can't count, such as long text areas, have no fill count.

Reports and dashboard

The Tomba Health Score by Day report in the Tomba Reports folder shows the average health score per object over the last 90 days, and the Tomba Data Health dashboard charts it. Every viewer sees the same scores. See Reports, dashboard and record panel.

Credits and limits

  • Health checks, format checks, monitors and field documentation use no Tomba credits. Runs started from a Fix link use credits like any bulk run.
  • A health check counts records with COUNT queries and doesn't load them. If a count times out in a very large org, that part is left out of the score and the rest of the check continues.
  • A format check reads up to 10,000,000 records per run.
Last modified on November 2, 2026
Field mappingClean data
On this page
  • Before you start
  • Check data health
    • How the score is calculated
    • Key fields
    • Format check
  • Fix what the check found
  • Check every day and get alerts
    • Monitors
    • Who runs the daily check
  • Document fields
  • Reports and dashboard
  • Credits and limits