How to read and use the revenuebase_contact_verification_summary field
The revenuebase_contact_verification_summary field gives you a human and machine-readable summary of
how and when RevenueBase verified a contact. Use it to understand data freshness and to display verification
transparency to your users.
Verification summary examples
The revenuebase_contact_verification_summary field looks something like this:
Verified by RevenueBaseExperience last observed on LinkedIn on September 7, 2025: Proposal Manager at MetaphaseProfile: linkedin.com/in/jamie-gregory-xxx333Email last verified on October 15, 2025 via RevenueBase's Email Verification ToolNext verification scheduled: November 2025Learn more at https://revenuebase.ai/verified-by-revenuebase
How to read it
Use this key to interpret each part of the summary:
Element
Meaning
Verified by RevenueBase
The record was verified directly by RevenueBase systems.
Experience last observed
The last time the LinkedIn profile was publicly visible in this state.
Email verified
When the mailbox was confirmed to exist within its domain.
Next verification
When the contact is next scheduled for re-verification.
Observe, verify, reconfirm
RevenueBase follows a clear process for every person record:
1
Observe
We observe publicly available professional information such as LinkedIn profiles.
2
Verify
We verify email deliverability and domain integrity using our proprietary system.
3
Re-confirm
We recheck every contact regularly.
Why this matters
Profiles and domains can change after verification—sometimes even retroactively.
Continuous updates
RevenueBase continuously updates its dataset and reissues verification summaries in every release, so the field always reflects the latest observed and verified information:
Cadence
What happens
Every 30 days
Full dataset refresh.
Every 60 days
Email deliverability is re-verified.
Every 90 days
At least core information (name, location) on profile re-confirmed using a trusted source such as public LinkedIn profiles.
Use the revenuebase_contact_verification_summary field in your UI or exports so your users and AI systems can see verification dates and sources at a glance.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.