You have access to an identity resolution API. You can resolve anonymous website visitors to real people - name, email, phone, company, job title, intent data. Over 100 data points per person.
Now what?
Most teams stop at the obvious use case: pipe identified visitors into the CRM and let sales follow up. That’s fine. It works. But it’s like buying a Swiss Army knife and only using the bottle opener.
Here are seven things teams are actually building with identity resolution APIs - from weekend projects to production platforms generating real revenue. Each includes the architecture, the cost, and enough detail to start building today.
Use Case 1: AI Sales Agent
What it is: An automated pipeline that identifies website visitors, classifies their intent, generates personalized outreach with AI, and sends emails - without human intervention.
Why it matters: AI SDR platforms charge $900-10,000/month. You can build the same thing for $167.
Architecture
Website Visitor
↓
Leadpipe Pixel (identify)
↓
Webhook → Your Server
↓
Intent Classifier (rules-based)
↓
ICP Qualifier (firmographic filters)
↓
OpenAI GPT-4 (personalize email)
↓
Email Sender (Resend / SMTP)
↓
CRM Logger + Slack AlertHow It Works
- A visitor lands on your pricing page. Leadpipe’s pixel resolves the anonymous session into a person with 100+ data points - including contact details, demographics, social profiles, HEMs, company firmographics, and intent signals.
- Your webhook receives the identity payload in real time.
- A rules engine classifies intent based on pages visited, time on site, and intent topics from Leadpipe’s 20,735-topic taxonomy.
- If the visitor matches your ICP (right title, right company size, right industry), they pass to the next step.
- OpenAI drafts a personalized 3-sentence email referencing what the visitor was researching - without sounding like you’re watching them.
- The email sends automatically. The outreach logs to your CRM. Your sales rep gets a Slack ping.
Cost Breakdown
| Component | Monthly Cost |
|---|---|
| Leadpipe Starter | $147 |
| OpenAI GPT-4 API | ~$20 |
| Resend (email) | Free tier |
| Server (Railway/Fly) | ~$5 |
| Total | ~$167/mo |
Compare that to 11x ($5,000-10,000/mo), Artisan ($2,400/mo), or AiSDR ($900/mo).
Full tutorial with working code: Build a Custom AI SDR with Leadpipe + OpenAI
Use Case 2: White-Label Visitor ID Platform
What it is: A platform where agencies or SaaS companies offer visitor identification to their own clients, powered by Leadpipe’s API behind the scenes.
Why it matters: Visitor identification is one of the highest-demand features agencies get asked about. Instead of reselling someone else’s tool (and losing the margin), you can white-label it as your own.
Architecture
Agency Dashboard (your product)
↓
Pixel Management (Leadpipe API)
├── Client A → Pixel A → Webhook A
├── Client B → Pixel B → Webhook B
└── Client C → Pixel C → Webhook C
↓
Identity Data → Your Database
↓
Client-Facing Dashboard (branded as yours)How It Works
- You create a tracking pixel for each client using Leadpipe’s pixel management endpoints (
POST /v1/data/pixels). - Each pixel is installed on the client’s website.
- Webhooks route identified visitor data to your server, tagged by client/pixel.
- Your platform stores the data and presents it through a branded dashboard.
- Clients see “powered by [YourBrand]” - not Leadpipe.
Revenue Model
| Item | Cost/Revenue |
|---|---|
| Leadpipe (your cost) | $1,279/mo (agency plan) |
| Your price per client | $500-3,000/mo |
| 10 clients at $1,000/mo | $10,000/mo revenue |
| Net margin | $8,721/mo |
You’re arbitraging the difference between API-level pricing and SaaS-level pricing. Your clients pay for the convenience, the dashboard, and the support. You pay for the data.
Detailed guide: White-Label Visitor Identification
Multi-tenant API setup: Multi-Tenant Visitor Identification for SaaS Platforms
Use Case 3: Real-Time Sales Alerts
What it is: Instant Slack (or Teams/email) notifications when a high-value prospect visits your website.
Why it matters: The average B2B buyer visits your site 2-3 times before filling out a form. If your sales rep contacts them within 5 minutes of a pricing page visit, the probability of qualification is 21x higher than waiting 30 minutes. Real-time alerts make that possible.
Architecture
Leadpipe Webhook (First Match trigger)
↓
Your Server (filter logic)
↓
Slack Incoming Webhook
↓
#sales-alerts channelHow It Works
- Configure a Leadpipe webhook with the “First Match” trigger.
- Your server receives the webhook payload and applies filters:
- Is the visitor from a target account?
- Did they view the pricing or demo page?
- Does their job title indicate decision-making authority?
- If they pass the filters, format a Slack message with the visitor’s name, company, title, pages viewed, and intent topics.
- Post to your #sales-alerts channel.
Example Slack Alert
🔥 High-Intent Visitor Identified
Name: Sarah Chen
Title: VP of Marketing
Company: Acme Corp (500 employees, SaaS)
Email: sarah.chen@acmecorp.com
Pages: /pricing → /case-studies → /demo
Intent Topics: visitor identification, lead generation, ABM
Time on Site: 4m 32s
[View in CRM] [Send Outreach]Your sales rep sees this in real time, opens the CRM link, and reaches out while the prospect is still thinking about your product.
Cost: $0 additional (Slack webhooks are free, Leadpipe webhook delivery is included in all plans).
Setup guide: Leadpipe Slack Visitor Alerts
Use Case 4: CRM Enrichment Pipeline
What it is: An automated pipeline that identifies visitors, enriches their data through Clay’s waterfall, and pushes complete records to your CRM.
Why it matters: Most CRM data decays at 25-30% per year. And most leads enter the CRM with minimal information - maybe a name and email from a form submission. This pipeline ensures every contact in your CRM has complete, current data, plus the context of what they were researching on your site.
Architecture
Leadpipe Webhook
↓
Clay (waterfall enrichment)
├── Clearbit → company data
├── Apollo → contact data
├── LinkedIn → social profile
└── Your custom sources
↓
HubSpot / Salesforce
↓
Lead Score → Assignment → SequenceHow It Works
- Leadpipe identifies a website visitor and fires a webhook.
- The webhook triggers a Clay workflow that runs the visitor through multiple enrichment sources (waterfall pattern).
- Each source fills in gaps: Clearbit adds firmographics, Apollo adds direct dials, LinkedIn adds social context.
- The enriched record pushes to your CRM with all fields populated.
- Your CRM’s lead scoring model processes the record and routes it to the right sales rep.
The key insight: Leadpipe provides the identity layer (who is this person?), and Clay’s waterfall enrichment fills in everything else. Instead of relying on one data source, you get the best data from multiple sources, deduped and merged.
What Makes This Better Than Manual Enrichment
Manual enrichment means your SDRs spend 15-30 minutes per lead researching contacts on LinkedIn, verifying emails, and filling CRM fields. At scale, that’s 50-100 hours per month of research time.
This pipeline does it in seconds, automatically, for every visitor. Your SDRs skip the research and go straight to outreach.
Setup guide: How to Add Visitor Identification to Clay Waterfall
Use Case 5: Intent-Powered Ad Targeting
What it is: Build highly targeted ad audiences from Leadpipe’s intent data, export them as CSV, and upload to LinkedIn Ads or Google Ads.
Why it matters: Most B2B ad targeting is broad. You target job titles, industries, and company sizes - and pray that the right people see your ads. Intent data lets you target people who are actively researching topics relevant to your product. The click-through and conversion rates are dramatically higher.
Architecture
Leadpipe Intent API
↓
Filter by Topic + Confidence Score
↓
Export CSV (email, company, title)
↓
Upload to LinkedIn Matched Audiences
↓
Run ads to people actively researching your categoryHow It Works
- Query Leadpipe’s intent endpoints to find people researching topics relevant to your product.
- Filter by confidence score (focus on high-confidence signals), job title, company size, and industry.
- Export the audience as a CSV with email addresses.
- Upload the CSV to LinkedIn’s Matched Audiences or Google’s Customer Match.
- Run ads specifically to people who are already in-market for your solution.
Why This Works
Traditional LinkedIn targeting: “VPs of Marketing at SaaS companies with 50-500 employees.” That’s everyone who holds that title - whether they’re looking for a solution like yours or not.
Intent-powered targeting: “VPs of Marketing at SaaS companies who researched ‘visitor identification’ or ‘ABM software’ in the last 14 days.” That’s a fraction of the audience, but they’re actively looking for what you sell.
The result: 2-5x higher conversion rates on the same ad spend. You’re not interrupting - you’re appearing in front of people who are already thinking about your category.
Leadpipe tracks 20,735 intent topics across its identity graph. That granularity lets you build audiences around specific research behavior, not just demographics.
Detailed guide: Build LinkedIn Ads Audiences with Orbit
More on intent audiences: Every SaaS Company Should Build These Audiences
Use Case 6: Customer Churn Detection
What it is: Track when existing customers visit competitor websites, your cancellation page, or search for alternative solutions - and trigger retention workflows automatically.
Why it matters: Churn doesn’t happen suddenly. Customers start researching alternatives weeks before they cancel. If you can detect those signals early, your customer success team can intervene before the decision is made.
Architecture
Leadpipe Intent Data
↓
Match Against Customer List
↓
Churn Signal Detection
├── Visited competitor pages?
├── Researching "[your category] alternatives"?
├── Visited your cancellation/downgrade page?
└── Decreased usage + competitor research?
↓
Alert Customer Success Team
↓
Trigger Retention WorkflowHow It Works
- Export your current customer list (email, company domain) from your CRM.
- Use Leadpipe’s intent data to monitor what your customers are researching across the web.
- Flag accounts where intent topics match churn signals:
- Searching for “[your product] alternatives”
- Researching competitor products by name
- Looking at “[your category] pricing” (comparison shopping)
- Visiting your cancellation or account settings page
- Score accounts by churn risk based on signal strength and frequency.
- Alert your CS team when an account crosses the risk threshold.
- Trigger automated retention workflows: personalized email from the account manager, offer to jump on a call, proactive feature introduction.
The Math
If your average customer is worth $2,000/month and your churn rate is 5%, you’re losing $100 per customer per month to churn on average. Reducing churn by even 10% on a 1,000-customer base saves $120,000/year.
The cost of monitoring: your existing Leadpipe plan (intent data is included). The cost of the CS intervention: your team’s time, which they’d spend reactively anyway. The difference: you catch churn signals 2-4 weeks earlier, when you can still do something about it.
Detailed guide: Detect Customer Churn Signals from Website Behavior
Use Case 7: Multi-Tenant SaaS Feature
What it is: Embed visitor identification as a feature in your SaaS product, where each of your customers gets their own pixel, their own data, and their own dashboard.
Why it matters: If you’re building a sales tool, marketing platform, or agency management system, your customers expect visitor identification as a native feature. Without it, they’re logging into a separate tool and manually connecting the dots. With it, your product becomes the single source of truth.
Architecture
Your SaaS Platform
↓
Leadpipe Pixel API
├── POST /v1/data/pixels → Create pixel for Customer A
├── POST /v1/data/pixels → Create pixel for Customer B
├── POST /v1/data/pixels → Create pixel for Customer C
↓
Webhooks (routed by pixel ID)
├── Customer A data → Your DB (tenant A)
├── Customer B data → Your DB (tenant B)
└── Customer C data → Your DB (tenant C)
↓
Your Frontend (per-tenant views)How It Works
- When a new customer signs up for your platform, you create a Leadpipe pixel via the API (
POST /v1/data/pixels). - Your customer installs the pixel on their website (you provide them with the snippet).
- Leadpipe fires webhooks to your server with the pixel ID included, so you know which tenant the data belongs to.
- You store the identity data in your database, partitioned by tenant.
- Your frontend displays visitor data in each customer’s dashboard.
API Example
Creating a pixel for a new tenant:
curl -X POST "https://api.leadpipe.com/v1/data/pixels" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Customer ABC - Main Site",
"domain": "customerabc.com",
"webhook_url": "https://yourplatform.com/webhooks/leadpipe",
"trigger": "first_match"
}'Updating a pixel’s configuration:
curl -X PATCH "https://api.leadpipe.com/v1/data/pixels/px_abc123" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"webhook_url": "https://yourplatform.com/webhooks/leadpipe/v2",
"trigger": "every_update"
}'Revenue Model
This is where the economics get interesting. You’re embedding Leadpipe’s API as a feature in your product and charging your customers for the value.
| Item | Details |
|---|---|
| Your Leadpipe cost | Platform-tier pricing (volume-based) |
| Your customer’s price | $200-1,000+/mo as part of your SaaS subscription |
| Margin | 60-80% on the identity data feature |
The identity data isn’t your core product - it’s a feature that makes your core product more valuable. You’re not competing with Leadpipe. You’re using Leadpipe to compete with every other platform in your category that doesn’t offer visitor identification.
Setup guide: Multi-Tenant Visitor Identification for SaaS Platforms
Build vs buy decision: Identity Resolution for Platforms: Build vs Buy vs Embed
Getting Started
Every use case above runs on the same foundation: Leadpipe’s identity resolution API. Here’s how to start.
Step 1: Sign up. Create your free account. No credit card required. You get 500 identified leads to test with.
Step 2: Install the pixel. Add the JavaScript snippet to your website. Takes 2 minutes.
Step 3: Choose your use case. Start with the one that delivers value fastest for your team:
- Sales team? Start with real-time Slack alerts.
- Developer? Start with the AI sales agent.
- Agency? Start with the white-label platform.
- Marketing? Start with intent-powered ad targeting.
Step 4: Build. Use the TypeScript SDK (npm install @leadpipe/client), the MCP server (npx -y @leadpipe/mcp), or raw REST API calls. Full documentation is public.
The API is the same for all use cases. The 23 endpoints, the webhook system, and the 4.44B-profile identity graph work whether you’re building a weekend project or a production platform.
Start your free trial - 500 identified leads, no credit card, and you’ll have real identity data flowing within minutes.
FAQ
Which use case delivers the fastest ROI?
Real-time sales alerts (Use Case 3). You can set it up in under an hour, and your sales team starts getting actionable notifications immediately. No code required beyond a simple webhook handler. If your average deal size is above $1,000, you’ll see ROI from the first identified visitor who converts.
Can I combine multiple use cases?
Yes. Most teams start with one and expand. A common progression: start with Slack alerts (immediate value), add CRM enrichment (data quality), then build the AI sales agent (automation). All three use the same Leadpipe pixel and webhook infrastructure.
How much engineering effort does each use case require?
- Slack alerts: 1-2 hours (webhook handler + Slack integration)
- CRM enrichment: 2-4 hours (Clay workflow + CRM mapping)
- Intent ad targeting: 1-2 hours (API queries + CSV export)
- AI sales agent: 1-2 days (FastAPI server + OpenAI integration)
- White-label platform: 1-2 weeks (dashboard + multi-tenant data layer)
- Multi-tenant SaaS feature: 1-2 weeks (pixel management + tenant routing)
- Churn detection: 2-3 days (matching logic + alerting)
Do I need to be a developer to build these?
Use Cases 3 (Slack alerts) and 4 (CRM enrichment via Clay) can be built by non-developers using webhook tools like Zapier or Clay. The rest require development work - Python or TypeScript are most common.
What’s the minimum Leadpipe plan needed for each use case?
The Starter plan ($147/mo, 500 identified visitors) works for Use Cases 1, 3, 4, 5, and 6. Use Cases 2 and 7 (white-label and multi-tenant) typically require the Agency plan ($1,279/mo for 20,000 IDs) or higher. For platforms processing very high volume, Leadpipe’s high-volume tier stabilizes at $8,000/mo for 1M+ identifications ($0.008/ID), making the unit economics even stronger for white-label and multi-tenant use cases.
Can I use a different identity resolution API for these use cases?
In theory, any identity API works for the basic patterns. In practice, most of these use cases depend on features that other providers lack: real-time webhooks (FullContact doesn’t offer them), intent data (most providers don’t include it), pixel management API (enterprise providers don’t expose it self-serve), and MCP server (unique to Leadpipe). See the API comparison for a full feature breakdown.
How do I measure success?
Each use case has a different primary metric:
- AI sales agent: meetings booked per month
- White-label platform: monthly recurring revenue from clients
- Sales alerts: response time to high-intent visitors
- CRM enrichment: data completeness rate
- Ad targeting: cost per qualified lead
- Churn detection: retained accounts per quarter
- Multi-tenant feature: customer adoption rate and retention impact
Related Articles
- Build a Custom AI SDR with Leadpipe + OpenAI - complete AI sales agent tutorial
- White-Label Visitor Identification - agency and platform guide
- Leadpipe Slack Visitor Alerts - real-time alert setup
- How to Add Visitor Identification to Clay Waterfall - CRM enrichment pipeline
- Detect Customer Churn Signals from Website Behavior - churn detection guide
- Multi-Tenant Visitor Identification for SaaS Platforms - multi-tenant architecture
- Identity Resolution API Comparison 2026 - provider comparison
- Visitor Identification API: Complete Developer Guide - full API reference
