Contact dataSeptember 2026
B2B data provider benchmark, September 2026
BlitzAPI is the best B2B contact data provider in the September 2026 benchmark: the most accurate records, the highest accuracy and the fewest outdated jobs of the 6 providers tested on the same 3,445 LinkedIn profiles.
Tested on the same 3,445 LinkedIn profiles: Apollo, BlitzAPI, GetLeads.io, MoltSets, Prospeo and QuickEnrich.
Run by BlitzAPI, one of the 6 providers measured. The reference every answer is scored against comes from none of them. How to check us
01
Which B2B data provider returns the most usable contacts?
BlitzAPI returns the most accurate records: 82.4 per 100 contacts, ahead of Apollo (70.0) and Prospeo (52.7).
out of 100 contacts queried
AccurateReturned, not verified accurateNever returned
Show the exact numbers
Each track is the same 100 contacts. Solid is right, hatched came back but was not verified accurate (different title, stale employer or unverifiable), empty never came back at all.
| Provider | Rank | Coverage% of queried | Accuracy% of answered | Accurate per 100 | Interval |
|---|---|---|---|---|---|
| BlitzAPI | 1 | 90.4% | 91.2% | 82.4 | 81.1 to 83.7 |
| Apollo | 2 | 96.8% | 72.3% | 70.0 | 68.4 to 71.5 |
| Prospeo | 3 | 94.9% | 55.5% | 52.7 | 51.0 to 54.4 |
| QuickEnrich | 4 | 68.8% | 63.7% | 43.8 | 42.2 to 45.5 |
| MoltSets | 5 | 84.6% | 51.7% | 43.7 | 42.1 to 45.4 |
| GetLeads.io | 6 | 81.1% | 39.3% | 31.9 | 30.3 to 33.4 |
02
Which B2B data provider is the most accurate?
BlitzAPI is right 91.2% of the time, the highest accuracy of the 6 providers.
right employer and title, % of answers returnedaxis starts at 30%
Show the exact numbers
Each dot is a provider's accuracy. The axis is zoomed so the gaps can be read; every value and every gap is written on its row.
| Provider | Returned | Accuracy% of returned | Interval |
|---|---|---|---|
| BlitzAPI | 3,115 | 91.2% | 90.1 to 92.1 |
| Apollo | 3,334 | 72.3% | 70.8 to 73.8 |
| QuickEnrich | 2,370 | 63.7% | 61.8 to 65.6 |
| Prospeo | 3,271 | 55.5% | 53.8 to 57.2 |
| MoltSets | 2,915 | 51.7% | 49.9 to 53.5 |
| GetLeads.io | 2,793 | 39.3% | 37.5 to 41.1 |
03
Finding more people, or getting them right?
Every other provider sits under BlitzAPI's curve: none returns more accurate records per 100 contacts.
every provider on one frame: how often it answers, and how often that answer is right
How often it answers at allVertical axis: how often that answer is right
Bands, accurate records per 100under 5050 to 6060 to 7070 to 80over 80
BlitzAPIanswers on 90%, right on 91% of those, 82.4 accurate per 100
Apolloanswers on 97%, right on 72% of those, 70.0 accurate per 100
Prospeoanswers on 95%, right on 56% of those, 52.7 accurate per 100
QuickEnrichanswers on 69%, right on 64% of those, 43.8 accurate per 100
MoltSetsanswers on 85%, right on 52% of those, 43.7 accurate per 100
GetLeads.ioanswers on 81%, right on 39% of those, 31.9 accurate per 100
Show the exact numbers
Further right means it answers more often. Higher means the answer is right more often. The dashed curves join the pairs that produce the same number of accurate records, so two providers on one curve are worth the same; the solid blue one passes through BlitzAPI, and a provider under it returns fewer accurate records per 100. The frame is zoomed: answers from 60%, accuracy from 50%, and GetLeads.io, outside it, is pinned to the edge with its real value on the label.
| Provider | Queried | Returned | Right employer | Right employer and title |
|---|---|---|---|---|
| BlitzAPI | 3,445100.0% | 3,11590.4% | 2,91984.7% | 2,84082.4% |
| Apollo | 3,445100.0% | 3,33496.8% | 2,91984.7% | 2,41170.0% |
| Prospeo | 3,445100.0% | 3,27194.9% | 2,18863.5% | 1,81652.7% |
| QuickEnrich | 3,445100.0% | 2,37068.8% | 1,78651.8% | 1,51043.8% |
| MoltSets | 3,445100.0% | 2,91584.6% | 1,91755.6% | 1,50743.7% |
| GetLeads.io | 3,445100.0% | 2,79381.1% | 1,89254.9% | 1,09831.9% |
04
What goes wrong in a bad record?
BlitzAPI has the fewest outdated jobs: 4.4% of its answers, against up to 33.2%.
BlitzAPI3,115 returned
Apollo3,334 returned
Prospeo3,271 returned
QuickEnrich2,370 returned
MoltSets2,915 returned
GetLeads.io2,793 returned
Show the exact numbers
Shares of what each provider returned, so the four verdicts always add up to 100%. Rows keep the order of section 01, which ranks on accurate records per 100: a provider can be right more often than the row above it and still sit lower, because it answers less often.
| Provider | Returned | Right employer and title% of returned | Right employer, different title% of returned | Stale employer% of returned | Unverifiable% of returned |
|---|---|---|---|---|---|
| BlitzAPI | 3,115 | 91.2%2,840 | 2.5%79 | 4.4%138 | 1.9%58 |
| Apollo | 3,334 | 72.3%2,411 | 15.2%508 | 10.8%360 | 1.6%55 |
| Prospeo | 3,271 | 55.5%1,816 | 11.4%372 | 17.5%574 | 15.6%509 |
| QuickEnrich | 2,370 | 63.7%1,510 | 11.6%276 | 24.6%582 | 0.1%2 |
| MoltSets | 2,915 | 51.7%1,507 | 14.1%410 | 33.2%969 | 1.0%29 |
| GetLeads.io | 2,793 | 39.3%1,098 | 28.4%794 | 32.2%900 | 0.0%1 |
05
What happens when someone changes jobs?
Every provider struggles with people who just changed jobs. On jobs held for more than a year, BlitzAPI returns 96 accurate records per 100, the most of any provider.
Measure
accurate records per 100 contacts queried, by months since the current job started
accuracy, the share of returned contacts carrying the right employer and title, by months since the current job started
coverage, the share of contacts the provider returned at all, by months since the current job started
stale rate, the share of returned contacts naming an employer the person has left. Lower is better
| Provider | 0 to 1n = 785 | 2 to 3n = 916 | 4 to 6n = 255 | 7 to 12n = 448 | 12+n = 1,041 | Shape |
|---|---|---|---|---|---|---|
| 65798311 | 7386868 | 9398950 | 9598971 | 9699970 | ||
| 56609418 | 67709510 | 74749910 | 78789911 | 79801006 | ||
| 35389232 | 31339534 | 56599513 | 7476973 | 7579961 | ||
| 22395746 | 19326049 | 31437333 | 6888776 | 7592813 | ||
| 29368150 | 27338249 | 21248752 | 48568628 | 7383887 | ||
| 22297451 | 17227653 | 20238445 | 38448724 | 5361875 |
Reading aidweakest to strongest within a column. Bold marks the strongest value of the column.
How to read this chart
Color is a reading aid only, computed inside each column, and every value is written in the cell. The four measures cover the same people, so a row can be compared from one measure to the next.
Color is a reading aid only, computed inside each column, and every value is written in the cell. This printed copy shows accurate records per 100; accuracy, coverage and the stale rate cover the same people and are on the web page, behind the measure selector.
06
Results by country, industry, seniority and company size
BlitzAPI has the highest result on 29 of the 30 ranked segments.
Measure
accurate records per 100 contacts queried
coverage, the share of the segment the provider answered at all
accuracy, the share of answered contacts carrying the right employer and title
Country
Segments led, of 5 ranked
Segments led are counted on accurate records per 100
Segments led are counted on accurate records per 100
BlitzAPI5
Apollo0
Prospeo0
QuickEnrich0
MoltSets0
GetLeads.io0
| Country | Contacts | ||||||
|---|---|---|---|---|---|---|---|
| United States | 1,649 | 85.792.392.9 | 73.398.474.5 | 56.794.460.1 | 46.673.063.9 | 47.292.551.0 | 29.883.935.6 |
| United Kingdom | 493 | 83.290.791.7 | 68.895.172.3 | 52.194.755.0 | 46.974.063.3 | 43.484.851.2 | 33.982.441.1 |
| Germany | 204 | 70.682.485.7 | 62.395.165.5 | 42.693.645.5 | 38.766.258.5 | 12.726.548.1 | 26.573.036.2 |
| France | 152 | 65.884.278.1 | 50.093.453.5 | 28.399.328.5 | 27.040.167.2 | 34.278.343.7 | 17.870.425.2 |
| Canada | 118 | 83.994.189.2 | 79.7100.079.7 | 58.598.359.5 | 50.071.270.2 | 55.191.560.2 | 39.889.044.8 |
Company size
Segments led, of 8 ranked
Segments led are counted on accurate records per 100
Segments led are counted on accurate records per 100
BlitzAPI8
Apollo0
Prospeo0
QuickEnrich0
MoltSets0
GetLeads.io0
| Company size | Contacts | ||||||
|---|---|---|---|---|---|---|---|
| (unknown) | 939 | 78.086.590.1 | 67.394.970.9 | 50.194.053.2 | 35.961.358.5 | 39.483.747.1 | 29.477.737.8 |
| 51-200 | 599 | 87.391.795.3 | 73.197.874.7 | 57.495.360.2 | 53.173.572.3 | 49.284.658.2 | 35.282.142.9 |
| 1001-5000 | 499 | 84.892.691.6 | 72.197.673.9 | 54.396.656.2 | 48.972.967.0 | 47.185.055.4 | 35.983.443.0 |
| 11-50 | 429 | 90.794.695.8 | 73.498.874.3 | 59.494.662.8 | 50.873.769.0 | 50.888.657.4 | 32.983.739.3 |
| 201-500 | 374 | 88.093.993.7 | 74.197.176.3 | 60.494.963.7 | 52.175.968.7 | 48.785.357.1 | 38.284.045.5 |
| 10001+ | 202 | 65.384.777.2 | 55.094.158.4 | 24.894.626.2 | 19.357.433.6 | 25.276.732.9 | 15.873.321.6 |
| 1-10 | 183 | 80.391.388.0 | 73.298.474.4 | 53.695.156.3 | 42.166.163.6 | 42.189.147.2 | 31.185.836.3 |
| 501-1000 | 148 | 75.791.982.4 | 66.996.669.2 | 47.396.649.0 | 40.570.957.1 | 39.283.846.8 | 26.481.832.2 |
| 5001-10000small sample, not ranked | 72 | 73.684.786.9 | 62.597.264.3 | 44.491.748.5 | 30.666.745.8 | 29.279.236.8 | 27.877.835.7 |
LinkedIn followers
Segments led, of 5 ranked
Segments led are counted on accurate records per 100
Segments led are counted on accurate records per 100
BlitzAPI5
Apollo0
Prospeo0
QuickEnrich0
MoltSets0
GetLeads.io0
| LinkedIn followers | Contacts | ||||||
|---|---|---|---|---|---|---|---|
| 1k-4.9k | 2,002 | 86.793.393.0 | 73.598.674.6 | 55.895.558.5 | 48.973.266.8 | 47.286.754.5 | 35.083.841.7 |
| 5k-9.9k | 503 | 90.796.494.0 | 72.699.073.3 | 61.495.064.6 | 50.976.566.5 | 48.189.953.5 | 35.487.140.6 |
| 500-999 | 384 | 65.982.679.8 | 64.194.368.0 | 36.794.339.0 | 29.958.351.3 | 35.477.945.5 | 25.875.034.4 |
| 10k+ | 312 | 91.795.895.7 | 73.499.473.9 | 66.798.168.0 | 43.968.963.7 | 45.290.150.2 | 29.886.534.4 |
| < 500 | 244 | 44.760.274.1 | 41.078.352.4 | 16.487.718.7 | 9.833.229.6 | 17.660.729.1 | 11.548.823.5 |
Industry
Segments led, of 7 ranked
Segments led are counted on accurate records per 100
Segments led are counted on accurate records per 100
BlitzAPI7
Apollo0
Prospeo0
QuickEnrich0
MoltSets0
GetLeads.io0
| Industry | Contacts | ||||||
|---|---|---|---|---|---|---|---|
| Software Development | 676 | 88.893.594.9 | 75.099.175.7 | 59.595.162.5 | 55.075.772.7 | 45.781.855.9 | 35.584.841.9 |
| Technology, Information and Internet | 245 | 88.294.393.5 | 72.797.174.8 | 59.295.961.7 | 48.672.267.2 | 46.188.252.3 | 33.184.938.9 |
| IT Services and IT Consulting | 179 | 79.989.489.4 | 72.697.274.7 | 54.295.057.1 | 43.067.064.2 | 43.685.551.0 | 33.583.240.3 |
| Higher Education | 159 | 78.091.285.5 | 62.395.665.1 | 44.795.047.0 | 31.464.249.0 | 40.379.950.4 | 30.875.540.8 |
| Financial Services | 132 | 81.891.789.3 | 66.797.768.2 | 53.095.555.6 | 41.771.258.5 | 46.286.453.5 | 22.784.127.0 |
| Business Consulting and Services | 119 | 78.291.685.3 | 66.498.367.5 | 45.495.047.8 | 33.663.053.3 | 36.189.140.6 | 26.179.033.0 |
| (unknown) | 102 | 69.682.484.5 | 65.788.274.4 | 39.290.243.5 | 27.547.158.3 | 37.388.242.2 | 24.561.839.7 |
| Hospitals and Health Caresmall sample, not ranked | 63 | 74.685.787.0 | 66.795.270.0 | 46.092.150.0 | 33.361.953.8 | 34.988.939.3 | 33.377.842.9 |
Seniority
Segments led, of 5 ranked
Segments led are counted on accurate records per 100
Segments led are counted on accurate records per 100
BlitzAPI4
Apollo1
Prospeo0
QuickEnrich0
MoltSets0
GetLeads.io0
| Seniority | Contacts | ||||||
|---|---|---|---|---|---|---|---|
| Director | 1,121 | 89.393.595.5 | 74.098.874.9 | 62.096.364.4 | 55.077.471.1 | 49.186.456.8 | 38.785.545.3 |
| C-level/Founder | 860 | 84.790.893.2 | 75.597.177.7 | 60.693.664.7 | 42.862.368.7 | 49.787.356.9 | 33.781.041.6 |
| VP | 642 | 94.998.396.5 | 76.599.876.6 | 67.197.069.2 | 63.682.477.1 | 55.991.061.5 | 41.388.946.4 |
| IC/Staff | 542 | 60.578.876.8 | 48.989.754.5 | 20.393.021.8 | 13.147.627.5 | 20.872.328.8 | 13.365.920.2 |
| Manager | 280 | 62.181.476.3 | 62.994.366.7 | 21.192.922.7 | 16.463.925.7 | 20.778.226.5 | 13.275.017.6 |
07
Head to head: how every pair compares
On the people both providers found, BlitzAPI is right more often than each of the 5 others.
points of accuracy, row against column, on the contacts both returned
| Row is ahead by | Ahead on | ||||||
|---|---|---|---|---|---|---|---|
| +18.13,081BlitzAPI is ahead of Apollo by 18.1 points on 3,081 shared contacts | +33.43,033BlitzAPI is ahead of Prospeo by 33.4 points on 3,033 shared contacts | +28.72,287BlitzAPI is ahead of QuickEnrich by 28.7 points on 2,287 shared contacts | +39.82,730BlitzAPI is ahead of MoltSets by 39.8 points on 2,730 shared contacts | +52.42,683BlitzAPI is ahead of GetLeads.io by 52.4 points on 2,683 shared contacts | 5 of 5 | ||
| −18.13,081Apollo is behind BlitzAPI by 18.1 points on 3,081 shared contacts | +16.73,213Apollo is ahead of Prospeo by 16.7 points on 3,213 shared contacts | +14.32,366Apollo is ahead of QuickEnrich by 14.3 points on 2,366 shared contacts | +24.32,889Apollo is ahead of MoltSets by 24.3 points on 2,889 shared contacts | +37.12,784Apollo is ahead of GetLeads.io by 37.1 points on 2,784 shared contacts | 4 of 5 | ||
| −33.43,033Prospeo is behind BlitzAPI by 33.4 points on 3,033 shared contacts | −16.73,213Prospeo is behind Apollo by 16.7 points on 3,213 shared contacts | +3.02,327Prospeo is ahead of QuickEnrich by 3.0 points on 2,327 shared contacts | +7.92,895Prospeo is ahead of MoltSets by 7.9 points on 2,895 shared contacts | +24.32,762Prospeo is ahead of GetLeads.io by 24.3 points on 2,762 shared contacts | 3 of 5 | ||
| −28.72,287QuickEnrich is behind BlitzAPI by 28.7 points on 2,287 shared contacts | −14.32,366QuickEnrich is behind Apollo by 14.3 points on 2,366 shared contacts | −3.02,327QuickEnrich is behind Prospeo by 3.0 points on 2,327 shared contacts | +10.12,176QuickEnrich is ahead of MoltSets by 10.1 points on 2,176 shared contacts | +22.72,292QuickEnrich is ahead of GetLeads.io by 22.7 points on 2,292 shared contacts | 2 of 5 | ||
| −39.82,730MoltSets is behind BlitzAPI by 39.8 points on 2,730 shared contacts | −24.32,889MoltSets is behind Apollo by 24.3 points on 2,889 shared contacts | −7.92,895MoltSets is behind Prospeo by 7.9 points on 2,895 shared contacts | −10.12,176MoltSets is behind QuickEnrich by 10.1 points on 2,176 shared contacts | +13.02,578MoltSets is ahead of GetLeads.io by 13.0 points on 2,578 shared contacts | 1 of 5 | ||
| −52.42,683GetLeads.io is behind BlitzAPI by 52.4 points on 2,683 shared contacts | −37.12,784GetLeads.io is behind Apollo by 37.1 points on 2,784 shared contacts | −24.32,762GetLeads.io is behind Prospeo by 24.3 points on 2,762 shared contacts | −22.72,292GetLeads.io is behind QuickEnrich by 22.7 points on 2,292 shared contacts | −13.02,578GetLeads.io is behind MoltSets by 13.0 points on 2,578 shared contacts | 0 of 5 |
Row ahead, darker is a wider gapRow behindSmall figure in each cell: contacts both providers returned
Show the exact numbers
Read a row against the columns. Coverage drops out: each pair is measured only on the people both providers answered for. A cell is tinted only when the row is ahead, so a full row is a provider ahead of everyone.
| Pair | Both returned | First is right | Second is right | Gap |
|---|---|---|---|---|
| BlitzAPI vs GetLeads.io | 2,683 | 92.1% | 39.7% | 52.4 pts |
| BlitzAPI vs MoltSets | 2,730 | 92.1% | 52.3% | 39.8 pts |
| Apollo vs GetLeads.io | 2,784 | 76.4% | 39.3% | 37.1 pts |
| BlitzAPI vs Prospeo | 3,033 | 91.3% | 57.9% | 33.4 pts |
| BlitzAPI vs QuickEnrich | 2,287 | 93.4% | 64.7% | 28.7 pts |
| Apollo vs MoltSets | 2,889 | 76.0% | 51.7% | 24.3 pts |
| Prospeo vs GetLeads.io | 2,762 | 63.3% | 39.0% | 24.3 pts |
| QuickEnrich vs GetLeads.io | 2,292 | 64.5% | 41.8% | 22.7 pts |
| BlitzAPI vs Apollo | 3,081 | 91.4% | 73.3% | 18.1 pts |
| Apollo vs Prospeo | 3,213 | 73.1% | 56.4% | 16.7 pts |
| Apollo vs QuickEnrich | 2,366 | 78.0% | 63.7% | 14.3 pts |
| MoltSets vs GetLeads.io | 2,578 | 52.3% | 39.3% | 13.0 pts |
| QuickEnrich vs MoltSets | 2,176 | 64.2% | 54.1% | 10.1 pts |
| Prospeo vs MoltSets | 2,895 | 59.5% | 51.6% | 7.9 pts |
| Prospeo vs QuickEnrich | 2,327 | 66.8% | 63.8% | 3.0 pts |
Each provider against BlitzAPI, one page per pair
Apollo alternativeBlitzAPI vs ApolloRight employer and title, 3,081 people both foundBlitzAPI right 18.1 pts more often
Prospeo alternativeBlitzAPI vs ProspeoRight employer and title, 3,033 people both foundBlitzAPI right 33.4 pts more often
QuickEnrich alternativeBlitzAPI vs QuickEnrichRight employer and title, 2,287 people both foundBlitzAPI right 28.7 pts more often
MoltSets alternativeBlitzAPI vs MoltSetsRight employer and title, 2,730 people both foundBlitzAPI right 39.8 pts more often
GetLeads.io alternativeBlitzAPI vs GetLeads.ioRight employer and title, 2,683 people both foundBlitzAPI right 52.4 pts more often
08
Does adding a second provider help?
Querying a second provider on the misses lifts the run from 82.4 to 86.9 accurate records per 100. A third adds 0.3.
accurate records per 100 contacts, cumulative
StartBlitzAPI3,445 contacts queried
82.4start
Then
Apollo330 misses queried, 253 returned
86.9+4.4
Then
MoltSets77 misses queried, 20 returned
87.1+0.3
Then
Prospeo57 misses queried, 15 returned
87.2+0.0
Then
QuickEnrich42 misses queried, 1 returned
87.2+0.0
Best possible with all providers: 91.2. Reaching it would mean knowing which answers are wrong without a reference.
Show the exact numbers
Each step queries only the contacts no earlier step returned, which is what a waterfall can really recover. The chain starts from the top of the ranking, a sorting rule rather than a recommendation.
| Chain | Queried at this step | Coverage | Accurate per 100 | Records gained |
|---|---|---|---|---|
| BlitzAPI | 3,445 | 90.4% | 82.4 | |
| BlitzAPI then Apollo | 330 | 97.8% | 86.9 | +153 |
| BlitzAPI then Apollo then MoltSets | 77 | 98.3% | 87.1 | +9 |
| BlitzAPI then Apollo then MoltSets then Prospeo | 57 | 98.8% | 87.2 | +1 |
| BlitzAPI then Apollo then MoltSets then Prospeo then QuickEnrich | 42 | 98.8% | 87.2 | +1 |
09
Every result in one table
| Measure | BlitzAPI | Apollo | Prospeo | QuickEnrich | MoltSets | GetLeads.io |
|---|---|---|---|---|---|---|
| Accurate records per 100 queried | 82.4 | 70.0 | 52.7 | 43.8 | 43.7 | 31.9 |
| Coverageanswered, % of queried | 90.4% | 96.8% | 94.9% | 68.8% | 84.6% | 81.1% |
| Accuracyright employer and title, % of answered | 91.2% | 72.3% | 55.5% | 63.7% | 51.7% | 39.3% |
| Right employer, any title% of answered | 93.7% | 87.6% | 66.9% | 75.4% | 65.8% | 67.7% |
| Stale rateemployer the person has left, % of answered | 4.4% | 10.8% | 17.5% | 24.6% | 33.2% | 32.2% |
| Work history recall% of reference roles | 96.1% | 86.1% | 69.6% | 17.3% | 16.5% | 17.1% |
| Queried on | 2026-09-17 | 2026-09-17 | 2026-09-17 | 2026-09-18 (+1d) | 2026-09-18 (+1d) | 2026-09-18 (+1d) |
| Separate recomputation | 9 of 9 pass | 9 of 9 pass | 8 of 9, 1 warning | 9 of 9 pass | 9 of 9 pass | 9 of 9 pass |
10
How we ran the test
The reference
On the day of the test, the public LinkedIn profile of every contact was read from a source that is none of the providers tested, one row per role held. 3,916 profiles came back, 100.0% of those requested, producing 39,836 experience rows.
It comes from none of the providers being tested. A benchmark scored against one vendor's database measures similarity to that vendor, not accuracy.
The rules
Every provider received the same list through its own public API with the same input, one contact per query or in the batches its API requires. Employers are matched by LinkedIn company id, then company URL slug, then normalized company name; then the title on the matched role, after normalization.
Before publication, a separate script recomputes every verdict and aggregate from the raw answers: 9 checks per provider. Prospeo passes with a warning, on a field its answers never fill. The reference itself passes 12 of 13 gates.
Who was left out
- 435started the current job in the month of the test, so no index could reasonably have seen it yet
- 20have no current role on their profile, so there is nothing to be right or wrong about
- 15have fewer than 30 connections, our floor for an active account
- 1have no start date on the current role, so job age cannot be computed
They were removed before any provider was queried, never after. Excluding contacts once the answers are in is the easiest way to shape a benchmark.
The population
| Cohort | Contacts | What it isolates |
|---|---|---|
| New jobs · Americas | 835 | Recent job changes, Americas (Sales Navigator export, 17 Sept 2026) |
| New jobs · Europe | 723 | Recent job changes, Europe (Sales Navigator export, 17 Sept 2026) |
| Large cos · US/UK | 494 | Sample 1.1: marketing leaders, large companies (1,001-5,000+ employees), mostly US/UK |
| SMB industry · US | 490 | Sample 1.4: VP / Director marketing, 51-500 employees, US, manufacturing / medtech / pharma |
| SMB · EMEA | 454 | Sample 1.3: marketing leaders, 51-500 employees, EMEA (UK, DE, IL, FR, ES) |
| Micro cos · US | 449 | Sample 1.2: marketing / growth leaders, very small companies (1-50 employees), mostly US |
The providers, and how each was queried
BlitzAPIPOST https://api.blitz-api.ai/v2/enrichment/person
ApolloPOST https://api.apollo.io/api/v1/people/match
ProspeoPOST https://api.prospeo.io/enrich-person
QuickEnrichGET https://app.quickenrich.io/api/employees/search
MoltSetsPOST https://api.moltsets.com/api/v1/reverse_linkedin_lookup
GetLeads.ioDirect API route not published here
Each provider keeps the same colour in every figure and in every edition, from the first report it appears in. Colours follow the order providers first appear, then the alphabet, never the ranking. BlitzAPI, which runs the test, is drawn in its brand blue.
Full protocol, definitions, uncertainty rules, limits and the corrections policy: the methodology page.
11
Download the full report
The report as one printable document, with every figure and every number drawn from the same data as this page.
You are reading it. This document is the report page, printed: every figure and every number in it comes from the same data as the page. The live version is at blitz-api.ai/benchmarks/contact-data-september-2026.
Figures with a measure selector print on their default measure; the other measures stay on this page.
sha256 693b229deb5f6b33
No row in this report identifies a person. If you appear in a reference and want out of future runs, write to antoine@blitz-api.ai.
Other reports
Questions about this benchmark
Which B2B data provider is the most accurate?
BlitzAPI had the highest accuracy: 91.2% of its answers named the right current employer and job title. The other five were 18.9 to 51.9 points lower. Measured in the September 2026 benchmark of 6 providers on the same 3,445 LinkedIn profiles.
What happens to contact data when someone changes jobs?
People who just changed jobs are the hardest to get right, for every provider: on jobs started 1 month or less before the test, accurate records per 100 contacts ran from 22 to 65, against 53 to 96 on jobs started more than 12 months before. BlitzAPI went from 65 on the newest jobs, the most of any provider, to 96 on the oldest.
How often is B2B contact data out of date?
BlitzAPI had the fewest outdated jobs: 4.4% of its answers named a company the person had already left, against up to 33.2% (MoltSets). For every provider, most outdated answers are lag rather than invention: 84% to 94% of them name a company the person really worked for, just not anymore.
Does adding a second data provider (a waterfall) help?
It helps on the contacts the first provider misses, and this run measures by how much. Starting from BlitzAPI (82.4 accurate records per 100 contacts), sending only the contacts it missed to Apollo lifts the run to 86.9. A third provider adds 0.3 more. With all 6 providers, at least one is right on 91.2% of the contacts, but nobody can tell which answer is the right one without a reference.
How was the benchmark run?
Each provider's API was queried once per person, on the same 3,445 LinkedIn profiles, on September 17 and 18, 2026. Every answer was then checked against the person's public LinkedIn profile read on the test date: it counts as accurate only when both the current employer and the job title match. The same rules apply to every provider, and the reference comes from none of them.
Who ran this benchmark, and can I trust it?
BlitzAPI runs this benchmark and is one of the 6 providers tested. The reference every answer is scored against comes from none of them, the rules are published, and every result is online. That includes the measures where BlitzAPI is behind, such as the share of people found, where it is third of 6.
Is the full report free?
Yes. The full September 2026 report is a free PDF, with no email and no form, and every figure on this page is published under CC BY 4.0: reuse it anywhere, with attribution.