By the end of this tutorial, you’ll know how to create a Website visitors signal agent, connect your website tracking script, define visit criteria, choose the scope, and decide how matched signals should be processed.
Why this matters
Website visitors can now identify individual contacts who visit your website — not just companies. This upgrade adds person-level identification on top of the existing company-level detection.
This means you can see who visited your site, including their name, role, and seniority, so you can prioritize outreach more accurately and focus first on likely decision-makers.
Important: Person-level identification is currently available only for visitors in the United States 🇺🇸. If an individual cannot be resolved, the signal falls back to company-level detection.
Prerequisites
You should already know how to navigate your lemlist workspace and have access to Signal agents. You should also be able to update your website header or work with someone on your team who can install the tracking script for you.
Before launching, keep in mind that Website visitors costs 20 credits per signal.
What changed
No migration is required: existing setups benefit automatically.
No tracker update is required: the tracking pixel setup stays the same.
No settings change is required: the experience remains the same, but the signal can now include person-level details for US visitors.
Fallback still applies: if person-level identification is not possible, lemlist falls back to company-level detection.
How it works
Install the lemlist tracking pixel on your website.
When someone lands on your site, the pixel captures the visit and attempts to resolve it to an individual contact.
The signal appears in Signals with richer details when available, including the identified person.
If no person can be identified, the signal still appears at the company level.
Phase 1: Create the signal agent
Open the Website visitors setup flow.
Go to Signal agents, then click Create signal agent. This opens the setup wizard for a new Website visitors signal agent.
Select the Website visitors signal.
In the Buyer intent category, choose Website visitors. This is the signal that can now surface person-level visitor data for US traffic when available.
Name your signal agent.
Enter an Agent name. You’ll also see the setup guides for supported installation methods, but the tracker itself works the same as before.
Billing note: Website visitors cost 20 credits per signal.
Phase 2: Connect your website tracker
If your tracking script is already installed, you do not need to migrate or replace it. Just confirm the correct domain is selected. If it is not installed yet, complete the setup here.
Select your domain and review the tracker setup.
In the Website visitor set up section, choose the website you want to monitor, copy the script if needed, and confirm the tracker is installed on your site.
Good to know: The tracking setup has not changed. The upgrade happens in the signal resolution layer, not in the pixel installation.
Phase 3: Define which visits should count
Choose your inclusion criteria.
Select whether to track Any page or Custom landing pages, then set a minimum visit duration, minimum pages viewed, and optional target geographies. Since person-level identification is only available in the US, use geography filters carefully if that is your target use case.
Review your exclusion criteria.
Add any geographies you want to exclude and leave Exclude known bots and crawlers enabled to keep your signals clean.
Phase 4: Choose the scope
Select the segment to monitor.
Choose All segments if you want the signal agent to evaluate all matching website visitors across your monitored traffic.
Phase 5: Decide how signals should be processed
Choose how matched signals should be handled.
You can review signals manually, auto-create tasks, or auto-push leads into a campaign. In the example below, Auto-push to campaign is selected.
Phase 6: Review and deploy
Review the full configuration, then deploy the agent.
Check the signal setup, billing, processing method, and scope, then click Deploy agent.
Where you'll use it
You’ll use this inside your Website visitors signals view under Signals. The workflow stays familiar — you just get richer signal data whenever lemlist can identify the actual visitor instead of only the company.
Things to note
US only: individual contact identification is currently available only for visitors in the United States.
No billing change: Website visitors still costs 20 credits per signal.
No setup change: no migration, reconfiguration, or tracker update is required.
Fallback behavior: when person-level identification is not possible, the signal falls back to company-level detection.
Not every visitor will resolve: identification depends on whether a person can be matched from the visit.
Practical application
A strong use case is monitoring US website traffic and prioritizing outreach based on who visited. If a senior decision-maker lands on your pricing page, that signal can justify faster and more personalized follow-up. If the visitor is not a fit, your team can deprioritize that lead and focus elsewhere.
In other words: less guesswork, more targeted prospecting.