---
title: "Clay Waterfall Enrichment: Step-by-Step Setup (2026)"
description: "Set up Clay waterfall enrichment step by step: provider order, costs, and the exact config we use to push verified-email match rates past 90%."
---
[](https://www.genflows.com/)
[Case Studies](https://www.genflows.com/#case-studies) [Deliverables](https://www.genflows.com/#deliverables) [Process](https://www.genflows.com/#process) [Team](https://www.genflows.com/#team) [FAQ](https://www.genflows.com/#faq)
[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)
[Home](https://www.genflows.com/) / [Blog](https://www.genflows.com/blog)
[Clay & GTM Engineering](https://www.genflows.com/blog/tag/clay-gtm-engineering)
# How to Set Up Clay Waterfall Enrichment (Step-by-Step Guide for 2026)
GenFlows Team · Jun 29, 2026, 9:25:15 PM · 6 min read
**TL;DR**
- **Waterfall enrichment** queries data providers in sequence and stops at the first valid result — so you pay once per contact instead of once per provider.
- A single provider rarely clears **60–70% coverage**; a well-ordered 4–5 provider waterfall routinely pushes verified emails past **90%**.
- Order providers by **cost-to-accuracy**, not brand name: cheap-but-accurate first, premium fallbacks last.
- Always end the waterfall with an **email verification** step before anything reaches your sequencer.
- This guide gives you the exact column-by-column build, a recommended provider order, and the mistakes that quietly burn your credits.
If you have spent any time inside [Clay](https://www.genflows.com/blog/clay-workflow-automation-gtm-engineering-playbook), you already know the platform's real superpower is not scraping — it is **waterfall enrichment**. Yet most teams set it up wrong: they bolt on one provider, watch a third of their list come back blank, and conclude "the data is bad." The data is fine. The *routing* is the problem.
At GenFlows we run waterfall enrichment on every outbound list we touch for e-commerce and B2B clients. This is the exact, repeatable build we use — written for the GTM engineer who wants verified emails, not a vendor pitch. By the end you will have a working waterfall, a sane provider order, and a verification step that keeps junk out of your [sending infrastructure](https://www.genflows.com/blog/cold-email-infrastructure-deliverability).
## What Is Clay Waterfall Enrichment, Really?
A "waterfall" runs your enrichment providers **in sequence** rather than all at once. Clay asks provider #1 for the email. If it returns a valid result, the waterfall *stops* and moves to the next contact. If provider #1 comes back empty, Clay "falls" down to provider #2, then #3, and so on until something hits or the list is exhausted.
The economic difference is the whole point. Querying five providers in parallel means paying five times for every contact. A waterfall means you pay for provider #1 on the contacts it finds, and only spend on provider #2 for the contacts that *failed* #1. Same coverage, a fraction of the cost.
## Why Does Single-Provider Enrichment Keep Failing?
No data vendor has complete coverage. Each one is strong in different regions, company sizes, and seniority bands. ZoomInfo skews to enterprise North America; some EU-friendly providers win on GDPR-era records; mobile-focused vendors win on direct dials. Bet everything on one and you inherit that one vendor's blind spots.
| Approach | Typical verified-email coverage | Relative cost / contact |
| --- | --- | --- |
| Single provider | 55–70% | 1× |
| All providers in parallel | 88–95% | 4–5× |
| **Waterfall (ordered)** | **88–95%** | **~1.3–1.6×** |
That last row is why waterfall exists: near-parallel coverage at near-single-provider cost.
## How to Set Up Clay Waterfall Enrichment, Step by Step
### Step 1 — Start with a clean people table
Import or scrape your target contacts into a Clay table. At minimum you want `Full Name`, `Company Domain`, and ideally `LinkedIn URL`. Domain quality matters most — a missing or wrong domain is the single biggest cause of "no match." Normalize domains (strip `www`, `http`) before enriching.
### Step 2 — Add your first enrichment column
Add a column → choose your **cheapest accurate provider** as the "Find Work Email" source. Map its inputs to your name and domain columns. Run it on a 25-row test slice first — never the full list. Note the hit rate.
### Step 3 — Add the fallback column with a run condition
Add a second "Find Work Email" column from a different provider. In its settings, set the **run condition** to only fire when the first column is empty (e.g. `Provider 1 Email is empty`). This is the mechanic that turns two columns into a waterfall — provider #2 only spends credits on the misses.
### Step 4 — Stack 2–3 more fallbacks
Repeat Step 3 for each additional provider, each gated on "all previous columns empty." Three to five total is the sweet spot; beyond that you are paying premium credits to chase a few percent.
### Step 5 — Consolidate into one "Final Email" column
Add a formula column that coalesces the results: return the first non-empty email across your provider columns. Now you have one clean field to work with regardless of which provider found it.
### Step 6 — Verify before you trust
Add an **email verification** column (e.g. a verifier provider) on top of `Final Email`. Keep only `valid` / `deliverable` results. This single step protects your sender reputation more than any other — catch-alls and risky addresses never reach your sequencer.
### Step 7 — Export only verified rows
Filter to `verification = valid`, then push to your CRM or sequencer via Clay's native integrations or a webhook. If you automate that hand-off, see our companion guide on [connecting Clay to n8n](https://www.genflows.com/blog/clay-n8n-integration-automate-gtm-workflow-2026).
## What Order Should the Providers Go In?
Order by **cost-to-accuracy**, not reputation. A practical default we use as a starting point (then tune against your own hit rates):
| Tier | Role in the waterfall | Why here |
| --- | --- | --- |
| 1 | Cheap, high-volume provider | Clears the easy 55–65% at lowest cost |
| 2 | Region/industry specialist | Fills gaps the generalist misses |
| 3 | Premium accuracy provider | Expensive, so only runs on the hard remainder |
| 4 | Email verifier | Quality gate before export |
Re-order after your first 500 contacts. Whichever provider has the best hit rate *on your ICP* earns the top slot — this is data-specific, so let your numbers decide.
## Common Mistakes That Burn Credits
- **No run conditions.** Without them, every provider fires on every row and you have built an expensive parallel lookup, not a waterfall.
- **Running on the full list first.** Always test on 25 rows, confirm mappings, then scale.
- **Skipping verification.** Unverified emails tank deliverability — see our [deliverability guide](https://www.genflows.com/blog/cold-email-deliverability-in-2025-how-gtm-engineers-avoid-spam-filters-and-land-in-inbox).
- **Dirty domains.** Normalize and validate company domains before enriching; it is the #1 fixable cause of low match rates.
- **Too many tiers.** Five providers is plenty. The sixth rarely pays for itself.
## Frequently Asked Questions
### How many providers should a Clay waterfall have?
Three to five. Two providers already lift coverage meaningfully; four to five is the point of diminishing returns for most B2B and e-commerce lists.
### Does waterfall enrichment use more Clay credits?
Each enrichment provider has its own credit cost, but run conditions ensure later providers only spend on earlier misses — so total spend is far lower than running providers in parallel for the same coverage.
### What match rate is "good"?
For a clean, well-targeted list, 88–95% verified work emails is achievable. If you are under 75%, the problem is almost always domain quality or provider order, not Clay itself.
### Can I waterfall phone numbers too?
Yes — the same pattern works for mobile/direct dials. Use dial-specialist providers and gate each on the previous column being empty.
---
**Want this built for you?** GenFlows runs waterfall enrichment, verification, and sequencing as a managed outbound system. [See how the major data providers compare](https://www.genflows.com/blog/clay-vs-apollo-vs-zoominfo-outbound-comparison-2026), or [talk to our team](https://www.genflows.com/) about a done-for-you build.
*By the GenFlows GTM engineering team. Last updated June 2026.*
[#Clay & GTM Engineering](https://www.genflows.com/blog/tag/clay-gtm-engineering)
Share [in](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fclay-waterfall-enrichment-setup-step-by-step-2026) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fclay-waterfall-enrichment-setup-step-by-step-2026&text=%3Cspan+id%3D%22hs_cos_wrapper_name%22+class%3D%22hs_cos_wrapper+hs_cos_wrapper_meta_field+hs_cos_wrapper_type_text%22+style%3D%22%22+data-hs-cos-general-type%3D%22meta_field%22+data-hs-cos-type%3D%22text%22+%3EHow+to+Set+Up+Clay+Waterfall+Enrichment+%28Step-by-Step+Guide+for+2026%29%3C%2Fspan%3E)
↗
Written by
GenFlows Team
The GenFlows team builds AI-powered cold outbound systems for B2B teams.
On this page
## Keep reading
### [Outbound Systems Close CRM Power Dialer: Plans, Setup & Limits Oct 8, 2026, 11:54:26 AM Read →](https://www.genflows.com/blog/close-crm-power-dialer-outbound-calling-2026)
### [Outbound Systems Close CRM Reporting for Outbound: Reports & Metrics Oct 8, 2026, 11:50:47 AM Read →](https://www.genflows.com/blog/close-crm-reporting-outbound-2026)
### [Outbound Systems Close CRM Smart Views for Outbound: Filters & Recipes Oct 7, 2026, 12:50:20 PM Read →](https://www.genflows.com/blog/close-crm-smart-views-outbound-2026)
## Ready to fill your calendar?
We build AI-powered cold outbound engines that book meetings on autopilot. Let's see if it fits your team.
[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)
Precision-engineered outbound systems for B2B companies.
[](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [](https://www.smartlead.ai/partner/wouter-harink)
Explore
- [How it works](https://www.genflows.com/#process)
- [Results](https://www.genflows.com/#results)
- [Revenue calculator](https://www.genflows.com/#calculator)
- [About](https://www.genflows.com/#founder)
Reach us
- [info@genflowsagency.com](mailto:info@genflowsagency.com)
- [Book a call](https://app.iclosed.io/e/genflows/discovery-genflows)
- [LinkedIn](https://www.linkedin.com/company/genflows-agency/)
© 2026 GenFlows Agency. All rights reserved.
[Privacy](https://www.genflows.com/privacy) [Terms](https://www.genflows.com/terms) v1.0
```json
{
"@context" : "https://schema.org",
"@type" : "BlogPosting",
"author" : {
"@type" : "Person",
"name" : "GenFlows Team"
},
"dateModified" : "2026-07-22T17:08:29Z",
"datePublished" : "2026-06-29T19:25:15Z",
"description" : "Set up Clay waterfall enrichment step by step: provider order, costs, and the exact config we use to push verified-email match rates past 90%.",
"headline" : "How to Set Up Clay Waterfall Enrichment (Step-by-Step Guide for 2026)",
"image" : [ "" ],
"keywords" : "Clay & GTM Engineering",
"mainEntityOfPage" : {
"@id" : "https://www.genflows.com/blog/clay-waterfall-enrichment-setup-step-by-step-2026",
"@type" : "WebPage"
},
"publisher" : {
"@type" : "Organization",
"logo" : {
"@type" : "ImageObject",
"url" : ""
},
"name" : "GenFlows"
},
"wordCount" : 1164
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "BreadcrumbList",
"itemListElement" : [ {
"@type" : "ListItem",
"item" : "https://www.genflows.com/",
"name" : "Home",
"position" : 1
}, {
"@type" : "ListItem",
"item" : "https://www.genflows.com/blog",
"name" : "Blog",
"position" : 2
}, {
"@type" : "ListItem",
"name" : "How to Set Up Clay Waterfall Enrichment (Step-by-Step Guide for 2026)",
"position" : 3
} ]
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "BlogPosting",
"author" : {
"@type" : "Person",
"name" : "GenFlows Team",
"url" : "https://www.genflows.com/blog/author/genflows-team"
},
"datePublished" : "2026-06-29T19:25:15.000Z",
"headline" : "Clay Waterfall Enrichment: Step-by-Step Setup (2026)",
"mainEntityOfPage" : {
"@id" : "https://www.genflows.com/blog/clay-waterfall-enrichment-setup-step-by-step-2026",
"@type" : "WebPage"
},
"publisher" : {
"@type" : "Organization",
"logo" : {
"@type" : "ImageObject"
}
}
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "FAQPage",
"mainEntity" : [ {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Three to five. Two providers already lift coverage meaningfully; four to five is the point of diminishing returns for most B2B and e-commerce lists."
},
"name" : "How many providers should a Clay waterfall have?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Each enrichment provider has its own credit cost, but run conditions ensure later providers only spend on earlier misses — so total spend is far lower than running providers in parallel for the same coverage."
},
"name" : "Does waterfall enrichment use more Clay credits?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "For a clean, well-targeted list, 88–95% verified work emails is achievable. If you are under 75%, the problem is almost always domain quality or provider order, not Clay itself."
},
"name" : "What match rate is \"good\"?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Yes — the same pattern works for mobile/direct dials. Use dial-specialist providers and gate each on the previous column being empty. Want this built for you? GenFlows runs waterfall enrichment, verification, and sequencing as a managed outbound system. See how the major data providers compare, or talk to our team about a done-for-you build. By the GenFlows GTM engineering team. Last updated June 2026."
},
"name" : "Can I waterfall phone numbers too?"
} ]
}
```