Every field. Every source.
Full transparency.

A fill rate is the share of records in the Bulkdata.ai index that carry a value for that particular field. A field at a high fill rate is populated on most records; a low one means the attribute is genuinely scarce rather than that the record is broken. It describes observed coverage across the whole index, so it is a planning figure rather than a promise about any specific list.

Contact records group into identity fields such as name and record ID, professional fields such as job title, job function, seniority level and department, contact channels including business email, email verification status, direct dial, mobile and company phone, a LinkedIn profile URL, and location fields down to city, region, country and ISO country code. The data dictionary lists each field with its type, its description and its fill rate.

Company records cover firmographics such as name, domain, website, industry classification and SIC or NAICS codes; size fields including employee count and employee range; financial fields including revenue and revenue range; background fields such as founded year, company type and full headquarters address; plus a main phone number and social profile URLs. Every one is listed in the data dictionary with its type and observed fill rate.

No. Technographic fields — detected technologies, technology categories and stack size — are only present where a company’s public web properties expose enough to detect them. Intent fields, covering researched topics, a composite intent score and a detection date, are present only where a signal has actually been observed. Both carry visibly lower fill rates than core firmographics in the data dictionary, which is the honest picture rather than a gap.

Not necessarily. A fill rate describes coverage across the entire Bulkdata.ai index, and any specific list is a slice of it — coverage varies by market, by industry, by company size and by seniority. The reliable way to know what a field looks like for your target market is to run a sample of your own accounts and read the result, which is what a demo session is for.