> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revenuebase.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Data Overview
> Overview on data with RevenueBase.
export const RBCardGroup = ({cols = 3, children}) =>
}
{tag && {tag}}
;
};
RevenueBase delivers verified B2B data on people and organizations — structured into relational tables and refreshed monthly.
## Core identifiers
Every record links back to one of three identifiers. Getting these right is the foundation for every join, deduplication, and enrichment workflow.
| Identifier | Entity | Scope | What it identifies |
| ---------- | ------------ | ----------- | ---------------------------------------------------------------- |
| `RBID_PER` | Person | Global | The human being — stable across every company they work at |
| `RBID_ORG` | Organization | Global | The company — one ID regardless of how many people work there |
| `RBID_PAO` | Contact | Per company | This person at this company — combines `RBID_PER` and `RBID_ORG` |
**Developer rule of thumb**
1. Use **Person** when you care about *who* someone is — deduplication, career tracking, identity resolution.
2. Use **Contact** when you care about *where* they work and in what role — outbound campaigns, enrichment, work email lookup.
3. A person can have many contacts. A contact belongs to exactly one person and one organization.
### Example: Jane Smith works at two companies
Person
One real human · RBID\_PER
↙ 1 contact1 contact ↘
Contact A
Jane @ Acme Corp
RBID\_PAO: rb-pao-001
Contact B
Jane @ Stripe
RBID\_PAO: rb-pao-002
↓ RBID\_ORG: rb-org-acme
↓ RBID\_ORG: rb-org-stripe
Organization
Acme Corp · RBID\_ORG
Organization
Stripe · RBID\_ORG
Person
Contact (Person × Org)
Organization
| Entity | ID | Key data |
| ------------ | ------------------------- | ----------------------------------------------------------------------- |
| Person | `RBID_PER: rb-per123` | Jane Smith · LinkedIn · personal email |
| Contact | `RBID_PAO: rb-pao-001` | VP Engineering @ Acme · [jane@acme.com](mailto:jane@acme.com) · +1 415… |
| Contact | `RBID_PAO: rb-pao-002` | Advisor @ Stripe · [jane@stripe.com](mailto:jane@stripe.com) |
| Organization | `RBID_ORG: rb-org-acme` | Acme Corp · 500 employees · SaaS · San Francisco |
| Organization | `RBID_ORG: rb-org-stripe` | Stripe · 8,000 employees · Fintech · San Francisco |
If someone holds multiple current positions, they will have **multiple rows** in the person table — each with a unique `RBID_PAO` but sharing the same `RBID_PER`.`RBID_ORG` and `RBID_PAO` may be missing if the person's LinkedIn profile does not link to a company page. This occurs because the company name field on LinkedIn is free text — people can enter anything and may skip linking to an existing company page.
## Table index
| Table | Primary key | Foreign key | Description |
| -------------------------------------------------------------------------------- | -------------- | ------------------------------------------ | ------------------------------------------------------------- |
| [`PER_LATEST`](/docs/data-features/data-tables/person) | `RBID_PAO` | `RBID_ORG` → `ORG_LATEST.RBID` | Contact-level table — one row per person per organization |
| [`ORG_LATEST`](/docs/data-features/data-tables/organization) | `RBID` | — | Organization firmographics — one row per company |
| [`INSIGHTS_LATEST`](/docs/data-features/data-tables/insight) | `RBID_ORG` | `RBID_ORG` → `ORG_LATEST.RBID` | Derived signals and scores at the organization level |
| [`HISTORICAL_EXPERIENCE`](/docs/data-features/data-tables/historical-experience) | `LINKEDIN_URL` | `LINKEDIN_URL` → `PER_LATEST.LINKEDIN_URL` | Job and experience history for a person |
| `VELOCITY_BASE_UNLIMITED_LATEST` | `RBID_PAO` | — | Pre-joined: Person + Organization in a single view |
| `VELOCITY_ENHANCED_UNLIMITED_LATEST` | `RBID_PAO` | — | Pre-joined: Person + Organization + Insights in a single view |
For full field references, see [Person](/docs/data-features/data-tables/person), [Organization](/docs/data-features/data-tables/organization), [Insights](/docs/data-features/data-tables/insight), and [Historical experience](/docs/data-features/data-tables/historical-experience).
## Schema conventions
* **Timestamps** — `UPDATED_AT` and `EMAIL_LAST_VERIFIED_AT` are in UTC. `UPDATED_AT` changes when any field is updated (LinkedIn profile revalidation also triggers it, even with no data changes). `EMAIL_LAST_VERIFIED_AT` tracks the last time the email address was independently revalidated.
* **Nullability** — All fields are nullable. Missing values are `NULL` — not empty strings or sentinel values.
* **Fill rates** — Fill rate is the percentage of rows where a field is non-null. Rates vary by segment: US records and larger organizations typically have higher fill rates for phone, seniority, and financial data. See the [Data Dictionary](/docs/data-features/data-dictionary) for per-field fill rates.
***
## Delivery paths
In Snowflake, tables appear under the `RELEASES` database. For S3 deliveries, each table corresponds to a dataset folder in your bucket.
| Table | Snowflake path | S3 path |
| -------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------- |
| Person | `RELEASES.RELEASE.PER_LATEST` | `/per//` |
| Organization | `RELEASES.RELEASE.ORG_LATEST` | `/org//` |
| Insights | `RELEASES.RELEASE.INSIGHTS_LATEST` | `/insights//` |
| Pre-joined: Person + Organization | `RELEASES.RELEASE.VELOCITY_BASE_UNLIMITED_LATEST` | `/velocity_base_unlimited//` |
| Pre-joined: Person + Organization + Insights | `RELEASES.RELEASE.VELOCITY_ENHANCED_UNLIMITED_LATEST` | `/velocity_enhanced_unlimited//` |
***
## Entity reference
### Person
A real human being. There is exactly one Person record per human, identified by `RBID_PER`. It holds identity-level data — name, personal email, LinkedIn URL.
### Organization
A company. One record per company, identified by `RBID_ORG`. It holds firmographic data — headcount, revenue, industry, location.
### Contact
The join between Person and Organization. Jane at Acme Corp is one Contact; Jane at Stripe is another. Each Contact gets a unique `RBID_PAO`, but the same `RBID_PER` threads through both. If a person holds multiple current positions, they appear in multiple rows — one per organization.
### Email
A verified work email address for the contact at their current organization. Sourced from professional profiles and verified for deliverability. Use this for outbound outreach, enrichment, and CRM sync.
### Phone
A direct dial or company phone number associated with the contact. Where available, includes mobile numbers. Use this for outbound calling, sequencing, and contact enrichment workflows.
***