Waterfall enrichment is a way of finding a data point, such as a work email or phone number, by checking several data providers one after another and stopping when one returns a usable result. Instead of paying every provider to look up every contact, you ask the first provider, move to the next only if it comes up empty or fails validation, and stop as soon as you have an answer you trust. In Clay, Waterfalls are built into the enrichment menu, and you control the provider order, the validation rules and when the waterfall stops.
The idea is simple. The value comes from the setup: which providers you include, in what order, what counts as a good result and when it is not worth running a waterfall at all.
How does a waterfall run in Clay?
Clay calls providers one at a time in the order you set and stops when one returns a valid result.
Clay describes waterfalls as a way to use multiple data providers in a predetermined sequence so you don't duplicate tasks or spend extra credits. You can run a pre-built waterfall for a data point, such as a phone number or work email, or create your own.
A Clay waterfall has three parts:
| Part | What it controls | Clay setting |
|---|---|---|
| Providers | Which data sources are checked | Reorder, add or delete providers, or toggle a step off to skip it |
| Order | The sequence of calls; each step runs only if earlier steps found nothing | The provider order you set in the waterfall |
| Stop conditions | When a result is good enough | Validation settings |
For the Work Email waterfall, Clay stops as soon as one provider returns a valid result, based on the validation settings you choose.
Clay also lets you output the name of the provider that succeeded and hide the per-provider columns for a cleaner table. Turn the provider name on. It is the column you will use later to judge whether the order is working.
You can set run conditions as well, such as only running the waterfall when the email column is empty. That one rule prevents you from paying again for contacts you have already enriched. Once a configuration works, Clay lets you save it as a waterfall template so the team reuses it instead of rebuilding it.
How should you order waterfall providers?
Provider order is a trade-off between three things:
- Coverage: how often a provider returns anything for your type of contact.
- Cost: how many credits a lookup uses.
- Accuracy: how often what it returns is actually right.
No order is best for every list. A provider that does well on US software companies may do poorly on European manufacturers or small local businesses. That is why the order should come from your own data, not from a vendor's marketing claims.
A practical way to decide:
- Pull a sample of contacts that represents your real target list.
- Run each candidate provider on the sample separately.
- Compare how often each returns a result and how often that result validates.
- Put providers that are both accurate and cheaper for your segment first, and more expensive or broader providers later.
- Re-check the order periodically, since provider coverage changes over time.
For work emails, Clay also offers an Infer Email step that builds an address from a name and company domain using a common pattern before any paid provider is called. If the guess passes validation, the waterfall stops there. Clay recommends testing patterns on a small sample before running at scale.
How do you validate waterfall results?
Turn on validation so the waterfall only stops on a result that passes your settings, not on the first value it finds.
A waterfall that stops on the first result, without checking it, can fill your table with addresses that bounce. Validation is what makes the stop rule trustworthy.
In Clay's Work Email waterfall, validation settings include:
- Validation provider: when set, a validation step runs after each provider step.
- Require validation success: when on, the waterfall only accepts an email the validator explicitly confirms. When off, it may accept inconclusive results.
- Validation strategy: Conservative, Balanced, Aggressive or Advanced. Clay describes Conservative as best when deliverability matters, such as cold outreach where bounce rates affect sender reputation. Balanced includes catch-all addresses.
- Threshold for duplicate results: stops the waterfall early if the same email keeps failing validation across providers, so you don't keep spending credits on the same rejected result.
Validation inside the waterfall is only one layer. Add your own QA:
- Sample manually. Before sending, spot-check a handful of enriched rows. Does the person still work there? Does the title match?
- Watch bounces. Track bounce rates by the provider that supplied the email. If one provider's emails bounce more, move it down the order or remove it.
- Separate catch-alls. Treat catch-all addresses as a separate group with its own sending rules rather than mixing them into your main sequence.
Clean data also matters after enrichment. Our upcoming post on HubSpot data hygiene covers keeping enriched records accurate once they reach the CRM.
How do you control credit costs in a waterfall?
Use run conditions so rows that already have data are skipped, and test a new waterfall on a small sample first.
Waterfalls save credits compared with calling every provider for every row, but they can still burn credits quickly if left unchecked. Clay says that with the Work Email waterfall you only pay credits for the provider that finds a match, and that validation steps cost credits but are cheaper than running the waterfall without them.
Ways to keep spend in check:
- Filter the list first. Only enrich contacts who fit your ideal customer profile. Enriching people you will never email is the most common waste.
- Use run conditions. Only run the waterfall when the field is empty.
- Put cheaper, reliable providers first for your segment.
- Use the duplicate-result threshold when Conservative validation keeps rejecting the same address.
- Enrich phones only when you will call. Apollo notes that phone data typically costs more per provider than email, so don't run phone lookups on contacts who will only get email.
If you need account-level research rather than a single data point, Claygent handles that, and we cover it in a later post on Claygent for account research.
When isn't a waterfall worth it?
Waterfalls are not always the right tool. Skip one, or keep it short, when:
- The list is small and high-value. For a short list of strategic accounts, a person researching each contact may beat automation. Our comparison of Clay vs. manual research covers where each wins.
- One provider already covers your segment well. If a single source returns accurate data for most of your list, extra steps add cost and complexity for little gain.
- You lack the volume to justify setup. Building, testing and maintaining a waterfall takes time. A team sending a small number of emails a month may not get the time back.
- Your data problem is upstream. If your targeting is wrong, better emails just mean you reach the wrong people faster. Fix the account list first.
When a waterfall does make sense, it usually sits inside a larger system: account selection, signals, enrichment, sequencing and CRM sync. Our post on Clay outbound workflows shows how enrichment fits into that system, and our explanation of what GTM engineering is covers the wider approach. The upcoming Clay and HubSpot integration post covers getting enriched data into the CRM.
Getting help
If you want a waterfall built and tested on your own target list, our Clay consulting work covers enrichment, validation and the connections into sequencing and your CRM. For the broader system, see our GTM engineering service.
Frequently Asked Questions
What is waterfall enrichment?
Waterfall enrichment checks several data providers in sequence for a data point, such as a work email or phone number, and stops when one returns a usable result. It aims to improve coverage without paying every provider for every contact.
What are the best waterfall enrichment tools?
Clay and Apollo both offer waterfall enrichment, and several data vendors offer their own versions. The best choice depends on your workflow. Clay gives you control over provider order, validation and run conditions inside a table. Apollo runs a waterfall within its own platform. Whatever you choose, test providers on your own target list rather than relying on vendor claims.
What is waterfall enrichment on Apollo?
In Apollo, waterfall enrichment checks Apollo's own data first, then moves through the third-party sources your admin has connected, in the order you define. If a validator is connected, it runs after each source. Apollo says the run continues until a validated result is found or every source has been tried, and that each source that returns data charges credits.
Is waterfall enrichment worth it?
It is worth it when you enrich contacts at volume, no single provider covers your segment well and you validate results before sending. It is less useful for small, high-value account lists, for segments one provider already covers, or when the real problem is targeting.
