Turn de-anonymized website visitors into named, contactable buyers

Go from a company-level website visit to the right persona with email and mobile.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

A selection of teams that run this job on Forager · plus other sales-tech platforms

Uses POST /person_role_search/, POST /person_detail_reverse_lookup/by_email/, POST /person_contacts_lookup/phone_numbers/ · People search API reference

What it costs: 15 credits per mobile found · 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

3 inputs → People search + Person enrichment + Work emails + Mobile numbers → 4 fields sample data

01 · Inputs

Company domain

example.com

resolved email (optional)

linkedin.com/in/jane-example

persona definition

linkedin.com/in/jane-example

02 · Forager

People search + Person enrichment + Work emails + Mobile numbers POST /person_role_search/

Match found

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

role title: VP Revenue Operations
work email: jane@example.com
phone number: +1 (415) 555-0142
name: Jane Example
company: Example Inc.

4 fields in the responseexample data

Steps

Receive the visiting company domain (and person email if resolved) from the visitor-ID layer
Find matching personas with POST /person_role_search/ (organization_domains, role_title)
For person-level matches, resolve with POST /person_detail_reverse_lookup/by_email/
Add work_email and mobile via /work_emails/ and POST /person_contacts_lookup/phone_numbers/
Push to sequencing or alert the account owner with pages viewed

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Receive the visiting company domain (and person email if resolved) from
# the visitor-ID layer

# 2. Find matching personas with POST /person_role_search/
# (organization_domains, role_title)
r1 = requests.post(f"{BASE}/person_role_search/", headers=HEADERS, json=body)

# 3. For person-level matches, resolve with POST
# /person_detail_reverse_lookup/by_email/
r2 = requests.post(f"{BASE}/person_detail_reverse_lookup/by_email/", headers=HEADERS, json=body)

# 4. Add work_email and mobile via /work_emails/ and POST
# /person_contacts_lookup/phone_numbers/
r3 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 5. Push to sequencing or alert the account owner with pages viewed

# 1. POST /person_role_search/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_role_search/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. POST /person_detail_reverse_lookup/by_email/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_reverse_lookup/by_email/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 3. POST /person_contacts_lookup/phone_numbers/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: People search API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
visitor company domain	`person name`
resolved email (optional)	`role_title`
persona definition	`work_email`
	`phone_number`

Questions about this recipe

How do I get contact details for companies visiting my website?

Receive the visiting company domain (and person email if resolved) from the visitor-ID layer. Add work_email and mobile via /work_emails/ and POST /person_contacts_lookup/phone_numbers/.

What does it cost to turn de-anonymized website visitors into named, contactable buyers?

People search: people search 1 credit per request and people search: role details 1 credit per request, charged whether or not data comes back. Person enrichment: 1 credit per request, charged whether or not data comes back. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles, 1,650 emails or 8,250 search requests, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send persona definition, resolved email (optional) and visitor company domain. You get back person name, phone_number, role_title and work_email, as JSON. You also need a Forager API key, which comes with a free account.

What's the next step after identifying which companies visit my site?

Go from a company-level website visit to the right persona with email and mobile. Website traffic converts into contactable pipeline.

Is there a free way to try Forager on this workflow?

Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.

When should I run this workflow?

Visitor-ID resolves a session to a company domain or a person-level match. Website traffic converts into contactable pipeline.

Which Forager products does this recipe use?

People search, person enrichment, work emails and mobile numbers. People search: find the people who hold a role at target companies, filtered by title, seniority, department and location. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.

How do I know the data is right?

Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.

How do I enrich website visitors with contact info?

Receive the visiting company domain (and person email if resolved) from the visitor-ID layer. Add work_email and mobile via /work_emails/ and POST /person_contacts_lookup/phone_numbers/.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from your own code, Make and n8n. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

5 steps: receive the visiting company domain (and person email if resolved) from the visitor-ID layer, find matching personas with POST /person_role_search/ (organization_domains, role_title), for person-level matches, resolve with POST /person_detail_reverse_lookup/by_email/, add work_email and mobile via /work_emails/ and POST /person_contacts_lookup/phone_numbers/ and push to sequencing or alert the account owner with pages viewed.

Is there a contract or minimum commitment?

No contract to start: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

A selection of teams that run this job on Forager · plus other sales-tech platforms

Clay
- GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Juicebox
- AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
Nooks
- Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Vieu
- ABM & intent
Relationship-mapping platform that helps sales teams and AI agents find warm introductions.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
BetterContact
- Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
Cortex Intelligence
- ABM & intent
GTM intelligence platform for account research and outbound.
Epoch
- ABM & intent
B2B event marketing platform.

Turn de-anonymized website visitors into named, contactable buyers

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How do I get contact details for companies visiting my website?

What does it cost to turn de-anonymized website visitors into named, contactable buyers?

What do I need to run this recipe, and what comes back?

What's the next step after identifying which companies visit my site?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do I know the data is right?

How do I enrich website visitors with contact info?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

More recipes for ABM & intent

Score accounts on hiring momentum from job postings

Resolve email lists to professional profiles to lift ad match rates

Build enriched invite lists for executive dinners, round tables and conferences

Turn social post engagers into ICP-scored, emailable leads

Predict warm-intro paths from overlapping work history

Seed an ABM platform's contact layer with a licensed people feed

Put people, company and job data your users can act on inside your product