Clay is incredible at enriching contacts you already know about. Feed it a name or domain, and it’ll waterfall through 150+ data providers to find emails, phones, firmographics, and more. That enrichment depth is why Clay hit $100M ARR in late 2025 (263% YoY growth) and earned a $3.1B valuation.
But here’s the gap nobody talks about: Clay can’t tell you WHO is visiting your website right now.
It enriches known contacts. It doesn’t identify unknown visitors. And since 97% of your website traffic is anonymous, Clay has nothing to enrich for the vast majority of your potential buyers.
That’s where the pipeline breaks.
The Gap in Every Clay Workflow
Clay’s enrichment waterfall is legitimately powerful. Give it a name, email, or company domain and it’ll cascade through Apollo, Lusha, Cognism, PeopleDataLabs, and dozens more providers until it finds verified contact data. Coverage rates hit 85-95% when you start with a solid input.
The catch? You need a starting point.
| What Clay Needs | Where It Comes From |
|---|---|
| A person’s name | You provide it |
| An email address | You provide it |
| A company domain | You provide it |
See the pattern? Clay is an enrichment engine, not an identification engine. It answers “tell me more about this person” - not “who is this person?”
Meanwhile, your website gets hundreds or thousands of visitors every day. Some of them are actively evaluating your product, visiting your pricing page, reading case studies. They’re in-market buyers showing real intent. And they leave without a trace.
The math is brutal: If you get 5,000 monthly visitors and 97% are anonymous, that’s 4,850 potential buyers Clay never sees. Your enrichment waterfall is doing nothing for them because it doesn’t know they exist.
Most teams try to solve this by importing lists - scraping LinkedIn, buying databases, uploading CSVs from events. But those contacts aren’t on your website right now. They haven’t shown intent. You’re enriching cold data and hoping for the best.
The fix isn’t replacing Clay. It’s adding a layer before it - one that captures the intent signals already happening on your site and feeds them directly into Clay’s waterfall.
Where Leadpipe Fits in the Clay Stack
Think of your data pipeline as a stack with distinct layers. Clay sits at the enrichment layer. But you need an identification layer underneath it - what we call “Layer 0.”
Anonymous Visitor → Leadpipe (identify) → Clay Webhook Table (enrich) → CRM (act)Here’s how each layer breaks down:
| Layer | Tool | What It Does | Output |
|---|---|---|---|
| 0 | Leadpipe | Identifies anonymous visitors | Name, email, company, LinkedIn, pages viewed |
| 1 | Clay | Enriches + validates contacts | Verified email, phone, firmographics, AI research |
| 2 | CRM / AI SDR | Triggers workflows | Sequences, tasks, deals, personalized outreach |
Leadpipe’s visitor identification uses a proprietary identity graph (not a resold third-party graph) to match anonymous visitors to real people - with 30-40% match rates and deterministic matching. That means when Leadpipe says “Jane Smith from Acme Corp visited your pricing page,” it’s not a guess.
Every identification includes person-level data: name, email (personal and professional), company, job title, LinkedIn URL, plus behavioral data like pages visited, visit duration, and return visit history.
That’s exactly the starting input Clay needs. And because Leadpipe identifies visitors even without LinkedIn profiles - matching via business email, phone, and firmographic data - you’re capturing a much wider net than tools like RB2B that only work when visitors have LinkedIn accounts.
The setup takes about 2-5 minutes on the Leadpipe side (a JavaScript pixel on your site), and the webhook connection to Clay adds another few minutes. No developer required.
If you’ve already read our full Leadpipe + Clay + HubSpot integration guide, this post goes deeper on one specific angle: using Leadpipe as an enrichment source within Clay’s waterfall architecture. Less about the end-to-end pipeline, more about the technical setup and credit optimization.
Step 1: Connect Leadpipe to Clay via Webhook
The connection between Leadpipe and Clay runs through webhooks. Every time Leadpipe identifies a visitor on your site, it fires a webhook with that visitor’s data to Clay’s webhook table.
In Leadpipe:
- Go to Settings —> Integrations —> Webhooks
- Click Add Webhook
- Set trigger to “First Match” (one identification per visitor - prevents duplicate sends)
- Paste your Clay webhook URL (we’ll get this in Step 2)
- Click Test to verify the connection
Leadpipe Webhook Payload
Here’s what Leadpipe sends with each identification:
| Field | Example | Clay Column |
|---|---|---|
email | jane@acme.com | |
first_name | Jane | First Name |
last_name | Smith | Last Name |
company_name | Acme Corp | Company |
company_domain | acme.com | Domain |
job_title | VP Marketing | Job Title |
linkedin_url | linkedin.com/in/janesmith | |
page_url | /pricing | Page Visited |
visit_duration | 180 | Visit Duration (sec) |
Why “First Match” matters: Without this trigger, Leadpipe would send data every time a visitor returns. That means duplicate rows in Clay, wasted credits, and messy CRM records. First Match ensures each visitor flows through the waterfall exactly once.
Step 2: Set Up Your Clay Webhook Table
Clay’s webhook tables are purpose-built for receiving data from external tools like Leadpipe. Setting one up takes about two minutes.
In Clay:
- Click New Table
- Select Import Data —> From Webhook
- Clay generates a unique webhook URL - copy it
- Paste this URL into Leadpipe (Step 1)
- Send a test event from Leadpipe
- Clay auto-detects the incoming fields - map them to columns
- Enable “Run enrichments on new rows” to trigger your waterfall automatically
Column Mapping
Once Clay receives the test payload, map each field:
| Incoming Field | Clay Column | Type |
|---|---|---|
| Text | ||
| first_name | First Name | Text |
| last_name | Last Name | Text |
| company_name | Company | Text |
| company_domain | Domain | Text |
| job_title | Job Title | Text |
| linkedin_url | LinkedIn URL | Text |
| page_url | Page Visited | Text |
| visit_duration | Visit Duration | Number |
With this in place, every new Leadpipe identification automatically creates a row in Clay, ready for enrichment. No manual imports, no CSV uploads, no lag time between a visitor hitting your site and their data appearing in Clay.
One thing worth noting: Clay’s webhook tables can handle high volume without issues. Even if you’re identifying hundreds of visitors per day through Leadpipe, the table ingests them in real time and queues enrichments accordingly. You won’t hit bottlenecks on the intake side - the constraint is always Clay credits on the enrichment side.
Step 3: Build Your Enrichment Waterfall
This is where Clay earns its keep. Even though Leadpipe provides solid contact data, Clay can validate, extend, and enrich it further. The goal is to take each identified visitor and build a complete lead profile.
Here’s a recommended waterfall setup with credit costs:
Column 1: Email Validation (~2 credits)
Not every email needs enrichment. Validate first, enrich second.
- Provider: ZeroBounce or NeverBounce
- Input: Email column
- Output: valid / invalid / catch-all
- Action: Only continue waterfall for valid emails
Column 2: Phone Number (~6 credits)
Use a waterfall of phone providers for maximum coverage:
- Provider 1: Apollo
- Provider 2: Lusha (fallback)
- Provider 3: PeopleDataLabs (fallback)
- Input: Email + Company Domain
- Output: Direct phone number
Column 3: Company Research via Claygent (~10 credits)
Clay’s AI agent researches the company and produces a structured summary:
- Prompt: “Research {company_name} ({company_domain}). Summarize: 1) What they do, 2) Company size and funding stage, 3) Recent news, 4) Key challenges they likely face. Keep it under 100 words.”
- Output: Personalized research for sales outreach
Column 4: LinkedIn Profile Enrichment (~3 credits)
- Provider: LinkedIn enrichment via Proxycurl or similar
- Input: LinkedIn URL from Leadpipe
- Output: Headline, connections, recent activity, mutual connections
Total Credit Cost Per Lead
| Enrichment Step | Credits |
|---|---|
| Email validation | ~2 |
| Phone waterfall | ~6 |
| Claygent research | ~10 |
| LinkedIn enrichment | ~3 |
| Total per lead | ~21 |
What That Means for Your Clay Plan
| Clay Plan | Monthly Price | Credits | Fully Enriched Leads/Month |
|---|---|---|---|
| Free | $0 | 100 | ~4 |
| Launch | $185/mo | 2,500 | ~119 |
| Growth | $495/mo | 6,000 | ~285 |
| Enterprise | $30K-154K/yr | Custom | Custom |
Credit-saving tip: You don’t need to run every enrichment on every lead. Filter by intent first (Step 4), then only waterfall the high-value visitors. This can 2-3x your effective leads per credit.
Step 4: Qualify and Score
Raw volume isn’t the goal - qualified volume is. Use Clay’s formula columns to filter and score before anything hits your CRM.
Disqualification Formula
IF(
OR(
CONTAINS(job_title, "student"),
CONTAINS(job_title, "intern"),
employee_count < 10,
CONTAINS(email, "gmail.com"),
CONTAINS(email, "yahoo.com"),
CONTAINS(email, "hotmail.com")
),
TRUE,
FALSE
)Any row where Disqualified = TRUE gets skipped. No credits wasted on enrichment, no junk in your CRM.
ICP Scoring Formula
| Criteria | Points |
|---|---|
| Job title contains “VP”, “Director”, “Head”, “C-level” | +20 |
| Visited /pricing or /demo page | +25 |
| Company size 50-500 employees | +15 |
| Company size 500+ employees | +10 |
| Visited case studies | +10 |
| B2B SaaS industry | +10 |
| Visit duration > 120 seconds | +5 |
| Personal email domain | -50 |
Set your export threshold at ICP Score >= 30. Only leads that clear this bar flow downstream.
This scoring approach mirrors what we cover in our guide on converting website visitors into qualified leads - but automated inside Clay instead of manually.
Step 5: Export to Your CRM or AI SDR
Once leads are enriched, validated, and scored, push them to wherever your team takes action.
Export Options
| Destination | Use Case | Setup |
|---|---|---|
| HubSpot | Full CRM automation | Clay native integration |
| Salesforce | Enterprise CRM | Clay native integration |
| AI SDR (11x, Artisan, etc.) | Automated outbound | Webhook or API |
| Slack | Real-time team alerts | Clay native integration |
| Google Sheets | Simple tracking | Clay native integration |
HubSpot Export (Most Common)
Map Clay columns to HubSpot properties:
- Email —> Email
- First Name / Last Name —> Contact name
- Company —> Company name
- Phone —> Phone number
- ICP Score —> Lead Score (custom property)
- Page Visited —> Original Source Drill-Down (custom)
- Claygent Summary —> Notes
Enable “Run on new rows” so every qualified lead automatically flows into HubSpot and triggers your workflows.
For the full HubSpot workflow setup (sequences, tasks, Slack alerts), see our complete Leadpipe + Clay + HubSpot guide.
AI SDR Export
If you’re running an AI SDR stack, Clay can push enriched leads directly via webhook. The Claygent research summary gives your AI SDR the context it needs to write personalized first lines - without burning additional research credits on the SDR side.
This is the stack architecture that AI SDR platforms are missing: most AI SDRs start with a static list or a database query, not real-time website intent. By feeding Leadpipe-identified, Clay-enriched leads directly into your AI SDR, you’re giving it prospects who were on your website minutes ago - with full context on what they viewed and researched company intel to personalize outreach.
Salesforce Export
For Salesforce teams, map Clay columns to Lead or Contact objects. The process is nearly identical to HubSpot. Clay’s native Salesforce integration supports field mapping, deduplication by email, and automatic record creation. Pair it with Salesforce Flow for post-creation automation like task assignment or sequence enrollment.
Try Leadpipe free with 500 leads —>
Leadpipe + Clay vs. Traditional Enrichment
Here’s how this stack compares to other approaches:
| Approach | Identifies Anonymous? | Enrichment Depth | Monthly Cost | Leads/Month |
|---|---|---|---|---|
| Leadpipe + Clay | Yes (30-40%) | 150+ providers | $484/mo | 500-1,500 |
| Clay alone | No | 150+ providers | $185-495/mo | 0 (needs input) |
| Apollo alone | No | Single database | $49/mo | Outbound only |
| ZoomInfo + Clay | No | Combined | $1,400+/mo | Outbound only |
| Leadpipe + CRM only | Yes | Basic | $299/mo | 500-1,500 |
| Warmly | Partial | Limited | $900+/mo | Lower match rate |
Key insight: Leadpipe + Clay is the only combination that takes you from anonymous website traffic to fully enriched, qualified leads - automatically. Every other approach either can’t identify visitors or can’t deeply enrich them. This stack does both.
The cost of ignoring anonymous traffic compounds every month. Each visitor who leaves unidentified is a potential deal your competitors might capture first.
Worth highlighting: “Leadpipe + CRM only” (the last row) still delivers solid results if you don’t need deep enrichment. Leadpipe’s native integrations push directly to HubSpot, Salesforce, or Pipedrive with the data it identifies - no Clay required. But if you want validated phone numbers, AI-generated company research, and multi-provider enrichment on every lead, Clay is the multiplier that takes basic identification data and turns it into a fully actionable lead profile.
Credit Math: The Full Cost Breakdown
Let’s get specific about what this pipeline costs end-to-end.
| Component | Plan | Monthly Cost | What You Get |
|---|---|---|---|
| Leadpipe | Growth | $299/mo | ~1,500 identified visitors |
| Clay | Launch | $185/mo | 2,500 credits (~119 fully enriched leads) |
| Total | $484/mo | Automated anonymous-to-enriched pipeline |
Cost Per Lead
- Fully enriched lead (all 4 waterfall steps): $2.70-4.00
- Basic enriched lead (email validation + phone only): $1.50-2.50
Comparison
| Solution | Monthly Cost | Identified + Enriched Leads |
|---|---|---|
| Leadpipe + Clay | $484 | 119-285 |
| Warmly | $900+ | Fewer (lower match rate) |
| ZoomInfo + Clay | $1,400+ | 0 from website (outbound only) |
| 6sense | $2,500+ | Company-level only |
At these price points, you’re paying roughly the same as one mid-market SDR’s monthly software stack - but generating pipeline 24/7 without manual prospecting. The ROI math gets compelling fast: if your average deal size is $10K+ and this stack produces even 2-3 closed deals per quarter, you’re looking at 5-10x return on investment.
Want to go deeper on the numbers? Check our visitor identification pricing comparison.
Pro Tips for Maximizing This Stack
1. Filter High-Intent Pages Only
Don’t waste Clay credits on blog-only visitors. In Leadpipe, use excluded paths to skip low-intent pages:
- Include: /pricing, /demo, /case-studies, /product, /features
- Exclude: /blog, /careers, /about, /legal
This alone can cut your Clay credit consumption by 50-70% while keeping lead quality high.
2. Gate Enrichment Behind Validation
Set Clay to run the phone/Claygent waterfall only on rows where email validation = “valid.” No point spending 19 credits enriching a bounce.
3. Use Claygent for Personalized First Lines
Add a second Claygent column with this prompt:
Based on {first_name}'s role as {job_title} at {company_name},
and the fact they visited {page_url} on our website, write a
personalized one-line email opener. Be specific and non-generic.
No buzzwords.This gives your sales team (or AI SDR) a ready-to-use first line for every lead.
4. Set Up Slack Alerts for Hot Leads
Add a Clay Slack integration that fires when a lead scores above 50:
Hot Lead Alert
Jane Smith (VP Marketing) from Acme Corp
Visited: /pricing (180 seconds)
ICP Score: 65
Phone: (555) 123-4567
LinkedIn: linkedin.com/in/janesmith
Claygent: Acme Corp is a 200-person Series B SaaS company
that recently raised $30M. Likely evaluating new tools
for their growing sales team.5. Build Lookalike Audiences
Export your highest-converting Leadpipe visitors from Clay to CSV, then upload to LinkedIn or Meta for lookalike targeting. You’re building audiences based on people who actually showed buying intent - not just demographic guesses.
6. Run Different Waterfalls by Intent Level
Not every visitor deserves the same enrichment spend. Create multiple Clay tables or use conditional enrichments:
| Visitor Type | Pages Viewed | Waterfall Depth | Credits Used |
|---|---|---|---|
| Hot (pricing, demo) | /pricing, /demo, /contact | Full waterfall (4 steps) | ~21 |
| Warm (product, case studies) | /product, /case-studies, /features | Email validation + phone | ~8 |
| Cool (blog only) | /blog/* | Skip enrichment | 0 |
This tiered approach can stretch your Clay credits 3-4x further while ensuring hot leads get the deepest enrichment.
FAQ
Does Leadpipe send data to Clay in real time?
Yes. Leadpipe’s webhook fires within seconds of identifying a visitor. The data lands in Clay’s webhook table immediately, and if you’ve enabled “Run enrichments on new rows,” the waterfall kicks off automatically.
Will this create duplicate contacts?
Not if you configure it correctly. Set Leadpipe’s webhook trigger to “First Match” (one send per visitor). On the Clay side, use email as the deduplication key when exporting to your CRM.
How many Clay credits does this actually use?
It depends on your waterfall depth. A basic setup (email validation + phone) runs about 8 credits per lead. The full waterfall we outlined above (validation + phone + Claygent + LinkedIn) is ~21 credits. You control exactly which enrichments run, so you can dial the cost up or down.
Can I use this without HubSpot?
Absolutely. Clay exports to Salesforce, Pipedrive, Google Sheets, Slack, and any tool that accepts webhooks. The Leadpipe-to-Clay portion works the same regardless of your CRM. For a broader look at how visitor identification integrates with different tools, see our Visitor Identification API guide.
What if Leadpipe already provides an email - why validate it in Clay?
Belt and suspenders. Leadpipe’s emails are high quality (deterministic matching from a proprietary identity graph), but running a quick validation in Clay costs only ~2 credits and ensures you’re never sending to a dead address. If you’re on a tight credit budget, you can skip this step - but if your outbound reputation matters (and it should), the extra validation prevents hard bounces that hurt deliverability scores.
Is this CCPA/GDPR compliant?
Leadpipe is CCPA compliant and provides company-level only data for EU visitors under GDPR. On the Clay side, you’re enriching with publicly available business data. That said, always include an unsubscribe mechanism in any outbound sequences and honor opt-out requests promptly. If compliance is a priority for your team, review how visitor identification tools handle data privacy for a broader overview of the landscape.
Start Building Your Waterfall
Here’s the bottom line: Clay is one of the best enrichment tools on the market. But enrichment without identification is like having a race car with no fuel. You need visitors flowing into the top of the funnel before Clay can work its magic.
Leadpipe fills that gap. It identifies the anonymous visitors Clay can’t see, feeds them into your webhook table automatically, and gives Clay everything it needs to enrich, validate, and score each lead.
The setup takes 30 minutes. The pipeline runs forever.
- Start your free Leadpipe trial - 500 identified leads, no credit card
- Connect the webhook to Clay
- Build your enrichment waterfall
- Watch enriched, qualified leads flow into your CRM on autopilot
Every day you wait, your anonymous traffic costs you pipeline. Your competitors’ visitors are getting identified and contacted. Yours should be too.
Start identifying your visitors for free —>
Related Articles
- How to Use Leadpipe with Clay + HubSpot (Complete Integration Guide)
- Best Contact Enrichment APIs in 2026
- Waterfall Enrichment + Visitor Identity: The Complete Stack
- Visitor Identification API: Complete Developer Guide
- The Data Layer AI Sales Agents Are Missing
- Website Visitor Identification Pricing Comparison
- How to Easily Identify Anonymous Website Visitors
