Skip to content

Contact Data Provenance: 10 Questions to Ask Data Vendors

Ten questions to ask a B2B data vendor about where contact data comes from, how fresh it is and how it is checked, plus a simple test.

Abedrahim B Nov 17, 2026 4 min read 970 words
Contact Data Provenance: 10 Questions to Ask Data Vendors

Contact data provenance is the record of where a piece of contact data came from, when it was collected, and how it was checked. Two vendors can sell what looks like the same list, with the same columns and the same claims, and still differ sharply in quality and in risk. The difference sits in the origin. This guide gives you ten questions to ask any B2B data vendor before you buy, and how to read the answers.

Contact data provenance questions cover
Contact data provenance questions cover

TL;DR#

  • Ask where each field comes from, and when it was last confirmed.
  • A vendor that cannot explain its sources is asking you to carry the risk.
  • Test with a sample you can check yourself, before you pay for a full list.
  • Keep a record of what you were told, because you may need it later.

Why does contact data provenance matter?#

Provenance affects three things you care about.

  1. Accuracy. Data from a live, recent source is more likely to be right than a copy of a copy.
  2. Deliverability. Old or scraped lists are where bounces and spam traps come from. See our guide to B2B contact data decay for how fast records age.
  3. Legal exposure. If you hold personal data, you may need to tell people where it came from. Article 14 of the GDPR, which covers information to give when data was not collected from the person, includes the source of the data. If your vendor cannot tell you the source, you cannot pass it on.

This is not legal advice. Ask your own counsel how the rules apply to you.

What are the types of contact data sources?#

Most B2B data comes from a mix of these:

Source type Example Strength Weakness
Public web pages Company sites, press pages, articles Easy to check yourself Can be out of date
Public profiles Professional networks, directories Rich detail Terms of use limit some uses
User-contributed data Contacts shared by members Broad coverage Consent and accuracy questions
Pattern inference Guessing first.last@company.com Fills gaps Must be verified
Direct verification Checking the mailbox with the mail server Strong signal Does not work on catch-all domains

None of these is wrong by itself. The risk is a vendor that mixes them and cannot say which is which.

Which questions should you ask a data vendor?#

About the source#

  1. Where does each field come from? Email, phone, title and company may each come from a different place.
  2. Is any of it bought or resold from another vendor? A chain of resellers loses the trail.
  3. How are people told their data is held, and how can they opt out?

About freshness#

  1. When was each record last checked? Ask for a date per record, not a general claim.
  2. How often is the database refreshed? Ask for the process, not just the promise.

About checks#

  1. How are emails verified? Ask whether the vendor checks them when you ask, or only when they were first collected.
  2. How are catch-all domains handled? A good answer admits the limits.
  3. What happens to a bounce? Does the record get removed or flagged?

About the contract#

  1. What do you promise if the data is wrong? Look for credits for bounces, not just a refund policy.
  2. Can I see a source statement? Tomba publishes a page on where its data comes from. A vendor that does the same makes your review easier.

How do you test contact data provenance claims?#

Do not rely on the sales deck. Run a small test yourself.

  1. Pick 50 to 100 contacts that you can check by hand: people at companies you know.
  2. Ask the vendor for those records, or run them through its tool.
  3. Compare the title and company with the company's own site.
  4. Run the emails through a verifier such as the Tomba Email Verifier, and count what comes back invalid.
  5. Send a small, careful batch to the valid ones and watch bounces and replies.

Record the result for each vendor in the same sheet. A fair comparison needs the same sample for everyone.

What are the red flags in contact data provenance?#

  • No answer, or a vague one, to "where does this come from?".
  • A claim of a single, huge accuracy number with no method behind it.
  • A price per record that is far below the market, with no explanation.
  • No way for people to opt out or ask for their data to be removed.
  • Pressure to buy the full list before you can test it.

How can you build your own provenance record?#

For every list you load into your CRM, store the vendor, the date, the method and the terms. Add a "source" field to each contact. When someone asks where you got their address, you can answer in one minute. Good contact data provenance records are cheap to keep and expensive to rebuild later.

Frequently asked questions#

What is contact data provenance?#

It is the history of a contact record: where it came from, when it was collected and how it was checked.

Is scraped data always bad?#

Not always. Public pages are a common source. The question is whether the vendor can explain what it collects, how it uses it and how people can opt out.

How often should I recheck bought data?#

Check it before every send, and verify again if the record is more than a few months old.

Do I need to know the source for every record?#

For personal data, you may. Keep a source field in your CRM, and ask your counsel what your rules require.

Next step#

Ask your current vendor the ten questions above, and note the answers. To compare, test the Tomba Domain Search on a company you know well.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
Abedrahim B

// about the author

Abedrahim B

CEO

Was this helpful?