Two providers, no integration. Apollo cannot tell you what a waterfall call will cost, and says so.
An Apollo paid plan for API enrichment, a Reverse Contact API key, and an orchestrator to run the waterfall
Contacts, Companies, one way, out.
These are competitors, so the honest page is a waterfall rather than an integration, and the useful finding is not about coverage. It is that Apollo is itself a waterfall over data partners your admin configures, which means Apollo cannot tell you in advance what a call will cost or whether a miss is billed, and its documentation says exactly that. Reverse Contact publishes a credit cost per endpoint and a flat rule that errors are free. Those are two different products wearing the same category name, and knowing which one you are buying matters more than either coverage figure.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Nothing | One way, out | There is no sync between two data providers, no app on either side and nothing to configure between them. |
| The first call | One way, out | Whichever provider suits the identifier you hold, in Clay, n8n or your own code. |
| The fallback | One way, out | The other provider, on the rows that came back null. This is the only sense in which the two are connected. |
| The verification | One way, out | A separate step at the end, which almost every practitioner who has built this says they added. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
There is nothing to map between two data providers. What is worth laying out is what each call costs, what each one returns when it fails, and what the published coverage figures actually count, because that last one is where most comparisons of these two go wrong.
| In Apollo | In Reverse Contact | What to know about the match |
|---|---|---|
| An email, a name or a domain | Reverse Contact: 2 credits, unmetered from $699 | Identity, the current role, history and the company on one schema. A miss returns null with a confidence score and costs nothing. |
| A profile URL | Reverse Contact: 1 credit, unmetered from $249 | Half the price, same schema. The identifier you hold decides the bill more than the plan does. |
| A set of filters, looking for new people | Apollo search, or Reverse Contact people search | Apollo's paid plans allow 200 search requests a minute, 6,000 an hour and 50,000 a day. Reverse Contact charges 1 credit per profile delivered and nothing for the count endpoint that sizes the result first. |
| A record missing an email or a phone | Apollo waterfall, with run_waterfall_email or run_waterfall_phone | Needs a webhook_url, and phone results come back only at the webhook. The sources queried, and what a miss costs, are whatever your admin configured. |
| The same gap | Reverse Contact Find Email at 3, Find Phone at 20 | Charged only when one is found, asynchronous, returning a task id to poll with check_task. These stay on credits on every plan. |
| A record you think is stale | The free check, then a 2-credit live refresh | The check costs nothing and says when the profile was last updated. The live refresh is the one call here billed even when it finds nothing. |
| Either provider's answer | A verifier, before a sequence | Resolved is not deliverable. This step is in every practitioner account of this build and in neither vendor's quickstart. |
| Anything between the two | Nothing at all | No sync, no app, no shared record. The orchestrator is the only thing that knows both exist. |
The coverage comparison is the reason a page like this is usually not written, so here it is with each figure attributed to the vendor that publishes it. The point of the table is the second column: these are not the same unit, and a ratio between them is arithmetic rather than information.
| The published figure | What it actually counts |
|---|---|
| Reverse Contact: 800M+ profiles, 70M+ companies | Public professional profiles. A profile is an identity you can resolve to, not a mailbox you can write to, and the product is built around going from an identifier you hold to one of these |
| Apollo: 240M contacts, 30M companies | Contact records in a database you search. A contact is a person with contact details attached, which is a smaller and more expensive thing to assemble than a profile |
| The ratio between them, about three to one | Nothing you can act on. Three times as many profiles is not three times as many people you can email, because the two numbers are not counting the same object |
| Reverse Contact: a 70%+ identity match rate | A global average across their whole corpus, published as one, with the instruction to measure your own on 500 rows. It is not a prediction about your list |
| Apollo: no published match rate | Their documentation instead names the identifiers that improve one, which is first and last name, a LinkedIn URL, or an email. That is more useful than a number and it is not comparable to one |
| Reverse Contact: 200M refreshes a month | How often the corpus is revisited, which is the figure that decides whether a record resolved today reflects this year. Apollo publishes no equivalent in the material cited here |
| What a competitor publishes about Apollo | A different number again. ZoomInfo's own site gives Apollo 270M contacts and 70M companies, against Apollo's own 240M and 30M, which is the clearest possible argument for only ever quoting a vendor about itself |
A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, seven the published figure rows and four documented exclusions, each one's note, and the ten vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The last row of the second table is the one to remember when anybody sends you a comparison chart: two vendors publish two different figures for Apollo, and only one of them is Apollo. Quote a vendor about itself, count your own rows, and treat every corpus number as a description of a database rather than a forecast about your list.
Comparing coverage is the obvious thing to do here and the least useful, because neither figure predicts your list. What you can compare properly is predictability: whether the cost of a call is published, whether a miss is billed, whether the answer arrives in the response, and whether any plan stops metering it. Every cell is from the vendor's own documentation. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The route | The per-call cost is published | A miss is free | The answer is in the response | Some plan stops metering it |
|---|---|---|---|---|
| Apollo search over its database | Not published | Not published | Synchronous | Always on credits |
| Apollo waterfall for email or phone | Depends on your config | Depends on your config | Webhook only | Always on credits |
| Reverse Contact from an email or domain | Published | Free | Synchronous | Unmetered from $699 |
| Reverse Contact from a profile URL | Published | Free | Synchronous | Unmetered from $249 |
| Reverse Contact Find Email or Find Phone | Published | Free | A task id to poll | Always on credits |
Counted off that grid, of twenty pairings: three give you published, two give you depends on your config, two give you not published, three give you free, three give you synchronous, one gives you webhook only, one gives you a task id to poll, one gives you unmetered from $249, one gives you unmetered from $699, three give you always on credits. Read the first two columns of the second row together, because that is the finding and it is not a criticism. A waterfall over partners somebody configures cannot publish a per-call price or a miss policy, since both depend on which partners are in it, and Apollo says so plainly. The cost of predictability is the bottom row, where Reverse Contact is also asynchronous and also never unmetered, which is worth printing on a page its publisher pays for.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Your own notes, not a tool
Finding people you did not know about is a search problem and resolving somebody you already hold is a lookup problem. They have different costs, different failure modes and different providers, and a waterfall that mixes them pays search prices for rows that only needed resolving.
Your CRM, your list or your warehouse
A profile URL is a 1-credit cached lookup on Reverse Contact and unmetered from the $249 plan. An email, a name or a domain is 2 credits and unmetered only from $699. Apollo separately advises a name, a LinkedIn URL or an email for better match rates, so the audit pays off on both sides.
Apollo and Reverse Contact
Reverse Contact gives a trial with no card and 500 credits on a new account, which is 500 profile-URL lookups or 250 reverse ones, and it runs until those credits are spent rather than for a number of days. Apollo grants 30,000 credits per seat per year upfront on Basic, so a pilot there is a draw against a budget you have already committed.
Your orchestrator
The provider whose misses are free belongs first, because the rows it cannot resolve cost nothing to discover. On Reverse Contact that is every endpoint except a live fetch; on Apollo's waterfall it depends on which sources your admin configured, so find that out before fixing the order.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a second pass over a list pays only for what has moved. On a bake-off this also tells you how much of one provider's apparent advantage is simply a fresher copy of the same record.
Apollo: webhook_url on the request
Apollo requires a valid webhook_url on every waterfall request and does not return phone numbers in the synchronous response. A build that reads only the immediate reply will report that phones are never found, which is a configuration error that looks exactly like a coverage result.
A verifier, at the end
Every practitioner account of this build ends with a verification step, and several describe paying for verified addresses that bounced anyway. A resolved identity and a deliverable address are two different claims and only one of them is what a sequence needs.
Your bake-off sheet
A provider can identify the right person and give you a dead address, or give you a live address for the wrong person, and a single accuracy number hides both. Reverse Contact returning null with a confidence score rather than a guess is only worth something if your count distinguishes a refusal from a mistake.
Your orchestrator
Fall through to the other provider, queue for review, or write nothing. All three are defensible and the one that is not is writing a low-confidence guess into a field that a rep will read as a fact.
Only the first step is expensive to get wrong, and it is a question rather than a configuration: find somebody, or resolve somebody. Everything after it is an afternoon of plumbing and a week of counting, and the counting is the part that produces an answer you can defend to whoever is paying for both.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/apollo-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/apollo-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyApollo requires a webhook_url on every waterfall request and phone results are not in the synchronous response.
Stand the webhook up first and confirm it receives a test payload. This failure is indistinguishable from a coverage problem and has been mistaken for one.
WhyA waterfall was ordered by coverage rather than by what a miss costs, so the rows nobody could resolve were discovered expensively.
Put the provider whose misses are free first. Find out which of your configured Apollo sources charge on a lookup rather than on a result, since Apollo states that both kinds exist.
WhyFind somebody new and resolve somebody you hold were treated as the same operation, which is the mistake step one of the checklist exists to prevent.
Split the list by the identifier it carries. Rows with an email or a profile URL go to a lookup, and only the rows with neither need a search.
WhyResolution and deliverability are two different claims, and neither provider's match is a delivery guarantee.
Add a verification step before anything reaches a sequence, and count bounces separately from misses. Every practitioner account of this build includes this step and neither vendor's quickstart does.
WhyGeneral endpoints allow 200 a minute, 400 an hour and 2,000 a day on Basic and Professional, with Organization at 200, 600 and 6,000.
Honour the retry-after header and check which plan the key belongs to, because the hourly and daily figures differ between Basic and Organization while the per-minute one does not.
WhyReverse Contact's covered calls are unmetered up to 100,000 profiles per workspace per UTC day and refused after that until midnight UTC.
Spread the job across UTC days. The minute limit is 100 on Go, Plus and Max alike, so a bigger plan buys unmetered families rather than a faster backfill.
WhyA cached database is as current as its last refresh, and the two corpora are refreshed on different schedules.
Treat the disagreement as the signal rather than as an error, and check the update date. Reverse Contact's free check returns when the profile was last updated, which is the cheapest tiebreak available.
WhyVendors publish figures for their competitors. ZoomInfo's own site gives Apollo 270M contacts and 70M companies while Apollo publishes 240M and 30M.
Quote a vendor only about itself, and run your own 500 rows. A number nobody will stand behind in their own documentation is not a number to buy on.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2025 to 2026 were read in full on 28 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
I've also found Apollo will often return HQ phone numbers and just blatant wrong info rather than "no number" which is a problem. [...] The biggest problem I've seen when sourcing from Apollo is wrong numbers though.
r/gtmengineering·September 2026·1 points
The single most relevant comment in any of the seven harvests, and the person writing it was reviewing a dialer rather than making an argument about data quality. Returning a plausible value instead of an admission is the failure that reports success, and it is the reason this directory treats null with a confidence score as a feature rather than as a gap. It is also a reminder that the same complaint will be made about any provider that guesses.
I've used data enrichment tools for over 7 years. All these tools they get their data from the same vendors. The only difference is how frequently they update their database.
r/gtmengineering·September 2026·3 points
A strong claim from one experienced person rather than a demonstrated fact, and worth holding loosely for that reason. What makes it worth printing is the second sentence, which names refresh rate as the real differentiator, and that is a figure one side of this comparison publishes and the other does not. It also explains why a bake-off on your own rows beats any coverage table.
apollo's been sliding for a while now. i used to pull solid lists from there but lately it's like half the contacts are from companies that got acquired two years ago or people who left six months back
r/gtmengineering·September 2026·1 points
One person's experience and a precise description of how decay is actually experienced: not a gap you notice but a full record that is quietly about somebody's old job. Half is their estimate rather than a measurement. The practical response is the one in the checklist, which is to compare the returned employer against what you already hold, because that comparison catches exactly this and no coverage figure does.
The data enrichment problem is such a money pit. We were burning through different providers every quarter thinking the next one would magically stay fresh longer. Apollo, Zoominfo, Seamless... they all start strong then decay at basically the same rate. [...] My SDRs would find someone on LinkedIn who changed jobs 6 months ago but our CRM still showed them at the old company.
r/SalesOperations·December 2025·1 points
The comment that should temper this whole page, and it is the reason the recommendation here is a measurement rather than a provider. The same team's eventual fix was a last verified field maintained by hand, which is a worse version of reading metadata.updatedAt from the response and storing it. Decay is a property of the problem, so the thing to buy is a refresh schedule rather than a bigger database.
Some services can apply waterfall enrichment cross a set of providers, and automatically refresh the data on a regular schedule or when estimated accuracy falls below a threshold. In some cases (ie Clay) you'll pay per each enrichment update. On others [...] you pay over a period of time, like a year, and they keep it auto-refreshed which address your auto decay issue. [...] They also charge based on the enrichment meets a pre-defined rule or quality bar vs on every attempt
r/SalesOperations·December 2025·1 points
Somebody working out from first principles that these products have different meters, which is the argument of the grid above. The last clause is the sharpest: charging only when the result clears a quality bar rather than on every attempt is the same distinction as Find Email being billed only when an address is found. Pick the meter that matches how often you intend to re-enrich, because that decision outlasts any coverage comparison.
Nobody discusses this pair by name, because it is not a pair, so the search was for the job: deciding between enrichment providers and stacking them when one is not enough. This is the most opinionated harvest of the seven and the most useful, because people who pay for Apollo say what they get. One comment names the exact failure mode this directory's honesty rules exist to prevent, without knowing it was doing so.
Four of the five are about freshness rather than coverage, which is the finding and it is not what anybody searching for a comparison expects to read. The one to act on is the first, because it names the difference this directory is built around: a provider that answers "no number" is more useful than one that answers with a switchboard, and neither coverage figure tells you which you are buying.
A directory published by a data vendor and naming its competitors is either the most useful page on the site or the least credible, and the way to make it the first is to be specific about what each product is for. Apollo sells a searchable database of contacts bundled with sending, so its natural question is who else is out there. Reverse Contact sells resolution, so its natural question is who is this, from an email, a domain or a profile URL. Those are different questions and most teams have both.
The structural finding is that Apollo is already a waterfall. Its own documentation describes an admin-selected list of data sources queried in sequence, with a webhook for the results, which puts it in the same category as Gong's Enrich feature rather than in the category of a single provider. That matters for two reasons: the cost of a miss becomes a property of your configuration, and a second waterfall stacked on the first is often the thing that makes a build unaccountable.
So the recommendation on this page is a measurement rather than a product. Run both on 500 of your own rows, count the resolved rate and the bounce rate separately, and look at what each one does when it does not know. The Clay route is the cheapest place to do that because it runs on Clay credits and needs no Reverse Contact account, and the ZoomInfo comparison is the same exercise against a third meter again.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Apollo, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
No, and there is no reason there would be. These are two data providers rather than a tool and a data source, so nothing syncs between them. What people build instead is a waterfall: call one, and call the other for the rows that came back empty. This page is about that, including the comparison, because a page about two enrichment vendors that refused to compare them would be worthless.
Whichever one answers the question you are actually asking. Apollo searches a database to find people you did not know existed, which Reverse Contact's people search does too but is not mainly for. Reverse Contact resolves an identifier you already hold into a full record, which is a different job, and if your rows already carry an email or a profile URL then starting with a search is paying to find what you have.
Yes, and that is the most important thing on this page. Apollo documents run_waterfall_email and run_waterfall_phone parameters, an admin-selected list of data sources, and a required webhook_url, since phone results do not come back in the synchronous response. So Apollo is itself a waterfall orchestrator over partners you configure, which is the same shape as Gong Enrich rather than a single provider.
Reverse Contact publishes it: every 4xx and 5xx is 0 credits, Find Email and Find Phone are charged only when something is found, and a live fetch is the one exception because its 2 credits are kept whatever comes back. Apollo cannot publish a single answer for its waterfall, and says so: some configured sources charge only when they return data and others may charge for a lookup that finds nothing.
They do not, and saying so is more useful than a ratio. Apollo publishes 240M contacts and 30M companies; Reverse Contact publishes 800M+ profiles and 70M+ companies. A profile is a public professional identity and a contact is a record with contact details attached, so the two figures count different things and dividing one by the other produces a number that means nothing. Run 500 of your own rows through both instead.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.