Skip to main content
The Data Dictionary has the most up-to-date field definitions for this table. Use it as your primary reference for column names and descriptions.
Column names in this table have no _ORG suffix. Use HEADQUARTERS_CITY, INDUSTRY_LINKEDIN, etc. exactly as listed below — do not append _ORG to any field when querying RELEASE.ORG_LATEST directly. The _ORG suffix appears only in INSIGHTS_LATEST and the pre-joined VELOCITY_* tables, where it disambiguates organization fields after a merge — never in ORG_LATEST itself.
The organizations table contains organization-level records with firmographic data. Use it for account targeting, ICP filtering, segmentation, and enriching your CRM with organization-level attributes. One row per organization; join to contacts and insights via RBID.

Where data comes from

Organization records are built from public profiles, websites, regulatory filings, and third-party data providers. Industry and size are normalized for consistent filtering. Location and financials are updated with each release; fill rates for revenue and funding are higher for public and venture-backed organizations.

Organization counts by region

The map below shows current organization counts by country. Use it to understand coverage and plan account-based campaigns by region.

Table stats

Data dictionary

For the complete and most current field reference, see the Data Dictionary. Fill rate is the percentage of rows where a field is non-null. Rates vary by segment (e.g. US and public organizations often have higher fill rates for financials and industry).

Identifiers

Organization basics

Industry & classification

Size & financials

Addresses

Location vs. Headquarters: For small organizations, location and HQ fields may point to the same address. For organizations with multiple branches, the LOCATION_* fields represent one of the locations listed on the organization’s LinkedIn page, while HEADQUARTERS_* fields are derived from the headquarters information on the LinkedIn organization page.

Metadata

Joining this table

Join org_latest to per_latest on RBID = RBID_ORG to attach firmographics to people. Join to insights_latest on RBID = RBID_ORG to attach buying signals and technographics.

Organization + Person (accounts with decision-makers)

Organization + Insights (firmographics + signals)

How to calculate fill rates

Use this pattern to compute fill rates for any field or segment. Replace the sample fields with the columns you care about.

Sample queries

Find target accounts by ICP (mid-size software in the US)

What you’re finding: Organizations that match your ideal customer profile so you can build an account list or sync to a CRM. Why these fields: industry and employee_count define ICP; revenue_range adds budget signal. hq_city and hq_state support territory or regional campaigns. We select only the columns you’d need for account creation or routing. Logic: Filter by industry, size band, country, and revenue band. Order by employee_count to prioritize larger accounts within the band.

Normalize LinkedIn URN

What you’re finding: The LINKEDIN_URL_ID field contains LinkedIn’s numeric organization identifier. Some integrations (e.g. LinkedIn Ads, Sales Navigator APIs) require the full URN format (urn:li:organization:<id>) rather than the raw ID or URL. Why these fields: LINKEDIN_URL_ID is the source value; the query constructs the URN by prepending the standard LinkedIn organization URN prefix. Rows without a LINKEDIN_URL_ID are excluded.

Check fill rates for a segment

What you’re finding: How complete key fields are for a subset (e.g. one industry or region) so you know what to expect when building lists. Why these fields: Same as the global fill-rate query, but with a WHERE clause so percentages reflect only the segment you care about.