By the end of this tutorial, you’ll know how to create a Website Visitors watchlist, install the tracking script, define the right visit criteria, and route matched companies into your workflow for follow-up.
Why this matters
Website visitor signals help you turn anonymous traffic into actionable company-level intent. When you track the right pages and apply the right filters, you can focus your team on accounts already showing interest instead of starting from cold outreach.
Prerequisites
You should already know how to navigate your lemlist workspace and have access to Signals. 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.
What you can use Website Visitors for
High-intent page visits: Trigger faster outbound follow-up when companies visit pages like pricing, product, or integrations.
ABM workflows: Use website visit data as a company-level intent signal for prioritization and segmentation.
Building target lists: Turn visitor activity into qualified company lists for outreach and campaign planning.
Phase 1: Create the watchlist
Open the Website Visitors setup flow.
Go to Signals, then click New watchlist. This starts a new signal workflow and lets you choose what kind of buying intent you want to monitor.
Select the website visitor signal.
Choose Company visited my website, then click Next. This tells lemlist to identify companies visiting your website based on visitor IP data.
Name your watchlist clearly.
Enter a descriptive watchlist name that tells your team what this watchlist is meant to track. A clear name makes it easier to manage multiple watchlists later.
Phase 2: Install the Website Visitors tracking script
Before the watchlist can detect visitors, you need to connect it to the website you want to monitor.
Select the domain you want to track.
In the Website visitor set up section, click the website field. If your domain is already listed, select it. If it is not listed yet, choose Add new website URL. This makes sure your watchlist is attached to the correct site.
Copy the tracking script.
Click the copy icon next to the script. You’ll use this code in your website installation flow so lemlist can detect and identify visits.
Install the script on your website.
Choose the installation method that matches how your site is managed:Option 1: Install the tracking script directly in your website header
Paste the copied script into your website <head> section.Option 2: Install the tracking script using Google Tag Manager
Log in to Google Tag Manager and open the container for your website.
Click Tags in the left-hand menu, then click New.
Click Tag Configuration and select Custom HTML.
Paste the lemlist tracking code into the HTML field.
Click Triggering, then select All Pages.
Click Save and give the tag a recognizable name, such as lemlist Website Visitors.
Click Submit in the top-right corner, then click Publish to make the changes live.
Option 3: Install the tracking script using Webflow
Open your Webflow project and go to Site Settings.
Click the Custom Code tab.
Paste the lemlist tracking code into the Footer Code section.
Click Save Changes.
Publish your site to make the changes live.
Confirm installation in lemlist.
After the script is live on your site, check I have pasted the tracking code on my website, then click Next to proceed.
Important: Website Visitors works at the company level, not the individual visitor level. For best results, install the script on the exact domain you want to monitor and focus on pages that indicate real buying intent.
Where to manage your Website Visitors script later
If you need to revisit your tracker later, click your profile avatar, select Settings, then open Website visitors. From there, you can review your active trackers, copy the script again, and adjust your daily identification limits.
Phase 3: Configure which visits should count as a signal
This phase determines what kind of website traffic should trigger your watchlist. The more intentional your setup is, the more useful your signals will be.
Choose what pages to track.
Select Any page if you want broad coverage across your site, or choose Custom landing pages if you only want to monitor specific high-intent URLs. Use custom landing pages when you want tighter qualification and less noise.
Set engagement thresholds.
Choose a minimum visit duration and minimum pages viewed. These filters help you ignore weak visits and focus on companies showing stronger interest.
Add target geographies if relevant.
Use Target geographies if your team only sells in specific countries or regions. This keeps your watchlist aligned with your actual market.
Exclude locations you do not want to monitor.
Add excluded geographies when there are countries or regions outside your sales scope. This is especially useful if your site gets traffic from markets you do not serve.
Keep bot filtering enabled.
Leave Exclude known bots and crawlers turned on to remove automated traffic and keep your signal quality high.
Phase 4: Choose which companies to evaluate
After defining the visit criteria, choose the population you want the watchlist to monitor.
Select the segment to monitor.
For a standard setup, choose All segments. This lets the watchlist evaluate every company that matches your visitor rules instead of limiting detection to a narrower list.
Phase 5: Decide how signals should be processed
Once a company matches your watchlist, you need to decide what should happen next. This is where you turn intent into action.
Choose your processing method and configure follow-up.
You can manually process signals, create tasks for your team, or use campaign routing when available. In the example below, the watchlist is set to Create a task for the identified signals, with task ownership, title, and instructions configured for follow-up. This is a practical option when you want your team to act on visitor intent quickly without checking Signals manually all day.
Best practice: Decide on your processing method before you launch the watchlist. A good routing setup ensures signals do not sit unused after companies start appearing.
Phase 6: Review and finish setup
Review the summary before activating the watchlist.
Check the tracked domain, inclusion criteria, billing impact, and signal processing setup. This final review helps you catch misconfigurations before the watchlist goes live.
Practical application
A common use case is creating a watchlist for high-intent traffic from the United States with a minimum visit duration and page-view threshold. This helps sales teams focus on companies that did more than just bounce from the homepage.
For example, you might track all pages, require at least 1 minute on site and 1 page viewed, limit detection to the United States, and create a task whenever a company matches. That setup gives you a steady stream of qualified website visitor signals your team can work through every day.
Troubleshooting & pitfalls
No visits are being detected
Root cause: The script is not installed correctly or the wrong domain is selected.
Fix: Re-copy the script from the watchlist or from Settings > Website visitors.
Fix: Confirm the script is pasted inside the website <head> section, added through Google Tag Manager, or inserted in Webflow Custom Code.
Fix: Check that the selected domain matches the live site receiving traffic.
Fix: If you used Google Tag Manager or Webflow, make sure you published the change so it is live on your site.
You are getting too many low-quality matches
Root cause: Your rules are too broad.
Fix: Switch from Any page to Custom landing pages if you only care about high-intent sections.
Fix: Increase the minimum visit duration or minimum pages viewed.
Fix: Add geography filters to focus only on your target market.
You are not getting enough matches
Root cause: Your filters may be too restrictive.
Fix: Lower the duration or page-view thresholds.
Fix: Remove unnecessary geography restrictions.
Fix: Check whether your daily identification limit in Settings > Website visitors is too low.
Your team is not acting on signals fast enough
Root cause: Signals are being collected but not routed into a workflow.
Fix: Use Create a task for the identified signals so matched companies automatically appear in your team’s task flow.
Fix: Add clear instructions in the task configuration so reps know what to do next.